fail to start a CT

I

iruindegi

Well-Known Member
Proxmox Subscriber
Aug 26, 2016
52
0
46
Zarautz
Hi,

I can't start a CT from the web so I tried within the console:

Code: 
root@pve:~# pct start 829
root@pve:~# pct start 829
Job for pve-container@829.service failed because the control process exited with error code.
See "systemctl status pve-container@829.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@829' failed: exit code 1


root@pve:~# systemctl status pve-container@829.service
● pve-container@829.service - PVE LXC Container: 829
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-03-01 13:59:59 CET; 1min 33s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 26004 ExecStart=/usr/bin/lxc-start -n 829 (code=exited, status=1/FAILURE)

mar 01 13:59:58 pve systemd[1]: Starting PVE LXC Container: 829...
mar 01 13:59:59 pve lxc-start[26004]: lxc-start: 829: lxccontainer.c: wait_on_daemonized_start: 751 No such file or di
mar 01 13:59:59 pve lxc-start[26004]: lxc-start: 829: tools/lxc_start.c: main: 371 The container failed to start.
mar 01 13:59:59 pve lxc-start[26004]: lxc-start: 829: tools/lxc_start.c: main: 373 To get more details, run the contai
mar 01 13:59:59 pve lxc-start[26004]: lxc-start: 829: tools/lxc_start.c: main: 375 Additional information can be obtai
mar 01 13:59:59 pve systemd[1]: pve-container@829.service: Control process exited, code=exited status=1
mar 01 13:59:59 pve systemd[1]: Failed to start PVE LXC Container: 829.
mar 01 13:59:59 pve systemd[1]: pve-container@829.service: Unit entered failed state.
mar 01 13:59:59 pve systemd[1]: pve-container@829.service: Failed with result 'exit-code'.



root@pve:~# journalctl -xe
-- The result is failed.
mar 01 13:59:59 pve systemd[1]: pve-container@829.service: Unit entered failed state.
mar 01 13:59:59 pve pct[26001]: command 'systemctl start pve-container@829' failed: exit code 1
mar 01 13:59:59 pve systemd[1]: pve-container@829.service: Failed with result 'exit-code'.
mar 01 13:59:59 pve pct[25997]: <root@pam> end task UPID:pve:00006591:01197BEB:5A97F94E:vzstart:829:root@pam: command 
mar 01 14:00:00 pve systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit pvesr.service has begun starting up.
mar 01 14:00:00 pve systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit pvesr.service has finished starting up.
-- 
-- The start-up result is done.
mar 01 14:00:05 pve telegraf[1785]: 2018-03-01T13:00:05Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:00:05 pve telegraf[1785]: 2018-03-01T13:00:05Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:00:15 pve telegraf[1785]: 2018-03-01T13:00:15Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:00:15 pve telegraf[1785]: 2018-03-01T13:00:15Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:00:25 pve telegraf[1785]: 2018-03-01T13:00:25Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:00:25 pve telegraf[1785]: 2018-03-01T13:00:25Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:00:35 pve telegraf[1785]: 2018-03-01T13:00:35Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:00:35 pve telegraf[1785]: 2018-03-01T13:00:35Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:00:36 pve postfix/qmgr[2146]: 0DE41580152: from=<root@pve.pasaia.net>, size=2602, nrcpt=1 (queue active)
mar 01 14:00:36 pve postfix/qmgr[2146]: 707D2580F2D: from=<root@pve.pasaia.net>, size=3687, nrcpt=1 (queue active)
mar 01 14:00:36 pve postfix/smtp[26564]: connect to pasaia.net[172.28.64.23]:25: Connection refused
mar 01 14:00:36 pve postfix/smtp[26564]: 0DE41580152: to=<informatika@pasaia.net>, relay=none, delay=189645, delays=18
mar 01 14:00:36 pve postfix/smtp[26565]: connect to pasaia.net[172.28.64.23]:25: Connection refused
mar 01 14:00:36 pve postfix/smtp[26565]: 707D2580F2D: to=<informatika@pasaia.net>, relay=none, delay=34801, delays=348
mar 01 14:00:45 pve telegraf[1785]: 2018-03-01T13:00:45Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:00:45 pve telegraf[1785]: 2018-03-01T13:00:45Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:00:55 pve telegraf[1785]: 2018-03-01T13:00:55Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:00:55 pve telegraf[1785]: 2018-03-01T13:00:55Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:01:00 pve systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit pvesr.service has begun starting up.
mar 01 14:01:00 pve systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit pvesr.service has finished starting up.
-- 
-- The start-up result is done.
mar 01 14:01:05 pve telegraf[1785]: 2018-03-01T13:01:05Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:01:05 pve telegraf[1785]: 2018-03-01T13:01:05Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:01:15 pve telegraf[1785]: 2018-03-01T13:01:15Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:01:15 pve telegraf[1785]: 2018-03-01T13:01:15Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:01:25 pve telegraf[1785]: 2018-03-01T13:01:25Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:01:25 pve telegraf[1785]: 2018-03-01T13:01:25Z E! Error writing to output [influxdb]: Could not write to any
mar 01 14:01:35 pve telegraf[1785]: 2018-03-01T13:01:35Z E! InfluxDB Output Error: Post http://172.28.64.248:8086/writ
mar 01 14:01:35 pve telegraf[1785]: 2018-03-01T13:01:35Z E! Error writing to output [influxdb]: Could not write to any
root@pve:~#


Any help or clue? Other VM and CTs are working ok
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back