CT fails to start reaching t/o

than0s

Member
Feb 16, 2018
3
0
6
37
Any idea regarding this error? All resources found are pointing to upgrade but I am already running the latest version.

Code:
Virtual Environment 5.1-52
Container 106 (nginx1a) on node 'nuc1'
Logs
()
Job for pve-container@113.service failed because a timeout was exceeded.
See "systemctl status pve-container@113.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@113' failed: exit code 1

Code:
root@nuc1:~# systemctl status pve-container@113.service
● pve-container@113.service - PVE LXC Container: 113
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: timeout) since Sun 2018-05-13 18:23:40 EEST; 3min 47s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 8654 ExecStart=/usr/bin/lxc-start -n 113 (code=killed, signal=TERM)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/system-pve\x2dcontainer.slice/pve-container@113.service

May 13 18:22:10 nuc1 systemd[1]: Starting PVE LXC Container: 113...
May 13 18:23:40 nuc1 systemd[1]: pve-container@113.service: Start operation timed out. Terminating.
May 13 18:23:40 nuc1 systemd[1]: Failed to start PVE LXC Container: 113.
May 13 18:23:40 nuc1 systemd[1]: pve-container@113.service: Unit entered failed state.
May 13 18:23:40 nuc1 systemd[1]: pve-container@113.service: Failed with result 'timeout'.
root@nuc1:~# journalctl -xe
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
May 13 18:25:30 nuc1 systemd[9046]: Startup finished in 10ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd

-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required KERNEL_USEC microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 10192 microseconds.
May 13 18:25:30 nuc1 systemd[1]: Started User Manager for UID 0.
-- Subject: Unit user@0.service has finished start-up
-- Defined-By: systemd

-- 
-- Unit user@0.service has finished starting up.
-- 
-- The start-up result is done.
May 13 18:25:55 nuc1 kernel: JBD2: Invalid checksum recovering block 1 in log
May 13 18:25:55 nuc1 kernel: JBD2: recovery failed
May 13 18:25:55 nuc1 kernel: EXT4-fs (loop2): error loading journal
May 13 18:25:55 nuc1 pvestatd[1911]: unable to get PID for CT 113 (not running?)
May 13 18:25:55 nuc1 pvedaemon[1935]: unable to get PID for CT 113 (not running?)
May 13 18:25:55 nuc1 pvestatd[1911]: status update time (218.686 seconds)
May 13 18:25:55 nuc1 pmxcfs[1750]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/nuc1/local: -1
May 13 18:25:55 nuc1 pmxcfs[1750]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/nuc1/local: /var/lib/rrdcached/db/pve2-storage/nuc1/local: illegal attempt to update using time 1526225155 when last update tim
May 13 18:25:55 nuc1 pmxcfs[1750]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/nuc1/local-lvm: -1
May 13 18:25:55 nuc1 pmxcfs[1750]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/nuc1/local-lvm: /var/lib/rrdcached/db/pve2-storage/nuc1/local-lvm: illegal attempt to update using time 1526225155 when last up
May 13 18:25:55 nuc1 pmxcfs[1750]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/nuc1/nfs1: -1
May 13 18:25:55 nuc1 pmxcfs[1750]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/nuc1/nfs1: /var/lib/rrdcached/db/pve2-storage/nuc1/nfs1: illegal attempt to update using time 1526225155 when last update time 
May 13 18:26:00 nuc1 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd

-- 
-- Unit pvesr.service has begun starting up.
May 13 18:26:00 nuc1 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd

-- 
-- Unit pvesr.service has finished starting up.
-- 
-- The start-up result is done.
May 13 18:27:00 nuc1 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd

-- 
-- Unit pvesr.service has begun starting up.
May 13 18:27:00 nuc1 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd

-- 
-- Unit pvesr.service has finished starting up.
-- 
-- The start-up result is done.
root@nuc1:~#
 

Richard

Proxmox Staff Member
Staff member
Mar 6, 2015
876
40
48
Austria
Any idea regarding this error? All resources found are pointing to upgrade but I am already running the latest version.

Code:
Virtual Environment 5.1-52
Container 106 (nginx1a) on node 'nuc1'
Logs
()
Job for pve-container@113.service failed because a timeout was exceeded.
See "systemctl status pve-container@113.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@113' failed: exit code 1



[/code]


Container start fails, probably.


Try to start it in the foreground from Proxmox server console by

Code:
lxc-start -F -n 106

and look what happens.
 

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 your own in 60 seconds.

Buy now!