Search results

Debian 8.11

HI! Got a such problem: now i'm trying to make backup in "stop" mode of CT. But reseaved timeout. Wot/s goin on? <pre>INFO: starting new backup job: vzdump 202 --mode stop --node GPR --compress lzo --storage local --remove 0 INFO: Starting Backup of VM 202 (lxc) INFO: status = running INFO...

network interfaces is ok even whith IPv6. Servise ssh failed to start during system starts. But 'service ssh start' starts manualy without problem. Now tryin to understand why.

This is result of running commands. root@GPR:/home/log#pct config 107 arch: amd64 cores: 4 hostname: Sentry memory: 4096 net0: name=eth0,bridge=vmbr1,hwaddr=A2:AE:78:2A:21:01,ip=dhcp,ip6=dhcp,type=veth ostype: debian rootfs: virthard1:107/vm-107-disk-0.raw,size=80G swap: 0 unprivileged: 1...

I'v try to update debian 8.11 to debian 9 on CT. All seems to be Ok, update process was sucssesful untill reboot. Now CT show status "active" but not accesible. Help please to resolve this problem! Debug log in file below

Formatting '/home/vm//images/200/vm-200-disk-0.raw', fmt=raw size=171798691840 mke2fs 1.43.4 (31-Jan-2017) Discarding device blocks: 4096/41943040 done Creating filesystem with 41943040 4k blocks and 10485760 inodes Filesystem UUID: eec446f4-4b0b-49f8-be78-222b3b15b411 Superblock backups stored...

thank you helped pct unmount 201 pct fsck 201

Job for pve-container@201.service failed because the control process exited with error code. See "systemctl status pve-container@201.service" and "journalctl -xe" for details. TASK ERROR: command 'systemctl start pve-container@201' failed: exit code 1 lxc-start 201 -o 201.log -l debug...