Proxmox can not reboot CT

A

Artem.ws

Member
Dec 20, 2021
27
1
8
35
Hello everyone! I Installed latest proxmox 7.1.2 and i got problem with lxc CT. So, for example. I downloaded template centos 8, install it, then install some software (nginx, php-fpm) and enter in terminal (in CT) command - reboot. After that, i can ping my CT, but i can not enter into ssh or etc. In proxmox container have status running, but if i enter to console, i see this (screenshot 1)

Screenshot_2.png

Same problem, if i reboot via proxmox WEB.

But "Stop" and after that "Start" working normally. So i can not reboot my CT via proxmox or inside CT.
 
Sometimes, reboot successful, but not at once, approx 2-3 minutes. In log, i see this

Code: 
Dec 20 20:52:45 asus pvedaemon[274319]: requesting reboot of CT 101: UPID:asus:00042F8F:003554A7:61C08AAD:vzreboot:101:root@pam:
Dec 20 20:52:45 asus pvedaemon[254543]: <root@pam> starting task UPID:asus:00042F8F:003554A7:61C08AAD:vzreboot:101:root@pam:
Dec 20 20:53:45 asus kernel: fwbr101i0: port 2(veth101i0) entered disabled state
Dec 20 20:53:45 asus kernel: device veth101i0 left promiscuous mode
Dec 20 20:53:45 asus kernel: fwbr101i0: port 2(veth101i0) entered disabled state
Dec 20 20:53:45 asus pvedaemon[271008]: <root@pam> end task UPID:asus:00042F38:00355214:61C08AA6:vncproxy:101:root@pam: OK
Dec 20 20:53:45 asus audit[274952]: AVC apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=274952 comm="apparmor_parser"
Dec 20 20:53:45 asus kernel: audit: type=1400 audit(1640008425.512:58): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=274952 comm="apparmor_parser"
Dec 20 20:53:46 asus kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Dec 20 20:53:46 asus kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Dec 20 20:53:46 asus kernel: device fwln101i0 left promiscuous mode
Dec 20 20:53:46 asus kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Dec 20 20:53:46 asus kernel: device fwpr101p0 left promiscuous mode
Dec 20 20:53:46 asus kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Dec 20 20:53:46 asus pvedaemon[271008]: unable to get PID for CT 101 (not running?)
Dec 20 20:53:46 asus systemd[1]: pve-container@101.service: Succeeded.
Dec 20 20:53:46 asus systemd[1]: Started PVE LXC Container: 101.
Dec 20 20:53:47 asus kernel: loop1: detected capacity change from 0 to 629145600
Dec 20 20:53:47 asus kernel: EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Dec 20 20:53:47 asus audit[275003]: AVC apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=275003 comm="apparmor_parser"
Dec 20 20:53:47 asus kernel: audit: type=1400 audit(1640008427.480:59): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-101_</var/lib/lxc>" pid=275003 comm="apparmor_parser"
Dec 20 20:53:47 asus systemd-udevd[274950]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 20 20:53:47 asus systemd-udevd[274950]: Using default interface naming scheme 'v247'.
Dec 20 20:53:47 asus systemd-udevd[274950]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 20 20:53:47 asus systemd-udevd[274950]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 20 20:53:47 asus systemd-udevd[274949]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 20 20:53:47 asus systemd-udevd[274949]: Using default interface naming scheme 'v247'.
Dec 20 20:53:47 asus kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Dec 20 20:53:47 asus kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Dec 20 20:53:47 asus kernel: device fwln101i0 entered promiscuous mode
Dec 20 20:53:47 asus kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Dec 20 20:53:47 asus kernel: fwbr101i0: port 1(fwln101i0) entered forwarding state
Dec 20 20:53:47 asus kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Dec 20 20:53:47 asus kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Dec 20 20:53:47 asus kernel: device fwpr101p0 entered promiscuous mode
Dec 20 20:53:47 asus kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Dec 20 20:53:47 asus kernel: vmbr0: port 3(fwpr101p0) entered forwarding state
Dec 20 20:53:47 asus kernel: fwbr101i0: port 2(veth101i0) entered blocking state
Dec 20 20:53:47 asus kernel: fwbr101i0: port 2(veth101i0) entered disabled state
Dec 20 20:53:47 asus kernel: device veth101i0 entered promiscuous mode
Dec 20 20:53:47 asus kernel: eth0: renamed from vethjzPPPp
Dec 20 20:53:48 asus pvedaemon[254543]: <root@pam> end task UPID:asus:00042F8F:003554A7:61C08AAD:vzreboot:101:root@pam: OK
Dec 20 20:53:48 asus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 20 20:53:48 asus kernel: fwbr101i0: port 2(veth101i0) entered blocking state
Dec 20 20:53:48 asus kernel: fwbr101i0: port 2(veth101i0) entered forwarding state
Dec 20 20:53:50 asus pvedaemon[275702]: starting lxc termproxy UPID:asus:000434F6:00356E48:61C08AEE:vncproxy:101:root@pam:
Dec 20 20:53:50 asus pvedaemon[271008]: <root@pam> starting task UPID:asus:000434F6:00356E48:61C08AEE:vncproxy:101:root@pam:
Dec 20 20:53:50 asus pvedaemon[221593]: <root@pam> successful auth for user 'root@pam'

Kernel bug with network?

Installed Linux asus 5.13.19-2-pve #1 SMP PVE 5.13.19-4 (Mon, 29 Nov 2021 12:10:09 +0100) x86_64 GNU/Linux
 
You must log in or register to reply here.
Top Bottom