Details
-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Duplicate
-
Fix Version/s: OpenVZ-legacy
-
Component/s: Containers::Userspace
-
Security Level: Public
-
Environment:Operating System: Debian
Platform: x86_64 (AMD64)
-
External issue URL:
-
External issue ID:3175
Description
I'm not sure if this problem is related to vzctl, but I have had several containers failing for the past week. Everything looks good when starting the container, but running vzlist reveals that only 3 processes are running.
root@server2 /vz/root # vzctl exec 205 ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 10608 12 ? Ss 20:42 0:00 init boot
root 2 0.0 0.0 0 0 ? S 20:42 0:00 [kthreadd/205]
root 3 0.0 0.0 0 0 ? S 20:42 0:00 [khelper/205]
root 46 0.0 0.1 15268 1132 ? Rs 21:02 0:00 ps aux
root@server2 /vz/root # vzctl exec 205 mount
/dev/ploop13616p1 on / type ext4 (rw,relatime,barrier=1,data=ordered,balloon_ino=12)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/run never gets mounted, so I guess the reason why the container isn't starting, is because /run/initctl is not existing.
When stopping the container, I get the following error:
"Child XXXXXX exited with status 1"
This has been happening to a lot of my debian 7 containers, all running in ploop images. The same thing has been happening on two differen HNs, both running debian 7 + RHEL6 2.6.32-openvz-042stab102.9-amd64 + latest version of utilities from deb repositories.
root@server2 /vz/root # vzctl exec 205 ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 10608 12 ? Ss 20:42 0:00 init boot
root 2 0.0 0.0 0 0 ? S 20:42 0:00 [kthreadd/205]
root 3 0.0 0.0 0 0 ? S 20:42 0:00 [khelper/205]
root 46 0.0 0.1 15268 1132 ? Rs 21:02 0:00 ps aux
root@server2 /vz/root # vzctl exec 205 mount
/dev/ploop13616p1 on / type ext4 (rw,relatime,barrier=1,data=ordered,balloon_ino=12)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/run never gets mounted, so I guess the reason why the container isn't starting, is because /run/initctl is not existing.
When stopping the container, I get the following error:
"Child XXXXXX exited with status 1"
This has been happening to a lot of my debian 7 containers, all running in ploop images. The same thing has been happening on two differen HNs, both running debian 7 + RHEL6 2.6.32-openvz-042stab102.9-amd64 + latest version of utilities from deb repositories.
Attachments
Issue Links
- duplicates
-
OVZ-5739 debian 7 dist-upgrade removes upstart and installs sysvinit
- Closed