I upgraded on of my clients from V4 to V5 current patches. Now his firewall reboots every few minutes: I do have some log entries:
From the selfmon.log -------------------------->
check Failed increment sshd_running counter 1 - 3
2004:10:25-12:09:11 (none) selfmonng[592]: check Failed increment sshd_running counter 2 - 3
2004:10:25-12:09:16 (none) selfmonng[592]: check Failed increment sshd_running counter 3 - 3
2004:10:25-12:09:16 (none) selfmonng[592]: ssh server not running - restarted
2004:10:25-12:09:16 (none) selfmonng[592]: DEBUG: NOTIFYEVENT Name=sshd_running Level=INFO Id=108 sent
2004:10:25-12:09:16 (none) selfmonng[592]: triggerAction: 'cmd'
2004:10:25-12:09:16 (none) selfmonng[592]: actionCmd(+): '/etc/init.d/sshd restart'
2004:10:25-12:09:19 (none) selfmonng[592]: child returned status: exit='0' signal='0'
From the system.log --------------------------------------->
2004:10:25-12:09:30 (none) snmpd: NET-SNMP version 5.1
2004:10:25-12:09:33 (none) snmpd: Received TERM or STOP signal... shutting down...
2004:10:25-12:09:34 (none) snmpd: NET-SNMP version 5.1
2004:10:25-12:09:38 (none) syslog-ng[214]: new configuration initialized
2004:10:25-12:09:36 (none) syslog-ng[214]: SIGHUP received, restarting syslog-ng
2004:10:25-12:09:55 (none) syslog-ng[214]: new configuration initialized
2004:10:25-12:09:54 (none) syslog-ng[214]: SIGHUP received, restarting syslog-ng
2004:10:25-12:10:00 (none) /usr/sbin/cron[298]: (*system*) RELOAD (/etc/crontab)
2004:10:25-12:10:00 (none) /USR/SBIN/CRON[1103]: (root) CMD ( /usr/local/bin/reportcontrol.sh)
2004:10:25-12:10:06 (none) syslog-ng[214]: new configuration initialized
2004:10:25-12:10:04 (none) syslog-ng[214]: SIGHUP received, restarting syslog-ng
2004:10:25-12:10:18 (none) system[1222]: System was restarted
2004:10:25-12:10:21 (none) syslog-ng[214]: new configuration initialized
2004:10:25-12:10:20 (none) syslog-ng[214]: SIGHUP received, restarting syslog-ng
2004:10:25-12:13:00 (none) /usr/sbin/cron[298]: (*system*) RELOAD (/etc/crontab)
Notice the time in those logs.. it keeps getting reset to 12:00 after every boot.
What the #$#@%.
Jerry
This thread was automatically locked due to age.