Skip to main content

Nagios SELinux and you.


If you are running RHEL/CentOS and using SELinux, and you should... be using SELinux... you may have notced the following error when you attempt to submit an immediate check of a host:
Error: Could not stat() command file '/usr/local/nagios/var/rw/nagios.cmd'!

There are a number of ways to see if SELinux is preventing this from working, but the quickest is to
# setenforce 0
-- retry submitting
# setenforce 1

If the above allowed the command to run, then just run this
[root@apoc rw]# chcon -R --reference=/var/www/html /usr/local/nagios/share
[root@apoc rw]# chcon -R --reference=/var/www/html /usr/local/nagios/var
[root@apoc rw]# chcon -R --reference=/var/www/cgi-bin /usr/local/nagios/sbin
[root@apoc rw]# chcon -R -t httpd_sys_rw_content_t /usr/local/nagios/var/rw

Labels:

Comments

  1. UnknownMarch 27, 2018 at 11:13 AM

    Out of all of the comments, posts, replies that say to just disable or set SELinux to permissive, this is what we needed. Hopefully it eventually ends up at the top of the searches. Thank you!

    ReplyDelete

Post a Comment

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...
1 comment
Read more