Proxmox 4.0 CT deployment error

[sgt awesomesauce]

Hi all,

I'm having an issue deploying a container on a local ZFS storage.

CT 104 create:


[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]extracting archive '/var/lib/vz/template/cache/ubuntu-15.04-standard_15.04-1_amd64.tar.gz'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Total bytes read: 521256960 (498MiB, 53MiB/s)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Detected container architecture: amd64[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_dsa_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_ed25519_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_ecdsa_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating SSH host key 'ssh_host_rsa_key' - this may take some time ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Use of uninitialized value $path in pattern match (m//) at /usr/share/perl5/PVE/LXC.pm line 1969.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK OK
[/FONT][/COLOR]

I've deployed 2 containers so far and they've all gone off without any issues, so I'm not sure what's going on here. I've allocated 4096GB of disk space to the container. I'm using 3x2TB disks in a simple zpool for now, my hard drive space is reported by proxmox as 5.22TB free, and df -h verifies this. The container is created successfully, for some reason, but it won't start.

[COLOR=#000000][FONT=tahoma]
CT 104 start:

Use of uninitialized value $path in concatenation (.) or string at /usr/share/perl5/PVE/LXC.pm line 1110.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]lxc-start: lxc_start.c: main: 344 The container failed to start.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK OK

running in foreground mode: 

[/FONT][/COLOR]root@proxmox0:~# lxc-start -F --name storage
lxc-start: lxc_start.c: main: 295 Executing '/sbin/init' with no configuration file may crash the host

I'm not sure if there's anything else that's relevant.

 

[dietmar]

What is the output of

# pveversion -v

 

[sgt awesomesauce]

# pveversion -v
proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve)
pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0)
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-22
qemu-server: 4.0-30
pve-firmware: 1.1-7
libpve-common-perl: 4.0-29
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-25
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-9
pve-container: 1.0-6
pve-firewall: 2.0-12
pve-ha-manager: 1.0-9
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1
zfsutils: 0.6.5-pve4~jessie

 

[wbumiller]

Your pve-container package is at 1.0-6. Try updating, there have been updates to that section of the code since then.

 

[sgt awesomesauce]

It's working now.

I don't have an enterprise subscription, so pve-enterprise.list was incorrectly configured for me.

This was causing 403 errors on apt-get update, which in turn caused apt to incorrectly report an up to date system. Updating that as the package repositories wiki page suggests, to pve-no-subscription, fixed my issue.

Thanks for the help!