Startup on 2.0AA
-
I just did an upgrade to the latest SNAP and am again seeing a failure on the startup script.
The error in the logs is as follows:
Nov 15 11:43:48 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Nov 15 11:43:48 init: /bin/sh on /etc/rc terminated abnormally, going to single user modeI notice that the console screen hangs after generating the RRDgraphs and the only way to get the box to fully boot is to CTRL-C it at the console.
I also noticed that no changes can be made through the webConfigurator (assuming this is due to the single user level).
-
I am also seeing some "apinger" errors in the logs and thought it might be related ….
Nov 15 11:46:33 apinger: Exiting on signal 15.
Nov 15 11:46:24 apinger: command (touch /tmp/filter_dirty) exited with status: 1
Nov 15 11:46:24 apinger: Error while starting command.
Nov 15 11:46:14 apinger: ALARM: wan(127.0.0.2) *** down ***
Nov 15 11:46:04 apinger: Exiting on signal 15. -
what sort of wan is this.
The 127.0.0.2 dictates a down dynamic interface.
The exiting 15 is from when I kill it when it reconfigures. This is normal.
The touch filter_dirty is one I am still actively pursuing. It has to do with /tmp losing permissions.