Sources don't start after reboot(?)

[eloyd]

Okay, so we updated our CentOS box that we recently installed NNA on. Rebooted box. Nagios then alerted us ~10 minutes later that the box was not running the NNA sources. So I logged in and started them.

I would expect that these would start automatically upon system start. Did I miss something or do we need to log in and start them every time the box comes up?

[sreinhardt]

They definitely should be started on boot to my knowledge. Let me dig around the source creation code and see if that is in fact the case. Is this a new change post NNA update, system update, or possibly happening for a while and wasn't noticed?

[eloyd]

This was a new CentOS 6.5 box we turned up, did a yum -y update, installed NNA, and then didn't touch it for a few weeks. Recently did another yum -y update and rebooted.

[sreinhardt]

OK, so we don't really know if this was happening pre-update or not. I am going to assume that it was not working properly, and go digging for code. The worst I do is spend some time learning how thats all working and find that it's not a bug.

[eloyd]

I could always reboot again and see if they start automagically, but my lookey through the startups didn't show me any way that they would have been started:

Code: Select all

chkconfig --list | grep 3:on
auditd          0:off   1:off   2:on    3:on    4:on    5:on    6:off
blk-availability        0:off   1:on    2:on    3:on    4:on    5:on    6:off
crond           0:off   1:off   2:on    3:on    4:on    5:on    6:off
httpd           0:off   1:off   2:off   3:on    4:off   5:on    6:off
ip6tables       0:off   1:off   2:on    3:on    4:on    5:on    6:off
iptables        0:off   1:off   2:on    3:on    4:on    5:on    6:off
iscsi           0:off   1:off   2:off   3:on    4:on    5:on    6:off
iscsid          0:off   1:off   2:off   3:on    4:on    5:on    6:off
lvm2-monitor    0:off   1:on    2:on    3:on    4:on    5:on    6:off
mdmonitor       0:off   1:off   2:on    3:on    4:on    5:on    6:off
mysqld          0:off   1:off   2:off   3:on    4:off   5:on    6:off
netfs           0:off   1:off   2:off   3:on    4:on    5:on    6:off
network         0:off   1:off   2:on    3:on    4:on    5:on    6:off
rsyslog         0:off   1:off   2:on    3:on    4:on    5:on    6:off
sendmail        0:off   1:off   2:on    3:on    4:on    5:on    6:off
sshd            0:off   1:off   2:on    3:on    4:on    5:on    6:off
udev-post       0:off   1:on    2:on    3:on    4:on    5:on    6:off

# cat /etc/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

[lesnikov]

We have the same problem sources not starting after reboot.
Our installation is NNA 64-bit OVF template on ESX.

[sreinhardt]

I am seeing similar effects on a cent 5 system. I've put in an internal bug for it, as it doesn't appear anything has been posted yet for that.

[eloyd]

Cent 5? Do they even spell that anymore?

[jomann]

This is most likely due to how it is running the start/stop commands ... I do know there is a bug report filed and it should be getting fixed soon.

[sreinhardt]

Hey someone has to test the oldest supported OSes right? It's a wee bit of torture, but then again I'm an archlinux and zsh guy... I pretty much just pile it on