search for: myzabbix

> > What turns up in myzabbix.te? Same deal. :( #semodule -i myzabbix.te semodule: Failed on myzabbix.te! sigh... but thanks any other clues? On Wed, Jun 17, 2015 at 11:42 AM, Harold Toms <h.toms at qmul.ac.uk> wrote: > On 17/06/15 16:29, Tim Dunphy wrote: > >> That's because there's already a...

> > That's because there's already a zabbix module loaded (the message isn't > very informative!). I forgot that the received wisdom is to insert "my" in > front of ones own modules i.e.: > grep zabbix /var/log/audit/audit.log | audit2allow -M myzabbix > semodule -i myzabbix.pp Hmm no luck there either: [root at monitor2:~] #semodule -i myzabbix.pp *semodule: Failed on myzabbix.pp!* I also tried: [root at monitor2:~] #semodule -i my_zabbix semodule: Failed on my_zabbix! And [root at monitor2:~] #semodule -i my-zabbix semodule: Faile...

> > Sorry, I didn't put that very clearly. Could you show us the contents of > myzabbix.te. No prob! Thanks for all the help! But in searching my system I don't find anything of the sort. [root at monitor2:~] #updatedb [root at monitor2:~] #locate myzabbix.te [root at monitor2:~] #find / -name "myzabbix.*" I also did search using 'yum provides' to find someth...

...PM, Jonathan Billings wrote: > On Wed, Jun 17, 2015 at 03:30:51PM -0400, Tim Dunphy wrote: >> No prob! Thanks for all the help! But in searching my system I don't find >> anything of the sort. >> >> [root at monitor2:~] #updatedb >> [root at monitor2:~] #locate myzabbix.te >> [root at monitor2:~] #find / -name "myzabbix.*" >> >> I also did search using 'yum provides' to find something similar. But >> wasn't' able to find anything. > What we're asking for is the contents of the .te file that is created > w...

> > Try something like: > grep zabbix /var/log/audit/audit.log | audit2allow -M zabbix > semodule -i zabbix.pp Thanks for your response! However this is what happens when I try to install the module: [root at monitor2:~] #semodule -i zabbix.pp libsepol.print_missing_requirements: zabbix's global requirements were not met: type/attribute zabbix_t (No such file or directory).

...wrote: >> That's because there's already a zabbix module loaded (the message isn't >> very informative!). I forgot that the received wisdom is to insert "my" in >> front of ones own modules i.e.: >> grep zabbix /var/log/audit/audit.log | audit2allow -M myzabbix >> semodule -i myzabbix.pp > > > Hmm no luck there either: > > [root at monitor2:~] #semodule -i myzabbix.pp > *semodule: Failed on myzabbix.pp!* > > I also tried: > > [root at monitor2:~] #semodule -i my_zabbix > semodule: Failed on my_zabbix! > > And...

On 17/06/15 17:43, Tim Dunphy wrote: >> What turns up in myzabbix.te? > > Same deal. :( > > #semodule -i myzabbix.te > semodule: Failed on myzabbix.te! > > > sigh... but thanks any other clues? Sorry, I didn't put that very clearly. Could you show us the contents of myzabbix.te. -- regards Harold Toms URL: http://iodine.chem.qmu...

...s? > > Thanks, > Tim > > That's because there's already a zabbix module loaded (the message isn't very informative!). I forgot that the received wisdom is to insert "my" in front of ones own modules i.e.: grep zabbix /var/log/audit/audit.log | audit2allow -M myzabbix semodule -i myzabbix.pp -- regards Harold Toms http://iodine.chem.qmul.ac.uk "Priestley's works... tended to unsettle every thing, and yet settled nothing." - Samuel Johnson.

On Wed, Jun 17, 2015 at 03:30:51PM -0400, Tim Dunphy wrote: > No prob! Thanks for all the help! But in searching my system I don't find > anything of the sort. > > [root at monitor2:~] #updatedb > [root at monitor2:~] #locate myzabbix.te > [root at monitor2:~] #find / -name "myzabbix.*" > > I also did search using 'yum provides' to find something similar. But > wasn't' able to find anything. What we're asking for is the contents of the .te file that is created when you run audit2allow....