Hello
I am quite new to proxmox, and my knowledge is very limited.
I have had proxmox 5.* installed for about 6 months and everything have been working without any major problems.
This last week I am getting problems with what seems that the IP assigned to the container is not reachable from outside, and some times even from the container to outside.
IP becomes active after I have pinged from inside the container to outside any IP, then I can ping and SSH into lxc from outside, or if I wait for aprox 20 min, then the lxc respond to ping from outside.
Have a look at the video, if anyone could tell me what is going on, and how I can solve this?
Trying with another container gives the same result.
I get this in proxmox syslog:
Nov 09 17:34:12 pvedaemon[2161195]: starting CT 118: UPID:aplusvps1:0020FA2B:005EE4DC:5DC69624:vzstart:118:root@pam:
Nov 09 17:34:12 pvedaemon[2013506]: <root@pam> starting task UPID:aplusvps1:0020FA2B:005EE4DC:5DC69624:vzstart:118:root@pam:
Nov 09 17:34:12 systemd[1]: Starting PVE LXC Container: 118...
Nov 09 17:34:13 audit[2161216]: AVC apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-118_</var/lib/lxc>" pid=2161216 comm="apparmor_parser"
Nov 09 17:34:13 kernel: audit: type=1400 audit(1573295653.527:69): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-118_</var/lib/lxc>" pid=2161216 comm="apparmor_parser"
Nov 09 17:34:13 kernel: IPv6: ADDRCONF(NETDEV_UP): veth118i0: link is not ready
Nov 09 17:34:13 systemd-udevd[2161224]: Could not generate persistent MAC address for veth3VG5PN: No such file or directory
Nov 09 17:34:13 kernel: vmbr0: port 16(veth118i0) entered blocking state
Nov 09 17:34:13 kernel: vmbr0: port 16(veth118i0) entered disabled state
Nov 09 17:34:13 kernel: device veth118i0 entered promiscuous mode
Nov 09 17:34:14 kernel: eth0: renamed from veth3VG5PN
Nov 09 17:34:14 systemd[1]: Started PVE LXC Container: 118.
Nov 09 17:34:14 pvedaemon[2013506]: <root@pam> end task UPID:aplusvps1:0020FA2B:005EE4DC:5DC69624:vzstart:118:root@pam: OK
Nov 09 17:34:14 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 09 17:34:14 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 09 17:34:14 kernel: vmbr0: port 16(veth118i0) entered blocking state
Nov 09 17:34:14 kernel: vmbr0: port 16(veth118i0) entered forwarding state
pveversion if that can help:
root@:~# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-17-pve: 4.15.18-43
pve-kernel-4.15.18-16-pve: 4.15.18-41
pve-kernel-4.15.18-15-pve: 4.15.18-40
pve-kernel-4.15.18-14-pve: 4.15.18-39
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph: 12.2.12-pve1
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-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
I am quite new to proxmox, and my knowledge is very limited.
I have had proxmox 5.* installed for about 6 months and everything have been working without any major problems.
This last week I am getting problems with what seems that the IP assigned to the container is not reachable from outside, and some times even from the container to outside.
IP becomes active after I have pinged from inside the container to outside any IP, then I can ping and SSH into lxc from outside, or if I wait for aprox 20 min, then the lxc respond to ping from outside.
Have a look at the video, if anyone could tell me what is going on, and how I can solve this?
Trying with another container gives the same result.
I get this in proxmox syslog:
Nov 09 17:34:12 pvedaemon[2161195]: starting CT 118: UPID:aplusvps1:0020FA2B:005EE4DC:5DC69624:vzstart:118:root@pam:
Nov 09 17:34:12 pvedaemon[2013506]: <root@pam> starting task UPID:aplusvps1:0020FA2B:005EE4DC:5DC69624:vzstart:118:root@pam:
Nov 09 17:34:12 systemd[1]: Starting PVE LXC Container: 118...
Nov 09 17:34:13 audit[2161216]: AVC apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-118_</var/lib/lxc>" pid=2161216 comm="apparmor_parser"
Nov 09 17:34:13 kernel: audit: type=1400 audit(1573295653.527:69): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-118_</var/lib/lxc>" pid=2161216 comm="apparmor_parser"
Nov 09 17:34:13 kernel: IPv6: ADDRCONF(NETDEV_UP): veth118i0: link is not ready
Nov 09 17:34:13 systemd-udevd[2161224]: Could not generate persistent MAC address for veth3VG5PN: No such file or directory
Nov 09 17:34:13 kernel: vmbr0: port 16(veth118i0) entered blocking state
Nov 09 17:34:13 kernel: vmbr0: port 16(veth118i0) entered disabled state
Nov 09 17:34:13 kernel: device veth118i0 entered promiscuous mode
Nov 09 17:34:14 kernel: eth0: renamed from veth3VG5PN
Nov 09 17:34:14 systemd[1]: Started PVE LXC Container: 118.
Nov 09 17:34:14 pvedaemon[2013506]: <root@pam> end task UPID:aplusvps1:0020FA2B:005EE4DC:5DC69624:vzstart:118:root@pam: OK
Nov 09 17:34:14 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 09 17:34:14 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 09 17:34:14 kernel: vmbr0: port 16(veth118i0) entered blocking state
Nov 09 17:34:14 kernel: vmbr0: port 16(veth118i0) entered forwarding state
pveversion if that can help:
root@:~# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-17-pve: 4.15.18-43
pve-kernel-4.15.18-16-pve: 4.15.18-41
pve-kernel-4.15.18-15-pve: 4.15.18-40
pve-kernel-4.15.18-14-pve: 4.15.18-39
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph: 12.2.12-pve1
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-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
Last edited: