Article ID: 122953, created on Sep 19, 2014, last review on Sep 19, 2014

  • Applies to:
  • Virtuozzo 6.0


When a debian container is restarted, the services inside do not start automatically and it is necessary to start them manually.

Attempting to query the current runlevel inside the container returns unknown:

# runlevel


/sbin/initctl binary was modified/corrupted inside the container.


Confirm that /sbin/initctl exists, is a binary, e.g:


# which initctl
# dpkg -S /sbin/initctl
upstart: /sbin/initctl
# ls -al /sbin/init*
-rwxr-xr-x 1 root root 224568 Dec 10  2012 /sbin/init
-rwxr-xr-x 1 root root 159592 Dec 10  2012 /sbin/initctl
# file -sk /sbin/initctl
/sbin/initctl: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0x26fc1e0b5ef50fa83a4ca49659578df73e192fd6, stripped

Not correct:

# which initctl
# dpkg  -S /sbin/initctl
local diversion from: /sbin/initctl
local diversion to: /sbin/initctl.distrib
upstart: /sbin/initctl
# ls -al /sbin/init*
-rwxr-xr-x 1 root root 224568 Dec 10  2012 /sbin/init
lrwxrwxrwx 1 root root      9 Sep 12 16:15 /sbin/initctl -> /bin/true
-rwxr-xr-x 1 root root 159592 Dec 10  2012 /sbin/initctl.distrib

Reinstall upstart package if necessary.

Search Words


no service started

services do not start after container restart

runlevel unknown

autostart service

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF