Martian source

clearwater

Member
Nov 15, 2019
9
0
6
Hi,

I'm getting tens of thousands of 'martian source' entries in my syslog daily!

This is an example output from just some messages that appear in ONE SECOND - is this normal??
Code:
Feb 27 18:50:56 pve kernel: ll header: 00000000: ff ff ff ff ff ff f2 fe ea 6e bd 47 08 00
Feb 27 18:50:56 pve kernel: ll header: 00000000: ff ff ff ff ff ff f2 fe ea 6e bd 47 08 00
Feb 27 18:50:56 pve kernel: IPv4: martian source 192.168.0.255 from 192.168.0.151, on dev eth1
Feb 27 18:50:56 pve kernel: ll header: 00000000: ff ff ff ff ff ff f2 fe ea 6e bd 47 08 00
Feb 27 18:50:56 pve kernel: ll header: 00000000: ff ff ff ff ff ff f2 fe ea 6e bd 47 08 00
Feb 27 18:50:56 pve kernel: ll header: 00000000: ff ff ff ff ff ff f2 fe ea 6e bd 47 08 00
Feb 27 18:50:56 pve kernel: IPv4: martian source 192.168.0.255 from 192.168.0.151, on dev eth1
Feb 27 18:50:56 pve kernel: ll header: 00000000: ff ff ff ff ff ff f2 fe ea 6e bd 47 08 00
Feb 27 18:50:56 pve kernel: IPv4: martian source 192.168.0.43 from 192.168.0.201, on dev eth1
Feb 27 18:50:56 pve kernel: IPv4: martian source 192.168.0.43 from 192.168.0.201, on dev eth1
Feb 27 18:50:56 pve kernel: IPv4: martian source 192.168.0.43 from 192.168.0.201, on dev eth1
Feb 27 18:50:56 pve kernel: ll header: 00000000: ff ff ff ff ff ff 4a 3f 7e 64 64 1

Sometimes my entire home internet will be brought down, and I wonder if this has something to do with it (my router loses connection with my modem, even though my modem still has a valid internet connection. I am running TP-Link Omada hardware for my network (router, switches, etc) although I'm pretty sure this has been happening before I installed these on my network.

System specs: Dell r710, 24 x Intel(R) Xeon(R) CPU X5675 @ 3.07GHz (2 Sockets)
PVE version: pve-manager/7.1-10/6ddebafe (running kernel: 5.13.19-4-pve)

cat etc/network/interfaces:
Code:
auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto bond0
iface bond0 inet manual
        bond-slaves eno1 eno2 eno3 eno4
        bond-miimon 100
        bond-mode balance-rr

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.150/24
        gateway 192.168.0.1
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

Any suggestions or help is welcome, no matter how small. I am pulling my hair out trying to solve this!

Thank you
 
Last edited:

fiona

Proxmox Staff Member
Staff member
Aug 1, 2019
1,999
356
88
Hi,
there is no mention of eth1 in your network configuration. What does ip a show? This gives a quick run-down of some cases that can lead to the martian source message. It's likely a misbehaving/misconfigured device in your network.
 

clearwater

Member
Nov 15, 2019
9
0
6
Hi,

Thanks for your response. Yes, good point regarding no eth1. Could this be a holdout from a previous configuration? Or perhaps should I isolate one network port and label it eth1 to troubleshoot further? Not sure if this would make sense to do.

Here is the output of ip a:

Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether a4:ba:db:28:4c:4a brd ff:ff:ff:ff:ff:ff
    altname enp1s0f0
3: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether a4:ba:db:28:4c:4a brd ff:ff:ff:ff:ff:ff permaddr a4:ba:db:28:4c:4c
    altname enp1s0f1
4: eno3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether a4:ba:db:28:4c:4a brd ff:ff:ff:ff:ff:ff permaddr a4:ba:db:28:4c:4e
    altname enp2s0f0
5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc mq master bond0 state DOWN group default qlen 1000
    link/ether a4:ba:db:28:4c:4a brd ff:ff:ff:ff:ff:ff permaddr a4:ba:db:28:4c:50
    altname enp2s0f1
6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether a4:ba:db:28:4c:4a brd ff:ff:ff:ff:ff:ff
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a4:ba:db:28:4c:4a brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.150/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::a6ba:dbff:fe28:4c4a/64 scope link
       valid_lft forever preferred_lft forever
12: tap105i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr105i0 state UNKNOWN group default qlen 1000
    link/ether 7a:7e:11:25:15:23 brd ff:ff:ff:ff:ff:ff
13: fwbr105i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether aa:08:31:7b:fc:e9 brd ff:ff:ff:ff:ff:ff
14: fwpr105p0@fwln105i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether e6:d0:0f:cc:93:c9 brd ff:ff:ff:ff:ff:ff
15: fwln105i0@fwpr105p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr105i0 state UP group default qlen 1000
    link/ether 2e:e1:13:ae:a8:16 brd ff:ff:ff:ff:ff:ff
16: veth202i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr202i0 state UP group default qlen 1000
    link/ether fe:3b:1d:8e:a6:c2 brd ff:ff:ff:ff:ff:ff link-netnsid 0
17: fwbr202i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 8a:ac:86:80:8a:64 brd ff:ff:ff:ff:ff:ff
18: fwpr202p0@fwln202i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fa:90:da:d4:46:d8 brd ff:ff:ff:ff:ff:ff
19: fwln202i0@fwpr202p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr202i0 state UP group default qlen 1000
    link/ether 8a:fd:0c:c9:90:28 brd ff:ff:ff:ff:ff:ff
20: veth201i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr201i0 state UP group default qlen 1000
    link/ether fe:f9:fc:01:0f:3c brd ff:ff:ff:ff:ff:ff link-netnsid 1
21: fwbr201i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9e:72:5b:67:d0:8b brd ff:ff:ff:ff:ff:ff
22: fwpr201p0@fwln201i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 82:05:68:49:97:f3 brd ff:ff:ff:ff:ff:ff
23: fwln201i0@fwpr201p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr201i0 state UP group default qlen 1000
    link/ether 9a:59:2a:d4:2f:4e brd ff:ff:ff:ff:ff:ff
24: tap106i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether d2:b1:e6:e5:81:c8 brd ff:ff:ff:ff:ff:ff
25: veth206i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr206i0 state UP group default qlen 1000
    link/ether fe:ff:e3:f5:34:48 brd ff:ff:ff:ff:ff:ff link-netnsid 2
26: fwbr206i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e2:23:70:bb:2f:11 brd ff:ff:ff:ff:ff:ff
27: fwpr206p0@fwln206i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fa:b7:b3:f3:2c:3f brd ff:ff:ff:ff:ff:ff
28: fwln206i0@fwpr206p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr206i0 state UP group default qlen 1000
    link/ether 26:0f:bc:b7:9b:52 brd ff:ff:ff:ff:ff:ff
29: veth206i1@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr206i1 state UP group default qlen 1000
    link/ether fe:b5:67:52:4d:07 brd ff:ff:ff:ff:ff:ff link-netnsid 2
30: fwbr206i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 92:a7:b4:c1:a4:96 brd ff:ff:ff:ff:ff:ff
31: fwpr206p1@fwln206i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 6e:05:0f:5e:65:5f brd ff:ff:ff:ff:ff:ff
32: fwln206i1@fwpr206p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr206i1 state UP group default qlen 1000
    link/ether 12:da:f8:98:13:29 brd ff:ff:ff:ff:ff:ff
37: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
    link/ether a6:3d:bc:19:f7:dc brd ff:ff:ff:ff:ff:ff
38: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 36:31:3a:0b:24:e3 brd ff:ff:ff:ff:ff:ff
39: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 02:1c:c5:35:0b:11 brd ff:ff:ff:ff:ff:ff
40: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether 52:ad:12:09:5a:cb brd ff:ff:ff:ff:ff:ff
 

spirit

Famous Member
Apr 2, 2010
5,685
626
133
www.odiso.com
Hi,
I am having the same issue. How did you sort it out?
I'm not sure, but on original post
"IPv4: martian source 192.168.0.255"

Sound like the broadcast address was configured somewhere on the network as an interface ip.
(in ipv4, you can't use the first (network address) and last ip (brodcast address) of a subnet. They are martians ^_^).

for example in 192.168.0.0/24 , you can't use 192.168.0.0 && 192.168.0.255.
 

giuppy

New Member
Dec 10, 2020
28
0
1
45
In my case I have tons of entries like
Code:
Jun 24 08:04:25 pve2 kernel: IPv4: martian source 185.XXX.XX.255 from 185.22.XX.XX3, on dev lan
Jun 24 08:04:25 pve2 kernel: ll header: 00000000: ff ff ff ff ff ff 1e ea 3a 3e 0c f8 08 00
Jun 24 08:09:26 pve2 kernel: IPv4: martian source 255.255.255.255 from 185.22.XX.XX3, on dev lan
Jun 24 08:09:26 pve2 kernel: ll header: 00000000: ff ff ff ff ff ff 1e ea 3a 3e 0c f8 08 00
I clecked the guest and network config seems to be fine.
I really Have no idea where else to look
 
Last edited:

giuppy

New Member
Dec 10, 2020
28
0
1
45
The most strange thing is that any of the guest on that node is using the mentioned IPs. All ips are allocated on other nodes
 

tlex

Member
Mar 9, 2021
79
6
8
41
Same issue for me since this morning, logs gets flooded with such messages for ip client being vms and non-vms..
and more specifically I get those messages for an interface that doesn't exist on my system (eth0) :

no eth0 interface :

ip a |grep eth0 root@pve:~#


syslogs:

Jul 26 14:54:03 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.3, on dev eth0 Jul 26 14:54:03 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a c0 d0 08 00 Jul 26 14:54:03 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.2, on dev eth0 Jul 26 14:54:03 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a eb a0 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.3, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a c0 d0 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.2, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a eb a0 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:15 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.34, on dev eth0 Jul 26 14:54:15 pve kernel: ll header: 00000000: ff ff ff ff ff ff 92 df 18 27 d4 89 08 00 Jul 26 14:54:31 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:31 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:31 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:31 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:31 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.19, on dev eth0 Jul 26 14:54:31 pve kernel: ll header: 00000000: ff ff ff ff ff ff 00 0c 15 01 46 c6 08 00 Jul 26 14:54:57 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:57 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:57 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:57 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:55:01 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.19, on dev eth0 Jul 26 14:55:01 pve kernel: ll header: 00000000: ff ff ff ff ff ff 00 0c 15 01 46 c6 08 00 Jul 26 14:55:15 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.196, on dev eth0 Jul 26 14:55:15 pve kernel: ll header: 00000000: ff ff ff ff ff ff 72 cb a2 b3 5a 2e 08 00 Jul 26 14:55:23 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:55:23 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:55:23 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:55:23 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00


sudo ifdown eth0 error: main exception: cannot find interfaces: eth0 (interface was probably never up ?) root@pve:~# sudo ifup eth0 error: main exception: cannot find interfaces: eth0

what can it be ?
 
Last edited:

tlex

Member
Mar 9, 2021
79
6
8
41
Same issue for me since this morning, logs gets flooded with such messages for ip client being vms and non-vms..
and more specifically I get those messages for an interface that doesn't exist on my system (eth0) :

no eth0 interface :

ip a |grep eth0 root@pve:~#


syslogs:

Jul 26 14:54:03 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.3, on dev eth0 Jul 26 14:54:03 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a c0 d0 08 00 Jul 26 14:54:03 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.2, on dev eth0 Jul 26 14:54:03 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a eb a0 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.3, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a c0 d0 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.2, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff d4 5d 64 8a eb a0 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:05 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:05 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:15 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.34, on dev eth0 Jul 26 14:54:15 pve kernel: ll header: 00000000: ff ff ff ff ff ff 92 df 18 27 d4 89 08 00 Jul 26 14:54:31 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:31 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:31 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:31 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:31 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.19, on dev eth0 Jul 26 14:54:31 pve kernel: ll header: 00000000: ff ff ff ff ff ff 00 0c 15 01 46 c6 08 00 Jul 26 14:54:57 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:57 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:54:57 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:54:57 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:55:01 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.19, on dev eth0 Jul 26 14:55:01 pve kernel: ll header: 00000000: ff ff ff ff ff ff 00 0c 15 01 46 c6 08 00 Jul 26 14:55:15 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.196, on dev eth0 Jul 26 14:55:15 pve kernel: ll header: 00000000: ff ff ff ff ff ff 72 cb a2 b3 5a 2e 08 00 Jul 26 14:55:23 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:55:23 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00 Jul 26 14:55:23 pve kernel: IPv4: martian source 255.255.255.255 from 10.32.50.194, on dev eth0 Jul 26 14:55:23 pve kernel: ll header: 00000000: ff ff ff ff ff ff 28 16 a8 72 ac ca 08 00


sudo ifdown eth0 error: main exception: cannot find interfaces: eth0 (interface was probably never up ?) root@pve:~# sudo ifup eth0 error: main exception: cannot find interfaces: eth0

what can it be ?
as soon as I shutdown 1 lxc container the martian messages disapeared :

Jul 26 15:09:13 pve pvedaemon[2669140]: <root@pam> starting task UPID:pve:00343094:052074BF:62E03BD9:vzshutdown:105:root@pam: Jul 26 15:09:13 pve pvedaemon[3420308]: shutdown CT 105: UPID:pve:00343094:052074BF:62E03BD9:vzshutdown:105:root@pam: Jul 26 15:09:13 pve kernel: fwbr105i0: port 2(veth105i0) entered disabled state Jul 26 15:09:13 pve kernel: device veth105i0 left promiscuous mode Jul 26 15:09:13 pve kernel: fwbr105i0: port 2(veth105i0) entered disabled state Jul 26 15:09:14 pve audit[3420376]: AVC apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-105_</var/lib/lxc>" pid=3420376 comm="apparmor_parser" Jul 26 15:09:14 pve kernel: audit: type=1400 audit(1658862554.113:22): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-105_</var/lib/lxc>" pid=3420376 comm="apparmor_parser" Jul 26 15:09:14 pve pvedaemon[2669140]: unable to get PID for CT 105 (not running?) Jul 26 15:09:15 pve kernel: fwbr105i0: port 1(fwln105i0) entered disabled state Jul 26 15:09:15 pve kernel: vmbr0: port 3(fwpr105p0) entered disabled state Jul 26 15:09:15 pve kernel: device fwln105i0 left promiscuous mode Jul 26 15:09:15 pve kernel: fwbr105i0: port 1(fwln105i0) entered disabled state Jul 26 15:09:15 pve kernel: device fwpr105p0 left promiscuous mode Jul 26 15:09:15 pve kernel: vmbr0: port 3(fwpr105p0) entered disabled state Jul 26 15:09:15 pve pvedaemon[2669140]: <root@pam> end task UPID:pve:00343094:052074BF:62E03BD9:vzshutdown:105:root@pam: OK Jul 26 15:09:15 pve systemd[1]: pve-container@105.service: Succeeded.
 

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!

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 your own in 60 seconds.

Buy now!