Build environment was operational for extended period of time, and left un-touched. Went to make a build and received an error, so rebooted.
Then noticed that the lxc used for git-repo daemon, git sources stored in seperate lxc, was failing to start within Virtual Environment 5.0-30, task status below:
Job for lxc@100.service failed because the control process exited with error code.
See "systemctl status lxc@100.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start lxc@100' failed: exit code 1
Ran systemctl status to get more information:
$ systemctl status lxc@100.service
● lxc@100.service - LXC Container: 100
Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/lxc@.service.d
└─pve-reboot.conf
Active: failed (Result: exit-code) since Thu 2018-12-13 17:05:18 PST; 1 weeks 0 days ago
Docs: man:lxc-start
man:lxc
Process: 20037 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)
Looked at the start-up script and ran it manually and received no error, but didn't see the LXC show up in the Virtual Environment. Not sure what's wrong, so then thought to attempt a restore from back-up. Restore failed, due to needing to log-in as root to have permission. Failed attempt removed LXC 100 from the Virtual Environment machine list, but 100 still shows up in the backups. Assumed I needed to run restore from console, since host OS doesn't have a root user login.
Tried console restore 100, failed. Left off --storage since I thought it would figure out destination based on information contained within back-up file:
$ sudo /usr/sbin/pct restore 100 vzdump-lxc-100-2018_12_15-18_00_01.tar.gz
[sudo] password for paadmin:
400 Parameter verification failed.
storage: storage 'local' does not support container directories
pct restore <vmid> <ostemplate> [OPTIONS]
Tried console create 102 to test folder, failed:
$ sudo /usr/sbin/pct create 102 /media/awcs/backups/dumps/vzdump-lxc-100-2018_12_15-18_00_01.tar.gz -storage /media/awcs/luciano_delete_me_too
400 Parameter verification failed.
storage: invalid format - storage ID '/media/awcs/luciano_delete_me_too' contains illegal characters
pct create <vmid> <ostemplate> [OPTIONS]
Documentation I'm following:
https://pve.proxmox.com/pve-docs/pct.1.html
Version information:
$ pveversion -v
proxmox-ve: 5.0-19 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.17-2-pve: 4.10.17-19
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-3
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
Not sure what to try next, thanks.
Then noticed that the lxc used for git-repo daemon, git sources stored in seperate lxc, was failing to start within Virtual Environment 5.0-30, task status below:
Job for lxc@100.service failed because the control process exited with error code.
See "systemctl status lxc@100.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start lxc@100' failed: exit code 1
Ran systemctl status to get more information:
$ systemctl status lxc@100.service
● lxc@100.service - LXC Container: 100
Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/lxc@.service.d
└─pve-reboot.conf
Active: failed (Result: exit-code) since Thu 2018-12-13 17:05:18 PST; 1 weeks 0 days ago
Docs: man:lxc-start
man:lxc
Process: 20037 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)
Looked at the start-up script and ran it manually and received no error, but didn't see the LXC show up in the Virtual Environment. Not sure what's wrong, so then thought to attempt a restore from back-up. Restore failed, due to needing to log-in as root to have permission. Failed attempt removed LXC 100 from the Virtual Environment machine list, but 100 still shows up in the backups. Assumed I needed to run restore from console, since host OS doesn't have a root user login.
Tried console restore 100, failed. Left off --storage since I thought it would figure out destination based on information contained within back-up file:
$ sudo /usr/sbin/pct restore 100 vzdump-lxc-100-2018_12_15-18_00_01.tar.gz
[sudo] password for paadmin:
400 Parameter verification failed.
storage: storage 'local' does not support container directories
pct restore <vmid> <ostemplate> [OPTIONS]
Tried console create 102 to test folder, failed:
$ sudo /usr/sbin/pct create 102 /media/awcs/backups/dumps/vzdump-lxc-100-2018_12_15-18_00_01.tar.gz -storage /media/awcs/luciano_delete_me_too
400 Parameter verification failed.
storage: invalid format - storage ID '/media/awcs/luciano_delete_me_too' contains illegal characters
pct create <vmid> <ostemplate> [OPTIONS]
Documentation I'm following:
https://pve.proxmox.com/pve-docs/pct.1.html
Version information:
$ pveversion -v
proxmox-ve: 5.0-19 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.17-2-pve: 4.10.17-19
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-3
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
Not sure what to try next, thanks.
