Page 4 of 4
Re: Can't start nagios if apache is in custom location
Posted: Thu Jan 16, 2014 1:07 pm
by vinothsethuram
Getting command not found error. what copy you need from me?
Re: Can't start nagios if apache is in custom location
Posted: Thu Jan 16, 2014 1:10 pm
by vinothsethuram
ot@velocitylinux:/apps/apache-httpd/conf# ls
extra httpd.conf magic mime.types original workers.properties
root@velocitylinux:/apps/apache-httpd/conf# cd /httpd.conf
bash: cd: /httpd.conf: No such file or directory
Re: Can't start nagios if apache is in custom location
Posted: Thu Jan 16, 2014 1:13 pm
by tmcdonald
vino, we need you to give us a copy of the file located at:
/apps/apache-httpd/conf/httpd.conf
Re: Can't start nagios if apache is in custom location
Posted: Thu Jan 16, 2014 1:20 pm
by tmcdonald
Open up PuTTY, maximize the window, and run this:
Code: Select all
cat /etc/httpd/conf/httpd.conf | grep --invert-match "#" | sed '/^\s*$/d' | tr '\n' '#'
Then copy and paste the output here.
Re: Can't start nagios if apache is in custom location
Posted: Thu Jan 16, 2014 1:23 pm
by vinothsethuram
root@velocitylinux:~# cat /etc/httpd/conf/httpd.conf | grep --invert-match "#" | sed '/^\s*$/d' | tr '\n' '#'
cat: /etc/httpd/conf/httpd.conf: No such file or directory
I sent PM with attachment
Re: Can't start nagios if apache is in custom location
Posted: Thu Jan 16, 2014 1:25 pm
by tmcdonald
I got your PM. As for the command I had you run, I neglected to change the file path to yours.
We will review your file and get back to you.
Re: Can't start nagios if apache is in custom location
Posted: Fri Jan 17, 2014 9:27 am
by vinothsethuram
Hi,
Any updates?
Thanks
Re: Can't start nagios if apache is in custom location
Posted: Fri Jan 17, 2014 3:56 pm
by slansing
We looked over the config file and did not notice anything that would cause this issue, it looks in order. At this point we need to make it clear that we only support installations on clean minimal distro installs, and the packages that are grabbed as a part of nagios prerequisites are in their expected, default, installation locations. This is where Nagios expects to find what it requires. While we try to support installations that go beyond this, at a certain point it is no longer feasible to try and hunt down changes that are not officially supported.