LXC suddenly not booting

S

scarletdevil19

New Member
Aug 8, 2024
7
1
3
As the title states my qbittorrow L:XC suddenly won't boot no errors nothing strange it shows green but I can't access the console from proxmox nor can I acess SSH, in addition netwoprking seems to be down for it as well as theres no IP in the network tab and it's not appearing on my router's Client List

Here is what I can see from syslog on the node

Code: 
Apr 04 05:19:53 APTX-4869-Fujitsu2 pvedaemon[116776]: requesting reboot of CT 122: UPID:APTX-4869-Fujitsu2:0001C828:0012ED43:69D02EF9:vzreboot:122:root@pam:
Apr 04 05:19:53 APTX-4869-Fujitsu2 pvedaemon[100494]: <root@pam> starting task UPID:APTX-4869-Fujitsu2:0001C828:0012ED43:69D02EF9:vzreboot:122:root@pam:
Apr 04 05:19:54 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(veth122i0) entered disabled state
Apr 04 05:19:54 APTX-4869-Fujitsu2 kernel: veth122i0 (unregistering): left allmulticast mode
Apr 04 05:19:54 APTX-4869-Fujitsu2 kernel: veth122i0 (unregistering): left promiscuous mode
Apr 04 05:19:54 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(veth122i0) entered disabled state
Apr 04 05:19:54 APTX-4869-Fujitsu2 kernel: audit: type=1400 audit(1775251194.465:161): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-122_</var/lib/lxc>" pid=116855 comm="apparmor_parser"
Apr 04 05:19:54 APTX-4869-Fujitsu2 pvestatd[1200]: unable to get PID for CT 122 (not running?)
Apr 04 05:19:55 APTX-4869-Fujitsu2 kernel: EXT4-fs (loop3): unmounting filesystem 1b754915-63bc-4f21-9a70-7a96aac99f41.
Apr 04 05:19:55 APTX-4869-Fujitsu2 sshd-session[115471]: syslogin_perform_logout: logout() returned an error
Apr 04 05:19:55 APTX-4869-Fujitsu2 sshd-session[115488]: Received disconnect from 192.168.10.28 port 47294:11: disconnected by user
Apr 04 05:19:55 APTX-4869-Fujitsu2 sshd-session[115488]: Disconnected from user root 192.168.10.28 port 47294
Apr 04 05:19:55 APTX-4869-Fujitsu2 systemd[1]: session-65.scope: Deactivated successfully.
Apr 04 05:19:55 APTX-4869-Fujitsu2 sshd-session[115471]: pam_unix(sshd:session): session closed for user root
Apr 04 05:19:55 APTX-4869-Fujitsu2 systemd-logind[734]: Removed session 65.
Apr 04 05:19:55 APTX-4869-Fujitsu2 systemd[1]: session-68.scope: Deactivated successfully.
Apr 04 05:19:55 APTX-4869-Fujitsu2 systemd-logind[734]: Session 68 logged out. Waiting for processes to exit.
Apr 04 05:19:55 APTX-4869-Fujitsu2 systemd-logind[734]: Removed session 68.
Apr 04 05:19:55 APTX-4869-Fujitsu2 systemd[1]: pve-container@122.service: Deactivated successfully.
Apr 04 05:19:56 APTX-4869-Fujitsu2 systemd[1]: pve-container@122.service: Consumed 1.114s CPU time, 91.6M memory peak.
Apr 04 05:19:56 APTX-4869-Fujitsu2 systemd[1]: Started pve-container@122.service - PVE LXC Container: 122.
Apr 04 05:19:56 APTX-4869-Fujitsu2 kernel: loop3: detected capacity change from 0 to 50331648
Apr 04 05:19:56 APTX-4869-Fujitsu2 kernel: EXT4-fs (loop3): mounted filesystem 1b754915-63bc-4f21-9a70-7a96aac99f41 r/w with ordered data mode. Quota mode: none.
Apr 04 05:19:57 APTX-4869-Fujitsu2 kernel: audit: type=1400 audit(1775251197.155:162): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-122_</var/lib/lxc>" pid=116932 comm="apparmor_parser"
Apr 04 05:19:57 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251197.1981] manager: (veth122i0): new Veth device (/org/freedesktop/NetworkManager/Devices/31)
Apr 04 05:19:58 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(veth122i0) entered blocking state
Apr 04 05:19:58 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(veth122i0) entered disabled state
Apr 04 05:19:58 APTX-4869-Fujitsu2 kernel: veth122i0: entered allmulticast mode
Apr 04 05:19:58 APTX-4869-Fujitsu2 kernel: veth122i0: entered promiscuous mode
Apr 04 05:19:58 APTX-4869-Fujitsu2 kernel: eth0: renamed from veth2Ony4s
Apr 04 05:19:58 APTX-4869-Fujitsu2 pvedaemon[100494]: <root@pam> end task UPID:APTX-4869-Fujitsu2:0001C828:0012ED43:69D02EF9:vzreboot:122:root@pam: OK
Apr 04 05:19:58 APTX-4869-Fujitsu2 kernel: apparmor mqueue disconnected TODO
Apr 04 05:19:58 APTX-4869-Fujitsu2 kernel: apparmor mqueue disconnected TODO
 
Here is a syslog of a fresh start instead of a reboot

Code: 
Apr 04 05:29:56 APTX-4869-Fujitsu2 pvedaemon[132425]: <root@pam> starting task UPID:APTX-4869-Fujitsu2:00022AD6:0013D8AA:69D03154:vzstart:122:root@pam:
Apr 04 05:29:56 APTX-4869-Fujitsu2 pvedaemon[142038]: starting CT 122: UPID:APTX-4869-Fujitsu2:00022AD6:0013D8AA:69D03154:vzstart:122:root@pam:
Apr 04 05:29:56 APTX-4869-Fujitsu2 systemd[1]: Started pve-container@122.service - PVE LXC Container: 122.
Apr 04 05:29:57 APTX-4869-Fujitsu2 kernel: loop3: detected capacity change from 0 to 50331648
Apr 04 05:29:57 APTX-4869-Fujitsu2 kernel: EXT4-fs (loop3): mounted filesystem 1b754915-63bc-4f21-9a70-7a96aac99f41 r/w with ordered data mode. Quota mode: none.
Apr 04 05:29:57 APTX-4869-Fujitsu2 kernel: audit: type=1400 audit(1775251797.757:167): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-122_</var/lib/lxc>" pid=142067 comm="apparmor_parser"
Apr 04 05:29:57 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251797.7906] manager: (veth122i0): new Veth device (/org/freedesktop/NetworkManager/Devices/36)
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.6696] manager: (fwbr122i0): new Bridge device (/org/freedesktop/NetworkManager/Devices/37)
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.6944] manager: (fwpr122p0): new Veth device (/org/freedesktop/NetworkManager/Devices/38)
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.6959] manager: (fwln122i0): new Veth device (/org/freedesktop/NetworkManager/Devices/39)
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7173] device (fwpr122p0): carrier: link connected
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7178] device (fwln122i0): carrier: link connected
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(fwpr122p0) entered blocking state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(fwpr122p0) entered disabled state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwpr122p0: entered allmulticast mode
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwpr122p0: entered promiscuous mode
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(fwpr122p0) entered blocking state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: vmbr0: port 6(fwpr122p0) entered forwarding state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwbr122i0: port 1(fwln122i0) entered blocking state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwbr122i0: port 1(fwln122i0) entered disabled state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwln122i0: entered allmulticast mode
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwln122i0: entered promiscuous mode
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwbr122i0: port 1(fwln122i0) entered blocking state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwbr122i0: port 1(fwln122i0) entered forwarding state
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7590] device (fwbr122i0): carrier: link connected
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7620] device (fwbr122i0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7629] device (fwbr122i0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7637] device (fwbr122i0): Activation: starting connection 'fwbr122i0' (e1b4ae65-d02e-4653-a79a-a716f40481f1)
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7639] device (fwbr122i0): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 dbus-daemon[715]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=764 comm="/usr/sbin/NetworkManager --no-daemon" label="unconfined")
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7642] device (fwbr122i0): state change: prepare -> config (reason 'none', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7644] device (fwbr122i0): state change: config -> ip-config (reason 'none', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.7646] device (fwbr122i0): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwbr122i0: port 2(veth122i0) entered blocking state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: fwbr122i0: port 2(veth122i0) entered disabled state
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: veth122i0: entered allmulticast mode
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: veth122i0: entered promiscuous mode
Apr 04 05:29:58 APTX-4869-Fujitsu2 dbus-daemon[715]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 04 05:29:58 APTX-4869-Fujitsu2 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.8105] device (fwbr122i0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.8108] device (fwbr122i0): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.8112] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 04 05:29:58 APTX-4869-Fujitsu2 NetworkManager[764]: <info>  [1775251798.8116] device (fwbr122i0): Activation: successful, device activated.
Apr 04 05:29:58 APTX-4869-Fujitsu2 kernel: eth0: renamed from vethwJwur6
Apr 04 05:29:59 APTX-4869-Fujitsu2 pvedaemon[132425]: <root@pam> end task UPID:APTX-4869-Fujitsu2:00022AD6:0013D8AA:69D03154:vzstart:122:root@pam: OK
 
You must log in or register to reply here.
Top Bottom
Back