Error systemctl status degraded

@jmarher It would be better to use a different approach since you are not familiar with scp. Can you run the command less /tmp/lxc-103.log and copy the content into a file and post it here?

Eoin
 
  • Like
Reactions: jmarher
root@hp1:~# systemctl status pve-container@103.service
● pve-container@103.service - PVE LXC Container: 103
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor pr
Active: failed (Result: timeout) since Wed 2020-08-19 10:31:37 WEST; 21h ago
Docs: man:lxc-start
man:lxc
man:pct
Process: 28243 ExecStart=/usr/bin/lxc-start -n 103 (code=killed, signal=TERM)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/system-pve\x2dcontainer.slice/pve-container@103.service
└─28249 [lxc monitor] /var/lib/lxc 103

Aug 19 10:30:07 hp1 systemd[1]: Starting PVE LXC Container: 103...
Aug 19 10:31:37 hp1 systemd[1]: pve-container@103.service: Start operation timed
Aug 19 10:31:37 hp1 systemd[1]: Failed to start PVE LXC Container: 103.
Aug 19 10:31:37 hp1 systemd[1]: pve-container@103.service: Unit entered failed s
Aug 19 10:31:37 hp1 systemd[1]: pve-container@103.service: Failed with result 't
lines 1-16/16 (END)
 
oguz said:
we need the debug logs [0]. you can copy paste from your terminal if you're having trouble transfering the file

otherwise we have no information to help you...

also please post the full output of pveversion -v

[0]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_obtaining_debugging_logs
Click to expand...


root@hp1:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-50
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-25
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-19
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
root@hp1:~#
 
jmarher said:
root@hp1:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-50
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-25
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-19
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
root@hp1:~#
Click to expand...


pve 5.x is end of life, you need to update to the latest version to get the bugfixes and new features. please see here[0]

[0]: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
 
You must log in or register to reply here.
Top Bottom