Article ID: 123200, created on Oct 21, 2014, last review on Oct 21, 2014

  • Applies to:
  • Virtuozzo 6.0


Ubuntu\Debian container changes status to mounted right after the start.

In container's root you may find fresh core files that originate from "sulogin":

[root@pcs ~]# date
Tue Oct 21 19:56:10 CEST 2014
[root@pcs ~]# ls -lt /vz/root/101934/core*
-rw------- 1 root root 48451584 Oct 21 19:55 /vz/root/101934/core.86
-rw------- 1 root root 19480576 Oct 21 19:42 /vz/root/101934/core.96
-rw------- 1 root root 19480576 Oct 21 19:41 /vz/root/101934/core.95
-rw------- 1 root root 19480576 Oct 21 15:40 /vz/root/101934/core.98
-rw------- 1 root root 48451584 Apr 27 22:54 /vz/root/101934/core.85
[root@pcs ~]# file /vz/root/101934/core.86
/vz/root/101934/core.86: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/sbin/sulogin'
[root@pcs ~]#


/etc/passwd file is empty, or does not contain record for the root user. Therefore init process failed to impersonate root user, causing sulogin to crash.


To get container running you should fix /etc/passwd file, most likely you'll be able to copy it from a backup which is usually held in the same directory as /etc/passwd-. If backup is not present, you may copy the file from any other existing or new container.

Search Words



c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF