Page 1 of 1
New 4.0 install, won't start on boot
Posted: Tue Jan 28, 2014 9:05 am
by MikeM-2468
I've installed 4.0.2 on Debian 7.3.0. Everything is great except for start on boot. I've done what I've always done for all my other 3.x installs:
Code: Select all
ln -s /etc/init.d/nagios /etc/rcS.d/S99nagios
Running this works fine.
I'm not seeing any errors in any logs. Where can I look? I used the script in
http://support.nagios.com/forum/viewtop ... =7&t=21578 to make it start. I was getting the error
Code: Select all
Can't open /etc/rc.d/init.d/functions error.
with the default script.
I also tried applying all of the suggestions in
http://support.nagios.com/forum/viewtop ... oot#p60396
Re: New 4.0 install, won't start on boot
Posted: Tue Jan 28, 2014 11:02 am
by abrist
Any hints in the system messages from boot?
Re: New 4.0 install, won't start on boot
Posted: Tue Jan 28, 2014 11:04 am
by MikeM-2468
nothing
Re: New 4.0 install, won't start on boot
Posted: Tue Jan 28, 2014 2:59 pm
by abrist
How about the full system logs?
You could just create a script to start the service and then run that script on boot with rc.local, bashrc, etc.
Re: New 4.0 install, won't start on boot
Posted: Tue Jan 28, 2014 3:05 pm
by MikeM-2468
That won't help since nagios is part of the host name.
rc.local works, but I'm puzzled as to why it doesn't work the normal way. If it indicates a larger problem, I'd like to get to the bottom of it.
Re: New 4.0 install, won't start on boot
Posted: Wed Jan 29, 2014 10:45 am
by abrist
The larger problem is an issue with the init script - some newer distros changed up the lsb functions and broke the init script. I wrote a hack to get it working, but it most likely does not integrate nicely with certain init systems . . .
Re: New 4.0 install, won't start on boot
Posted: Wed Jan 29, 2014 10:51 am
by MikeM-2468
I used the hack to start it, but I can only get it to start in rc.local.
Re: New 4.0 install, won't start on boot
Posted: Wed Jan 29, 2014 11:12 am
by abrist
MikeM-2468 wrote:but I can only get it to start in rc.local.
That may be as far as you can go without the script getting fixed proper.