Hey guys,
Thanks! That worked.
[root@monitor2:~] #grep zabbix /var/log/audit/audit.log | audit2allow -M
myzabbix
IMPORTANT ***
To make this policy package active, execute:
semodule -i myzabbix.pp
[root@monitor2:~] #semodule -i myzabbix.pp
[root@monitor
On 06/17/2015 04:03 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@monitor2:~] #updatedb
>> [root@monitor2:~] #locate myzabbix.te
>> [root@
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@monitor2:~] #updatedb
> [root@monitor2:~] #locate myzabbix.te
> [root@monitor2:~] #find / -name "myzabbix.*"
>
> I also did sea
>
> 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@monitor2:~] #updatedb
[root@monitor2:~] #locate myzabbix.te
[root@monitor2:~] #find / -name "myzabbix.
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
>
> 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 wrote:
> On 17/06/15 16:29, Tim Dunphy wrote:
>
>> That's because there's already a zabbix module load
On 17/06/15 16:29, Tim Dunphy 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 myzab
>
> 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
On 17/06/15 15:27, Tim Dunphy wrote:
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@monitor2:~] #semodule -i zabbix.pp
libsepol.print_missin
>
> 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@monitor2:~] #semodule -i zabbix.pp
libsepol.print_missing_requirements: zabbix's global
Try something like:
grep zabbix /var/log/audit/audit.log | audit2allow -M zabbix
semodule -i zabbix.pp
On 16/06/15 15:58, Tim Dunphy wrote:
Hey guys,.
I have a centos 7 machine I'm using as a zabbix server. And I noticed that
apache won't start, with this complaint in the error log:
(13)Per
Hey guys,.
I have a centos 7 machine I'm using as a zabbix server. And I noticed that
apache won't start, with this complaint in the error log:
(13)Permission denied: AH00091: httpd: could not open error log file
/var/log/zabbix_error_log.
AH00015: Unable to open logs
I tried having a look at
12 matches
Mail list logo
