I rent a VPS from a VPS company and run an Ubuntu 14.04 web server there. Recently it had to be suspended by my provider for a while. After the suspension period (1-2 days), the VPS boots, but cannot acquire any runlevels.
root@vps:/# runlevel unknown
This, in turn, means no Upstart services are starting on boot, as the "useful stuff" requires
I can start individual services manually with
initctl, unless they have dependencies which the boot did not start automatically.
I cannot find anything useful/understandable from logs. Please do ask if you want specific log entries and I can try to find them.
The server is (was) running PHP7, Nginx, MySQL, Redis, Minecraft Server, Mumble Server. The server was operating fine (and survived multiple reboots) before the suspension period.
Here is my
initctl list after a fresh reboot: http://pastebin.com/fcfcnxBU. Please do ask for specific details as I'm not entirely sure where to look for them (e.g. log files, debug artifacts, files and directories, etc.).
EDIT: some progress via tinkering:
It seems the filesystem and/or network stack is not started correctly when booting. When I do the following:
$ ifup --all $ initctl emit static-network-up $ initctl emit filesystem ... Ctrl-C to exit loop $ initctl emit local-filesystems
Then I get
$ runlevel >N 2
And my server services (at least most of them) are running normally.
I'll check if there is a single command of these that makes the boot init sequence continue normally.
ifup --allbrings up a
venet0:0which is tied to the VPS' public static IP.
emit static-network-updoes nothing.
and something called
network-interface-security (network-interface/lo) start/runningdisappears.