4.0 Unable to get PID: CT won't start

NerdUno

Member
Sep 13, 2009
30
0
6
Trying out 4.0. VMs work great! Setting up CT using CentOS 6 template. Starts properly. Then we load a bunch of CentOS RPMs with yum and reboot. Message flashes that "Unable to get PID for CT 100" and startup fails. Any ideas??
 
works here - so you use our lxc centos 6 template?
 
Correct. Using the centos 6 template. The Ubuntu 14 one works fine so this appears to be a CentOS problem. We add several hundred packages from the CentOS repo to bring our servers up to what's needed for our PBX platforms. Thought maybe it was the kernel quirks, but eliminating the kernel issues did not fix the problem.
 
please tell exactly how I can trigger the issue here.
 
The easy way would be just to load our script and run it. You can save some time by editing the script once it's untarred and adding an exit command at about line 194. This will let you run through all of the yum commands and exit just before Asterisk, etc. are built. Then reboot and the error will appear.


yum -y install net-tools nano wget tar

wget http://incrediblepbx.com/incrediblepbx13-12.2-centos.tar.gz
tar zxvf incrediblepbx
*
./IncrediblePBX*



 
this install script is not really optimized for LXC, seems to install a lot of not needed stuff.
 
It's necessarily generic because we support a half dozen different RHEL flavors and about the same number of RHEL versions. ;)
 
It's necessarily generic because we support a half dozen different RHEL flavors and about the same number of RHEL versions. ;)

you can easily detect the running platform with a script and then you can act accordingly.

one of the benefits of a container is a lean installation. your script seems to install almost everything (still installing in the background...), so in this case I see no benefit and would choose a VM for this - why do you want to run this as container?
 
We already have an OpenVZ template, but it's a very old version of everything. What we typically do is install the kitchen sink and then remove packages before creating the container. Installing CentOS packages from the CentOS repo really shouldn't break CentOS, barebones or not. :cool:
 
one of the benefits of a container is a lean installation. your script seems to install almost everything (still installing in the background...), so in this case I see no benefit and would choose a VM for this - why do you want to run this as container?

I'm curious if you believe this is a design flaw in Linux Containers. We never saw this limitation with OpenVZ templates. Frankly, we haven't seen it on any other virtualization platform, and we test almost all of them. I understand running out of RAM or disk space but "too many RPMs" is a new one. Are there package limitations in the Linux Container design that don't exist with other virtualization platforms?
 
to get more debug info, start the container from the host command-line, with:

> lxc-start -lDEBUG -o YOURLOGFILE.log -F -n 118

of course, replace 118 with your CTID
 
  • Like
Reactions: user843
to get more debug info, start the container from the host command-line, with:

> lxc-start -lDEBUG -o YOURLOGFILE.log -F -n 118

Here are the problems from the log. This was after loading nothing but RPMs from the CentOS repo:

lxc-start 1444757316.105 DEBUG bdev - bdev.c:find_fstype_cb:151 - trying to mount '/dev/loop0'->'/usr/lib/x86_64-linux-gnu/lxc/rootfs' with fstype 'ext3'
lxc-start 1444757316.105 DEBUG bdev - bdev.c:find_fstype_cb:159 - mount failed with error: Invalid argument
lxc-start 1444757316.105 DEBUG bdev - bdev.c:find_fstype_cb:151 - trying to mount '/dev/loop0'->'/usr/lib/x86_64-linux-gnu/lxc/rootfs' with fstype 'ext2'
lxc-start 1444757316.105 DEBUG bdev - bdev.c:find_fstype_cb:159 - mount failed with error: Invalid argument
lxc-start 1444757316.105 DEBUG bdev - bdev.c:find_fstype_cb:151 - trying to mount '/dev/loop0'->'/usr/lib/x86_64-linux-gnu/lxc/rootfs' with fstype 'ext4'
lxc-start 1444757316.110 INFO bdev - bdev.c:find_fstype_cb:167 - mounted '/dev/loop0' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs', with fstype 'ext4'
lxc-start 1444757316.110 DEBUG lxc_conf - conf.c:setup_rootfs:1284 - mounted 'loop:/var/lib/vz/images/102/vm-102-disk-1.raw' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs'
lxc-start 1444757316.110 INFO lxc_conf - conf.c:setup_utsname:919 - 'incredtest.wardmundy.net' hostname has been setup
lxc-start 1444757316.121 DEBUG lxc_conf - conf.c:setup_hw_addr:2244 - mac address '8A:03:C0:8A:6B:8E' on 'eth0' has been setup
lxc-start 1444757316.121 DEBUG lxc_conf - conf.c:setup_netdev:2471 - 'eth0' has been setup
lxc-start 1444757316.121 INFO lxc_conf - conf.c:setup_network:2492 - network has been setup
lxc-start 1444757316.121 INFO lxc_conf - conf.c:mount_autodev:1148 - Mounting /dev under /usr/lib/x86_64-linux-gnu/lxc/rootfs
lxc-start 1444757316.121 INFO lxc_conf - conf.c:mount_autodev:1169 - Mounted tmpfs onto /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev
lxc-start 1444757316.121 INFO lxc_conf - conf.c:mount_autodev:1187 - Mounted /dev under /usr/lib/x86_64-linux-gnu/lxc/rootfs
lxc-start 1444757316.122 DEBUG lxc_conf - conf.c:mount_entry:1727 - remounting /sys/fs/fuse/connections on /usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections to respect bind or remount options
lxc-start 1444757316.122 DEBUG lxc_conf - conf.c:mount_entry:1742 - (at remount) flags for /sys/fs/fuse/connections was 4096, required extra flags are 0
lxc-start 1444757316.122 DEBUG lxc_conf - conf.c:mount_entry:1751 - mountflags already was 4096, skipping remount
lxc-start 1444757316.122 DEBUG lxc_conf - conf.c:mount_entry:1777 - mounted '/sys/fs/fuse/connections' on '/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections', type 'none'
lxc-start 1444757316.122 INFO lxc_conf - conf.c:mount_file_entries:2026 - mount points have been setup
lxc-start 1444757316.122 INFO lxc_conf - conf.c:run_script_argv:356 - Executing script '/usr/share/lxc/hooks/lxc-pve-mount-hook' for container '102', config section 'lxc'
lxc-start 1444757316.493 ERROR lxc_conf - conf.c:run_buffer:336 - Script exited with status 255
lxc-start 1444757316.493 ERROR lxc_conf - conf.c:lxc_setup:3827 - failed to run mount hooks for container '102'.
lxc-start 1444757316.493 ERROR lxc_start - start.c:do_start:702 - failed to setup the container
lxc-start 1444757316.493 ERROR lxc_sync - sync.c:__sync_wait:51 - invalid sequence number 1. expected 2
lxc-start 1444757316.493 WARN lxc_conf - conf.c:lxc_delete_network:2995 - failed to remove interface 'eth0'
lxc-start 1444757316.549 ERROR lxc_start - start.c:__lxc_start:1172 - failed to spawn '102'
lxc-start 1444757316.549 INFO lxc_conf - conf.c:run_script_argv:356 - Executing script '/usr/share/lxc/hooks/lxc-pve-poststop-hook' for container '102', config section 'lxc'
lxc-start 1444757316.913 ERROR lxc_start_ui - lxc_start.c:main:344 - The container failed to start.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!