The syslog.0 ends with:
Feb 25 06:25:02 bubba /USR/SBIN/CRON[1535]: (root) CMD (test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily)
Feb 25 06:26:00 bubba modprobe: FATAL: Could not load /lib/modules/2.6.16.16/modules.dep: No such file or directory
Feb 25 06:26:13 bubba last message repeated 2 times
and then bubba restarts. I have not noticed this before, but I think it started after the latest software upgrade - but I am not sure
What to do to avoid this?
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
Why unplanned restart each morning
Hi hakansj,
Bubba really should not reboot every morning. You have not changed anything.? What does the uptime on the main page in the web-ui say? Is it constant less than one day?
/Tor
Bubba really should not reboot every morning. You have not changed anything.? What does the uptime on the main page in the web-ui say? Is it constant less than one day?
/Tor
Co-founder OpenProducts and Ex Excito Developer
We did a forced restart 03:16 last night. Now at 22:00 the web-ui says 19 h uptime which is the time since 3:16. But why does the message in syslog.0 say what I quoted in the previous post and the first line in syslog says: Feb 25 06:26:16 bubba syslogd 1.4.1#17: restart.
Feb 25 06:36:22 bubba -- MARK --
I have now checked earlier syslogs, the same applies.
Will now have bubba running without any restarts until tomorrow morning and will then verify the logs.
/HÃ¥kan
Feb 25 06:36:22 bubba -- MARK --
I have now checked earlier syslogs, the same applies.
Will now have bubba running without any restarts until tomorrow morning and will then verify the logs.
/HÃ¥kan
Hi again,
What you see is most likely the restart of the logging daemon itself. sysklogd. Its restarted every morning at 6.25 by a cron job.
The --MARK-- is just an note that the log daemon is alive and well and can be ignored. The modprobe error is also harmless. Its due to no external device drivers been installed, which is not needed for normal operation.
Please let us know if the uptime does not pass one day though. (Then there is something else going on)
/Tor
What you see is most likely the restart of the logging daemon itself. sysklogd. Its restarted every morning at 6.25 by a cron job.
The --MARK-- is just an note that the log daemon is alive and well and can be ignored. The modprobe error is also harmless. Its due to no external device drivers been installed, which is not needed for normal operation.
Please let us know if the uptime does not pass one day though. (Then there is something else going on)
/Tor
Co-founder OpenProducts and Ex Excito Developer