Hi,
I have an Ubuntun 14.04 LTS conainer which is no longer properly starting up. It hangs and installed services are not starting up (e.g. sshd etc).
If I start the server, I get the following message:
I can enter the server via $ vzctl enter 100 and console:
and nothing more is shown.
If I enter the container and make a top the following programms are running:
Unfortunately there are not entries in boot.log or any of the relevant logs regarding the boot (it seems that the file system is not yet ready at the point where it hangs such that the logs are not written).
The 100.conf looks like this:
Has anyone an idea where I should look further in order to localize the problem?
Is the error during start of the container (resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory) a problem?
I have an Ubuntun 14.04 LTS conainer which is no longer properly starting up. It hangs and installed services are not starting up (e.g. sshd etc).
If I start the server, I get the following message:
Code:
# vzctl start 100
Starting container ...
Container is unmounted
Container is mounted
Adding IP address(es): 192.168.0.217
Setting CPU units: 1000
Setting CPUs: 2
resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory
Container start in progress...I can enter the server via $ vzctl enter 100 and console:
Code:
# vzctl console 100
Attached to CT 100 (ESC . to detach)
* Starting Signal sysvinit that the rootfs is mounted [ OK ]
* Starting Populate /dev filesystem [ OK ]
* Stopping Send an event to indicate plymouth is up [ OK ]
* Stopping Populate /dev filesystem [ OK ]
* Starting Clean /tmp directory [ OK ]
* Starting Populate and link to /run filesystem [ OK ]
* Starting Track if upstart is running in a container [ OK ]
* Stopping Clean /tmp directory [ OK ]
* Stopping Populate and link to /run filesystem [ OK ]
* Starting load fallback graphics devices [ OK ]
* Starting workaround for missing events in container [ OK ]
* Starting load fallback graphics devices [fail]
* Stopping workaround for missing events in container [ OK ]
* Starting userspace bootsplash [ OK ]
* Starting Send an event to indicate plymouth is up [ OK ]
* Stopping userspace bootsplash [ OK ]
* Starting configure network device security [ OK ]
* Stopping Send an event to indicate plymouth is up [ OK ]
* Starting Mount network filesystems [ OK ]
* Stopping Mount network filesystems [ OK ]
* Starting Bridge socket events into upstart [ OK ]
* Starting configure network device [ OK ]
* Starting Initialize or finalize resolvconf [ OK ]If I enter the container and make a top the following programms are running:
Code:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 32924 2240 1452 S 0.0 0.1 0:00.03 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd/100
3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper/100
52 root 20 0 19508 1424 1008 S 0.0 0.1 0:00.09 plymouth-upstar
53 root 20 0 36836 1244 952 S 0.0 0.1 0:00.00 plymouthd
58 root 20 0 25872 1248 892 S 0.0 0.1 0:00.00 mountall
189 root 20 0 15212 616 416 S 0.0 0.0 0:00.00 upstart-socket-
386 root 20 0 25556 676 460 S 0.0 0.0 0:00.00 vzctl
387 root 20 0 18124 2008 1528 S 0.0 0.1 0:00.00 bash
399 root 20 0 19840 1480 1060 R 0.0 0.1 0:00.00 topUnfortunately there are not entries in boot.log or any of the relevant logs regarding the boot (it seems that the file system is not yet ready at the point where it hangs such that the logs are not written).
The 100.conf looks like this:
Code:
ONBOOT="no"
PHYSPAGES="0:2048M"
SWAPPAGES="0:524288"
KMEMSIZE="930M:1024M"
DCACHESIZE="465M:512M"
LOCKEDPAGES="1024M"
PRIVVMPAGES="unlimited"
SHMPAGES="unlimited"
NUMPROC="unlimited"
VMGUARPAGES="0:unlimited"
OOMGUARPAGES="0:unlimited"
NUMTCPSOCK="unlimited"
NUMFLOCK="unlimited"
NUMPTY="unlimited"
NUMSIGINFO="unlimited"
TCPSNDBUF="unlimited"
TCPRCVBUF="unlimited"
OTHERSOCKBUF="unlimited"
DGRAMRCVBUF="unlimited"
NUMOTHERSOCK="unlimited"
NUMFILE="unlimited"
NUMIPTENT="unlimited"
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="20G:22G"
DISKINODES="4000000:4400000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"
# CPU fair scheduler parameter
CPUUNITS="1000"
CPUS="2"
HOSTNAME="stable"
NAMESERVER="8.8.8.8"
IP_ADDRESS="192.168.0.217"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/100"
OSTEMPLATE="ubuntu-14.04-x86_64-v1.tar.gz"Has anyone an idea where I should look further in order to localize the problem?
Is the error during start of the container (resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory) a problem?