search

SensorsIot / IOTstack

Docker stack for getting started on IOT on the Raspberry PI
GNU General Public License v3.0
1.44k stars 307 forks source link

Grafana updated and now broken #546

Closed confuserated closed 2 years ago

confuserated commented 2 years ago

Hi, Not super-techie here but I just updated all of the containers I was using on my Home Assistant Server (the usual suspects) and Grafana has now stopped working, it endlessly crashes and restarts the docker container, no configs have changed at all since last update and everything else is working fine.

Fairly sure I can't be the only one experiencing this problem on latest version of Grafana, all other systems are latest version and RPi OS is Bullseye latest.

Logs as follows:

pi@RPi4:~/IOTstack $ sudo journalctl --since 01:20 --until "now" -- Journal begins at Fri 2022-01-28 01:30:20 GMT, ends at Sat 2022-04-16 01:20:49 BST. -- Apr 16 01:20:04 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-e5740e62c66def928f7e1b9cf2a76bf7d5d4c38742c781124ec60c960e561e19-runc.YZFTNu.mount: Succeeded. Apr 16 01:20:04 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-e5740e62c66def928f7e1b9cf2a76bf7d5d4c38742c781124ec60c960e561e19-runc.YZFTNu.mount: Succeeded. Apr 16 01:20:04 RPi4 systemd[1]: run-docker-runtime\x2drunc-moby-e5740e62c66def928f7e1b9cf2a76bf7d5d4c38742c781124ec60c960e561e19-runc.YZFTNu.mount: Succeeded. Apr 16 01:20:07 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-9c67352dd77c503907dedd2c06299fa5e7c6a4b8fe3de6e2529db4af7bb3a7df-runc.ArH9rf.mount: Succeeded. Apr 16 01:20:07 RPi4 systemd[1]: run-docker-runtime\x2drunc-moby-9c67352dd77c503907dedd2c06299fa5e7c6a4b8fe3de6e2529db4af7bb3a7df-runc.ArH9rf.mount: Succeeded. Apr 16 01:20:07 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-9c67352dd77c503907dedd2c06299fa5e7c6a4b8fe3de6e2529db4af7bb3a7df-runc.ArH9rf.mount: Succeeded. Apr 16 01:20:08 RPi4 systemd[1]: docker-fa1f59e7c9f0316b08683ee45259ea61f52f66348176c639f0f5a65826c89554.scope: Succeeded. Apr 16 01:20:08 RPi4 systemd[1]: docker-fa1f59e7c9f0316b08683ee45259ea61f52f66348176c639f0f5a65826c89554.scope: Consumed 4.200s CPU time. Apr 16 01:20:08 RPi4 systemd[1]: docker-9c67352dd77c503907dedd2c06299fa5e7c6a4b8fe3de6e2529db4af7bb3a7df.scope: Succeeded. Apr 16 01:20:08 RPi4 systemd[1]: docker-9c67352dd77c503907dedd2c06299fa5e7c6a4b8fe3de6e2529db4af7bb3a7df.scope: Consumed 3.844s CPU time. Apr 16 01:20:08 RPi4 dockerd[621]: time="2022-04-16T01:20:08.751651920+01:00" level=info msg="ignoring event" container=fa1f59e7c9f0316b08683ee45259ea61f52f66348176c639f0f5a65826> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.752055214+01:00" level=info msg="shim disconnected" id=fa1f59e7c9f0316b08683ee45259ea61f52f66348176c639f0f5a65826c> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.752245305+01:00" level=warning msg="cleaning up after shim disconnected" id=fa1f59e7c9f0316b08683ee45259ea61f52f66> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.752371045+01:00" level=info msg="cleaning up dead shim" Apr 16 01:20:08 RPi4 systemd[1]: docker-bb0b8fe6e56513849212c327ad2dc98bcc963728102ba981a2f8c5e00bec8afa.scope: Succeeded. Apr 16 01:20:08 RPi4 systemd[1]: docker-bb0b8fe6e56513849212c327ad2dc98bcc963728102ba981a2f8c5e00bec8afa.scope: Consumed 19.583s CPU time. Apr 16 01:20:08 RPi4 dockerd[621]: time="2022-04-16T01:20:08.811927378+01:00" level=info msg="ignoring event" container=9c67352dd77c503907dedd2c06299fa5e7c6a4b8fe3de6e2529db4af7b> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.813286573+01:00" level=info msg="shim disconnected" id=9c67352dd77c503907dedd2c06299fa5e7c6a4b8fe3de6e2529db4af7bb> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.814065901+01:00" level=warning msg="cleaning up after shim disconnected" id=9c67352dd77c503907dedd2c06299fa5e7c6a4> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.814666564+01:00" level=info msg="cleaning up dead shim" Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.844432295+01:00" level=warning msg="cleanup warnings time=\"2022-04-16T01:20:08+01:00\" level=info msg=\"starting > Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.869854185+01:00" level=warning msg="cleanup warnings time=\"2022-04-16T01:20:08+01:00\" level=info msg=\"starting > Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.871071195+01:00" level=info msg="shim disconnected" id=bb0b8fe6e56513849212c327ad2dc98bcc963728102ba981a2f8c5e00be> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.871656839+01:00" level=warning msg="cleaning up after shim disconnected" id=bb0b8fe6e56513849212c327ad2dc98bcc9637> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.872084225+01:00" level=info msg="cleaning up dead shim" Apr 16 01:20:08 RPi4 dockerd[621]: time="2022-04-16T01:20:08.874088805+01:00" level=info msg="ignoring event" container=bb0b8fe6e56513849212c327ad2dc98bcc963728102ba981a2f8c5e00b> Apr 16 01:20:08 RPi4 containerd[523]: time="2022-04-16T01:20:08.921875252+01:00" level=warning msg="cleanup warnings time=\"2022-04-16T01:20:08+01:00\" level=info msg=\"starting > Apr 16 01:20:08 RPi4 dhcpcd[444]: veth42a41f5: carrier lost Apr 16 01:20:08 RPi4 kernel: br-1f4b14d68fa1: port 3(veth42a41f5) entered disabled state Apr 16 01:20:08 RPi4 kernel: vethbd295d2: renamed from eth0 Apr 16 01:20:09 RPi4 avahi-daemon[395]: Withdrawing address record for 169.254.92.209 on veth42a41f5. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth42a41f5.IPv4 with address 169.254.92.209. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Interface veth42a41f5.IPv4 no longer relevant for mDNS. Apr 16 01:20:09 RPi4 dhcpcd[444]: veth42a41f5: deleting route to 169.254.0.0/16 Apr 16 01:20:09 RPi4 avahi-daemon[395]: Interface veth42a41f5.IPv6 no longer relevant for mDNS. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth42a41f5.IPv6 with address fe80::940f:16ff:fe03:55f. Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 3(veth42a41f5) entered disabled state Apr 16 01:20:09 RPi4 kernel: device veth42a41f5 left promiscuous mode Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 3(veth42a41f5) entered disabled state Apr 16 01:20:09 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::940f:16ff:fe03:55f on veth42a41f5. Apr 16 01:20:09 RPi4 dhcpcd[444]: veth42a41f5: removing interface Apr 16 01:20:09 RPi4 systemd-udevd[2490]: vethbd295d2: Failed to query device driver: No such device Apr 16 01:20:09 RPi4 systemd-udevd[2490]: vethbd295d2: Failed to get link config: No such device Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 4(veth51dcc11) entered disabled state Apr 16 01:20:09 RPi4 kernel: veth54daba9: renamed from eth0 Apr 16 01:20:09 RPi4 systemd[713]: run-docker-netns-5d96685fdf78.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[31201]: run-docker-netns-5d96685fdf78.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[1]: run-docker-netns-5d96685fdf78.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[713]: var-lib-docker-overlay2-bda6ed5a1648374781c9fcf78511603faa23c8459f15cb7475363791c1ddafac-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[31201]: var-lib-docker-overlay2-bda6ed5a1648374781c9fcf78511603faa23c8459f15cb7475363791c1ddafac-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[1]: var-lib-docker-overlay2-bda6ed5a1648374781c9fcf78511603faa23c8459f15cb7475363791c1ddafac-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 dhcpcd[444]: veth51dcc11: carrier lost Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 6(veth8e39384) entered disabled state Apr 16 01:20:09 RPi4 kernel: veth8279769: renamed from eth0 Apr 16 01:20:09 RPi4 dhcpcd[444]: veth51dcc11: deleting address fe80::ee3e:2071:5b5c:e03b Apr 16 01:20:09 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::ee3e:2071:5b5c:e03b on veth51dcc11. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth51dcc11.IPv6 with address fe80::ee3e:2071:5b5c:e03b. Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 4(veth51dcc11) entered disabled state Apr 16 01:20:09 RPi4 kernel: device veth51dcc11 left promiscuous mode Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 4(veth51dcc11) entered disabled state Apr 16 01:20:09 RPi4 avahi-daemon[395]: Interface veth51dcc11.IPv6 no longer relevant for mDNS. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Interface veth51dcc11.IPv4 no longer relevant for mDNS. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth51dcc11.IPv4 with address 169.254.215.160. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Withdrawing address record for 169.254.215.160 on veth51dcc11. Apr 16 01:20:09 RPi4 systemd-udevd[2526]: veth54daba9: Failed to query device driver: No such device Apr 16 01:20:09 RPi4 systemd-udevd[2526]: veth54daba9: Failed to get link config: No such device Apr 16 01:20:09 RPi4 dhcpcd[444]: veth51dcc11: deleting route to 169.254.0.0/16 Apr 16 01:20:09 RPi4 dhcpcd[444]: veth51dcc11: removing interface Apr 16 01:20:09 RPi4 avahi-daemon[395]: Interface veth8e39384.IPv6 no longer relevant for mDNS. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth8e39384.IPv6 with address fe80::8013:cbff:fe92:674f. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Interface veth8e39384.IPv4 no longer relevant for mDNS. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth8e39384.IPv4 with address 169.254.205.171. Apr 16 01:20:09 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::8013:cbff:fe92:674f on veth8e39384. Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 6(veth8e39384) entered disabled state Apr 16 01:20:09 RPi4 kernel: device veth8e39384 left promiscuous mode Apr 16 01:20:09 RPi4 kernel: br-1f4b14d68fa1: port 6(veth8e39384) entered disabled state Apr 16 01:20:09 RPi4 avahi-daemon[395]: Withdrawing address record for 169.254.205.171 on veth8e39384. Apr 16 01:20:09 RPi4 dhcpcd[444]: dhcp_readbpf: veth8e39384: Network is down Apr 16 01:20:09 RPi4 systemd[31201]: run-docker-netns-7e86df2622b1.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[1]: run-docker-netns-7e86df2622b1.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[713]: run-docker-netns-7e86df2622b1.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[713]: var-lib-docker-overlay2-86522ae129450cc53c705086202ed4cbfe5d062b30deba2d2902857ab02eed20-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[1]: var-lib-docker-overlay2-86522ae129450cc53c705086202ed4cbfe5d062b30deba2d2902857ab02eed20-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[31201]: var-lib-docker-overlay2-86522ae129450cc53c705086202ed4cbfe5d062b30deba2d2902857ab02eed20-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 dhcpcd[444]: arp_read: veth8e39384: Network is down Apr 16 01:20:09 RPi4 systemd[31201]: run-docker-netns-9f6c4b2d3c45.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[1]: run-docker-netns-9f6c4b2d3c45.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[713]: run-docker-netns-9f6c4b2d3c45.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[31201]: var-lib-docker-overlay2-e168341b1554516a2ab773a54ae0cf7896b3443182a595df87a40cda038430ee-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[713]: var-lib-docker-overlay2-e168341b1554516a2ab773a54ae0cf7896b3443182a595df87a40cda038430ee-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 systemd[1]: var-lib-docker-overlay2-e168341b1554516a2ab773a54ae0cf7896b3443182a595df87a40cda038430ee-merged.mount: Succeeded. Apr 16 01:20:09 RPi4 dhcpcd[444]: veth8e39384: removing interface Apr 16 01:20:09 RPi4 dhcpcd[444]: veth8e39384: deleting route to 169.254.0.0/16 Apr 16 01:20:12 RPi4 systemd[1]: docker-efab84bacf6a37328e67be5fec6b694cc1c2163d032106f65f5c8196e676389a.scope: Succeeded. Apr 16 01:20:12 RPi4 systemd[1]: docker-efab84bacf6a37328e67be5fec6b694cc1c2163d032106f65f5c8196e676389a.scope: Consumed 4.165s CPU time. Apr 16 01:20:12 RPi4 containerd[523]: time="2022-04-16T01:20:12.216200902+01:00" level=info msg="shim disconnected" id=efab84bacf6a37328e67be5fec6b694cc1c2163d032106f65f5c8196e67> Apr 16 01:20:12 RPi4 containerd[523]: time="2022-04-16T01:20:12.216333587+01:00" level=warning msg="cleaning up after shim disconnected" id=efab84bacf6a37328e67be5fec6b694cc1c216> Apr 16 01:20:12 RPi4 containerd[523]: time="2022-04-16T01:20:12.216373698+01:00" level=info msg="cleaning up dead shim" Apr 16 01:20:12 RPi4 dockerd[621]: time="2022-04-16T01:20:12.216204884+01:00" level=info msg="ignoring event" container=efab84bacf6a37328e67be5fec6b694cc1c2163d032106f65f5c8196e6> Apr 16 01:20:12 RPi4 containerd[523]: time="2022-04-16T01:20:12.251575838+01:00" level=warning msg="cleanup warnings time=\"2022-04-16T01:20:12+01:00\" level=info msg=\"starting > Apr 16 01:20:12 RPi4 dhcpcd[444]: veth2310277: carrier lost Apr 16 01:20:12 RPi4 kernel: br-1f4b14d68fa1: port 1(veth2310277) entered disabled state Apr 16 01:20:12 RPi4 kernel: veth9ecf8d1: renamed from eth0 Apr 16 01:20:12 RPi4 dhcpcd[444]: veth2310277: deleting address fe80::76aa:3ef5:ae2c:536b Apr 16 01:20:12 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::76aa:3ef5:ae2c:536b on veth2310277. Apr 16 01:20:12 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth2310277.IPv6 with address fe80::76aa:3ef5:ae2c:536b. Apr 16 01:20:12 RPi4 avahi-daemon[395]: Interface veth2310277.IPv6 no longer relevant for mDNS. Apr 16 01:20:12 RPi4 avahi-daemon[395]: Interface veth2310277.IPv4 no longer relevant for mDNS. Apr 16 01:20:12 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth2310277.IPv4 with address 169.254.147.209. Apr 16 01:20:12 RPi4 avahi-daemon[395]: Withdrawing address record for 169.254.147.209 on veth2310277. Apr 16 01:20:12 RPi4 kernel: br-1f4b14d68fa1: port 1(veth2310277) entered disabled state Apr 16 01:20:12 RPi4 kernel: device veth2310277 left promiscuous mode Apr 16 01:20:12 RPi4 kernel: br-1f4b14d68fa1: port 1(veth2310277) entered disabled state Apr 16 01:20:12 RPi4 dhcpcd[444]: veth2310277: deleting route to 169.254.0.0/16 Apr 16 01:20:12 RPi4 systemd[1]: run-docker-netns-66f46c1d43a9.mount: Succeeded. Apr 16 01:20:12 RPi4 systemd[31201]: run-docker-netns-66f46c1d43a9.mount: Succeeded. Apr 16 01:20:12 RPi4 systemd[713]: run-docker-netns-66f46c1d43a9.mount: Succeeded. Apr 16 01:20:12 RPi4 systemd[713]: var-lib-docker-overlay2-188191cfd953d5e168b695f1e15c1ff12090d8cfbd18607d2b2bcf8d0f5baf72-merged.mount: Succeeded. Apr 16 01:20:12 RPi4 systemd[1]: var-lib-docker-overlay2-188191cfd953d5e168b695f1e15c1ff12090d8cfbd18607d2b2bcf8d0f5baf72-merged.mount: Succeeded. Apr 16 01:20:12 RPi4 systemd[31201]: var-lib-docker-overlay2-188191cfd953d5e168b695f1e15c1ff12090d8cfbd18607d2b2bcf8d0f5baf72-merged.mount: Succeeded. Apr 16 01:20:12 RPi4 systemd-udevd[2526]: veth9ecf8d1: Failed to query device driver: No such device Apr 16 01:20:12 RPi4 systemd-udevd[2526]: veth9ecf8d1: Failed to get link config: No such device Apr 16 01:20:12 RPi4 dhcpcd[444]: veth2310277: removing interface Apr 16 01:20:18 RPi4 dockerd[621]: time="2022-04-16T01:20:18.676612924+01:00" level=info msg="Container failed to exit within 10s of signal 15 - using the force" container=11fab2> Apr 16 01:20:18 RPi4 systemd[1]: docker-11fab24e7af1ae7e27b57e586f12c0625f33d3fc30692a79dc16d6c5a7643755.scope: Succeeded. Apr 16 01:20:18 RPi4 systemd[1]: docker-11fab24e7af1ae7e27b57e586f12c0625f33d3fc30692a79dc16d6c5a7643755.scope: Consumed 7min 13.236s CPU time. Apr 16 01:20:18 RPi4 containerd[523]: time="2022-04-16T01:20:18.792008259+01:00" level=info msg="shim disconnected" id=11fab24e7af1ae7e27b57e586f12c0625f33d3fc30692a79dc16d6c5a76> Apr 16 01:20:18 RPi4 containerd[523]: time="2022-04-16T01:20:18.792949383+01:00" level=warning msg="cleaning up after shim disconnected" id=11fab24e7af1ae7e27b57e586f12c0625f33d3> Apr 16 01:20:18 RPi4 containerd[523]: time="2022-04-16T01:20:18.793017827+01:00" level=info msg="cleaning up dead shim" Apr 16 01:20:18 RPi4 containerd[523]: time="2022-04-16T01:20:18.826566088+01:00" level=warning msg="cleanup warnings time=\"2022-04-16T01:20:18+01:00\" level=info msg=\"starting > Apr 16 01:20:18 RPi4 dockerd[621]: time="2022-04-16T01:20:18.792488830+01:00" level=info msg="ignoring event" container=11fab24e7af1ae7e27b57e586f12c0625f33d3fc30692a79dc16d6c5a7> Apr 16 01:20:19 RPi4 dhcpcd[444]: vethdddca33: carrier lost Apr 16 01:20:19 RPi4 kernel: br-1f4b14d68fa1: port 2(vethdddca33) entered disabled state Apr 16 01:20:19 RPi4 kernel: veth978af59: renamed from eth0 Apr 16 01:20:19 RPi4 dhcpcd[444]: vethdddca33: deleting address fe80::d26b:f86:8966:2e31 Apr 16 01:20:19 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::d26b:f86:8966:2e31 on vethdddca33. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface vethdddca33.IPv6 with address fe80::d26b:f86:8966:2e31. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Interface vethdddca33.IPv6 no longer relevant for mDNS. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Interface vethdddca33.IPv4 no longer relevant for mDNS. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface vethdddca33.IPv4 with address 169.254.204.2. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Withdrawing address record for 169.254.204.2 on vethdddca33. Apr 16 01:20:19 RPi4 kernel: br-1f4b14d68fa1: port 2(vethdddca33) entered disabled state Apr 16 01:20:19 RPi4 kernel: device vethdddca33 left promiscuous mode Apr 16 01:20:19 RPi4 kernel: br-1f4b14d68fa1: port 2(vethdddca33) entered disabled state Apr 16 01:20:19 RPi4 dhcpcd[444]: vethdddca33: deleting route to 169.254.0.0/16 Apr 16 01:20:19 RPi4 systemd[31201]: run-docker-netns-f8c825b4869b.mount: Succeeded. Apr 16 01:20:19 RPi4 systemd[1]: run-docker-netns-f8c825b4869b.mount: Succeeded. Apr 16 01:20:19 RPi4 systemd[713]: run-docker-netns-f8c825b4869b.mount: Succeeded. Apr 16 01:20:19 RPi4 systemd[31201]: var-lib-docker-overlay2-35c1ed4911e955d9f53684dc36d04d4f4f513e13587dc96eb8bb380222803f7d-merged.mount: Succeeded. Apr 16 01:20:19 RPi4 systemd[1]: var-lib-docker-overlay2-35c1ed4911e955d9f53684dc36d04d4f4f513e13587dc96eb8bb380222803f7d-merged.mount: Succeeded. Apr 16 01:20:19 RPi4 systemd[713]: var-lib-docker-overlay2-35c1ed4911e955d9f53684dc36d04d4f4f513e13587dc96eb8bb380222803f7d-merged.mount: Succeeded. Apr 16 01:20:19 RPi4 systemd-udevd[2719]: veth978af59: Failed to query device driver: No such device Apr 16 01:20:19 RPi4 systemd-udevd[2719]: veth978af59: Failed to get link config: No such device Apr 16 01:20:19 RPi4 dhcpcd[444]: vethdddca33: removing interface Apr 16 01:20:19 RPi4 avahi-daemon[395]: Interface br-1f4b14d68fa1.IPv6 no longer relevant for mDNS. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface br-1f4b14d68fa1.IPv6 with address fe80::42:7aff:fefa:f46. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Interface br-1f4b14d68fa1.IPv4 no longer relevant for mDNS. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface br-1f4b14d68fa1.IPv4 with address 172.20.0.1. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::42:7aff:fefa:f46 on br-1f4b14d68fa1. Apr 16 01:20:19 RPi4 avahi-daemon[395]: Withdrawing address record for 172.20.0.1 on br-1f4b14d68fa1. Apr 16 01:20:26 RPi4 systemd-udevd[2845]: Using default interface naming scheme 'v247'. Apr 16 01:20:26 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface br-9b221860107e.IPv4 with address 172.21.0.1. Apr 16 01:20:26 RPi4 avahi-daemon[395]: New relevant interface br-9b221860107e.IPv4 for mDNS. Apr 16 01:20:26 RPi4 avahi-daemon[395]: Registering new address record for 172.21.0.1 on br-9b221860107e.IPv4. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-dcf77ff207ffa944f1182a1fbcbe3f3a257586adabc22bd05ad995433ee07ad5\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-9b490b642429b5c28e8d44b35faf6e307aae46a15b1e3f9b1831fa5f388c73bb\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-dcf77ff207ffa944f1182a1fbcbe3f3a257586adabc22bd05ad995433ee07ad5\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-9b490b642429b5c28e8d44b35faf6e307aae46a15b1e3f9b1831fa5f388c73bb\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[31201]: var-lib-docker-overlay2-9b490b642429b5c28e8d44b35faf6e307aae46a15b1e3f9b1831fa5f388c73bb\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[31201]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-45722e15a62cabf222444b0d51444444bb46de5236b3dc1b8a860500288627ba\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[31201]: var-lib-docker-overlay2-9b490b642429b5c28e8d44b35faf6e307aae46a15b1e3f9b1831fa5f388c73bb-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[31201]: var-lib-docker-overlay2-45722e15a62cabf222444b0d51444444bb46de5236b3dc1b8a860500288627ba\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-9b490b642429b5c28e8d44b35faf6e307aae46a15b1e3f9b1831fa5f388c73bb-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-45722e15a62cabf222444b0d51444444bb46de5236b3dc1b8a860500288627ba\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-8e3478a5e269b83182a9edcdb4bfc3ce858cf384bc0a2a2bae990c477772fd05\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[31201]: var-lib-docker-overlay2-8e3478a5e269b83182a9edcdb4bfc3ce858cf384bc0a2a2bae990c477772fd05\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-8e3478a5e269b83182a9edcdb4bfc3ce858cf384bc0a2a2bae990c477772fd05\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-34ef3b83bb76ddef629493c268c567781a3de054945348d1d24c68e44db40077\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-34ef3b83bb76ddef629493c268c567781a3de054945348d1d24c68e44db40077\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[31201]: var-lib-docker-overlay2-34ef3b83bb76ddef629493c268c567781a3de054945348d1d24c68e44db40077\x2dinit-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[1]: var-lib-docker-overlay2-45722e15a62cabf222444b0d51444444bb46de5236b3dc1b8a860500288627ba-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[31201]: var-lib-docker-overlay2-45722e15a62cabf222444b0d51444444bb46de5236b3dc1b8a860500288627ba-merged.mount: Succeeded. Apr 16 01:20:26 RPi4 systemd[713]: var-lib-docker-overlay2-45722e15a62cabf222444b0d51444444bb46de5236b3dc1b8a860500288627ba-merged.mount: Succeeded. Apr 16 01:20:27 RPi4 systemd[1]: var-lib-docker-overlay2-8e3478a5e269b83182a9edcdb4bfc3ce858cf384bc0a2a2bae990c477772fd05-merged.mount: Succeeded. Apr 16 01:20:27 RPi4 systemd[31201]: var-lib-docker-overlay2-8e3478a5e269b83182a9edcdb4bfc3ce858cf384bc0a2a2bae990c477772fd05-merged.mount: Succeeded. Apr 16 01:20:27 RPi4 systemd[713]: var-lib-docker-overlay2-34ef3b83bb76ddef629493c268c567781a3de054945348d1d24c68e44db40077-merged.mount: Succeeded. Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered disabled state Apr 16 01:20:27 RPi4 kernel: device veth98776f0 entered promiscuous mode Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered forwarding state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered disabled state Apr 16 01:20:27 RPi4 dhcpcd[444]: veth98776f0: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: vethb8062b7: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: vethb8062b7: carrier acquired Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb8062b7: link becomes ready Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth98776f0: link becomes ready Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered forwarding state Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-9b221860107e: link becomes ready Apr 16 01:20:27 RPi4 dhcpcd[444]: vethb8062b7: IAID b7:aa:67:da Apr 16 01:20:27 RPi4 dhcpcd[444]: vethb8062b7: adding address fe80::4a33:bce1:b4fa:58 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface vethb8062b7.IPv6 with address fe80::4a33:bce1:b4fa:58. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface vethb8062b7.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::4a33:bce1:b4fa:58 on vethb8062b7.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth98776f0: carrier acquired Apr 16 01:20:27 RPi4 dhcpcd[444]: veth98776f0: IAID 16:41:3a:fa Apr 16 01:20:27 RPi4 dhcpcd[444]: veth98776f0: adding address fe80::b74:d7b7:8d90:2707 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth98776f0.IPv6 with address fe80::b74:d7b7:8d90:2707. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth98776f0.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::b74:d7b7:8d90:2707 on veth98776f0.. Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 2(veth0e4987e) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 2(veth0e4987e) entered disabled state Apr 16 01:20:27 RPi4 kernel: device veth0e4987e entered promiscuous mode Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 2(veth0e4987e) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 2(veth0e4987e) entered forwarding state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered disabled state Apr 16 01:20:27 RPi4 kernel: device veth1bacf9e entered promiscuous mode Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered forwarding state Apr 16 01:20:27 RPi4 dhcpcd[444]: veth6918e05: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: veth98776f0: soliciting a DHCP lease Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0e4987e: link becomes ready Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered disabled state Apr 16 01:20:27 RPi4 dhcpcd[444]: veth0e4987e: IAID 3f:3a:98:a5 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth0e4987e: adding address fe80::7d2:c6f2:daf:7e40 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth0e4987e.IPv6 with address fe80::7d2:c6f2:daf:7e40. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth0e4987e.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::7d2:c6f2:daf:7e40 on veth0e4987e.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: vethe1dc48c: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: carrier acquired Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered disabled state Apr 16 01:20:27 RPi4 kernel: device veth91d775b entered promiscuous mode Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered forwarding state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered disabled state Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1bacf9e: link becomes ready Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered forwarding state Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: IAID 3b:55:c7:47 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: adding address fe80::3d8b:cf6a:5811:b67c Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth1bacf9e.IPv6 with address fe80::3d8b:cf6a:5811:b67c. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth1bacf9e.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::3d8b:cf6a:5811:b67c on veth1bacf9e.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth6918e05: carrier acquired Apr 16 01:20:27 RPi4 dhcpcd[444]: veth6918e05: IAID 5c:dc:ff:cc Apr 16 01:20:27 RPi4 dhcpcd[444]: veth6918e05: adding address fe80::ff4:7507:2afa:42e Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth6918e05.IPv6 with address fe80::ff4:7507:2afa:42e. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth6918e05.IPv6 for mDNS. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: carrier lost Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::ff4:7507:2afa:42e on veth6918e05.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: deleting address fe80::3d8b:cf6a:5811:b67c Apr 16 01:20:27 RPi4 dhcpcd[444]: veth6918e05: soliciting an IPv6 router Apr 16 01:20:27 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::3d8b:cf6a:5811:b67c on veth1bacf9e. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth1bacf9e.IPv6 with address fe80::3d8b:cf6a:5811:b67c. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Interface veth1bacf9e.IPv6 no longer relevant for mDNS. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth5fcf0f4: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: veth98776f0: soliciting an IPv6 router Apr 16 01:20:27 RPi4 dhcpcd[444]: vethb8062b7: soliciting a DHCP lease Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth91d775b: link becomes ready Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered forwarding state Apr 16 01:20:27 RPi4 containerd[523]: time="2022-04-16T01:20:27.568427036+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v> Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 5(veth170dc51) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 5(veth170dc51) entered disabled state Apr 16 01:20:27 RPi4 kernel: device veth170dc51 entered promiscuous mode Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 5(veth170dc51) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 5(veth170dc51) entered forwarding state Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: IAID c1:9d:68:cb Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: adding address fe80::b8b:28d:ab05:e500 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth91d775b.IPv6 with address fe80::b8b:28d:ab05:e500. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth91d775b.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::b8b:28d:ab05:e500 on veth91d775b.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: carrier lost Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: deleting address fe80::b8b:28d:ab05:e500 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::b8b:28d:ab05:e500 on veth91d775b. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth91d775b.IPv6 with address fe80::b8b:28d:ab05:e500. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Interface veth91d775b.IPv6 no longer relevant for mDNS. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth170dc51: IAID df:dd:85:b0 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth170dc51: adding address fe80::4a42:7464:5274:c411 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth170dc51.IPv6 with address fe80::4a42:7464:5274:c411. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth170dc51.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::4a42:7464:5274:c411 on veth170dc51.. Apr 16 01:20:27 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-756f67218814e1d6051d467909f8b3a735a86ffbd1e182ee27ad32ab61adab6c-runc.oH5kkJ.mount: Succeeded. Apr 16 01:20:27 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-756f67218814e1d6051d467909f8b3a735a86ffbd1e182ee27ad32ab61adab6c-runc.oH5kkJ.mount: Succeeded. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth77f63fc: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: veth0e4987e: soliciting an IPv6 router Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: carrier acquired Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 6(veth841e5fa) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 6(veth841e5fa) entered disabled state Apr 16 01:20:27 RPi4 kernel: device veth841e5fa entered promiscuous mode Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth170dc51: link becomes ready Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 6(veth841e5fa) entered blocking state Apr 16 01:20:27 RPi4 kernel: br-9b221860107e: port 6(veth841e5fa) entered forwarding state Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: IAID c1:9d:68:cb Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: adding address fe80::b8b:28d:ab05:e500 Apr 16 01:20:27 RPi4 dhcpcd[444]: vethe1dc48c: carrier acquired Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth91d775b.IPv6 with address fe80::b8b:28d:ab05:e500. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth91d775b.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::b8b:28d:ab05:e500 on veth91d775b.. Apr 16 01:20:27 RPi4 dhcpcd[444]: vethe1dc48c: IAID 67:43:62:04 Apr 16 01:20:27 RPi4 dhcpcd[444]: vethe1dc48c: adding address fe80::5d79:91d7:6c76:e693 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: carrier lost Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface vethe1dc48c.IPv6 with address fe80::5d79:91d7:6c76:e693. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface vethe1dc48c.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::5d79:91d7:6c76:e693 on vethe1dc48c.. Apr 16 01:20:27 RPi4 systemd[1]: Started libcontainer container 756f67218814e1d6051d467909f8b3a735a86ffbd1e182ee27ad32ab61adab6c. Apr 16 01:20:27 RPi4 systemd[1]: run-docker-runtime\x2drunc-moby-756f67218814e1d6051d467909f8b3a735a86ffbd1e182ee27ad32ab61adab6c-runc.oH5kkJ.mount: Succeeded. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: deleting address fe80::b8b:28d:ab05:e500 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::b8b:28d:ab05:e500 on veth91d775b. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth91d775b.IPv6 with address fe80::b8b:28d:ab05:e500. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Interface veth91d775b.IPv6 no longer relevant for mDNS. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: carrier acquired Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: IAID 3b:55:c7:47 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth1bacf9e: adding address fe80::3d8b:cf6a:5811:b67c Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth1bacf9e.IPv6 with address fe80::3d8b:cf6a:5811:b67c. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth1bacf9e.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::3d8b:cf6a:5811:b67c on veth1bacf9e.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth5fcf0f4: carrier acquired Apr 16 01:20:27 RPi4 dhcpcd[444]: veth5fcf0f4: IAID 4f:18:52:d3 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth5fcf0f4: adding address fe80::71ab:a7e3:90d2:5db1 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth5fcf0f4.IPv6 with address fe80::71ab:a7e3:90d2:5db1. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth5fcf0f4.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::71ab:a7e3:90d2:5db1 on veth5fcf0f4.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth841e5fa: IAID ca:8c:06:7d Apr 16 01:20:27 RPi4 dhcpcd[444]: veth841e5fa: adding address fe80::873b:8f5b:617c:9e05 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth841e5fa.IPv6 with address fe80::873b:8f5b:617c:9e05. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth841e5fa.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::873b:8f5b:617c:9e05 on veth841e5fa.. Apr 16 01:20:27 RPi4 dhcpcd[444]: vethdfbc788: waiting for carrier Apr 16 01:20:27 RPi4 dhcpcd[444]: vethe1dc48c: soliciting an IPv6 router Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: carrier acquired Apr 16 01:20:27 RPi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth841e5fa: link becomes ready Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: IAID c1:9d:68:cb Apr 16 01:20:27 RPi4 dhcpcd[444]: veth91d775b: adding address fe80::b8b:28d:ab05:e500 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth91d775b.IPv6 with address fe80::b8b:28d:ab05:e500. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth91d775b.IPv6 for mDNS. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth170dc51: carrier lost Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::b8b:28d:ab05:e500 on veth91d775b.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth170dc51: deleting address fe80::4a42:7464:5274:c411 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::4a42:7464:5274:c411 on veth170dc51. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth170dc51.IPv6 with address fe80::4a42:7464:5274:c411. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Interface veth170dc51.IPv6 no longer relevant for mDNS. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth170dc51: carrier acquired Apr 16 01:20:27 RPi4 dhcpcd[444]: veth170dc51: IAID df:dd:85:b0 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth170dc51: adding address fe80::4a42:7464:5274:c411 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth170dc51.IPv6 with address fe80::4a42:7464:5274:c411. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth170dc51.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::4a42:7464:5274:c411 on veth170dc51.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth841e5fa: carrier lost Apr 16 01:20:27 RPi4 dhcpcd[444]: veth841e5fa: deleting address fe80::873b:8f5b:617c:9e05 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::873b:8f5b:617c:9e05 on veth841e5fa. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth841e5fa.IPv6 with address fe80::873b:8f5b:617c:9e05. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Interface veth841e5fa.IPv6 no longer relevant for mDNS. Apr 16 01:20:27 RPi4 dhcpcd[444]: vethb8062b7: soliciting an IPv6 router Apr 16 01:20:27 RPi4 dhcpcd[444]: veth77f63fc: carrier acquired Apr 16 01:20:27 RPi4 dhcpcd[444]: veth77f63fc: IAID 7f:c1:89:28 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth77f63fc: adding address fe80::6ab4:fab1:9272:3322 Apr 16 01:20:27 RPi4 dhcpcd[444]: veth841e5fa: carrier acquired Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth77f63fc.IPv6 with address fe80::6ab4:fab1:9272:3322. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth77f63fc.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::6ab4:fab1:9272:3322 on veth77f63fc.. Apr 16 01:20:27 RPi4 dhcpcd[444]: veth841e5fa: IAID ca:8c:06:7d Apr 16 01:20:27 RPi4 dhcpcd[444]: veth841e5fa: adding address fe80::873b:8f5b:617c:9e05 Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth841e5fa.IPv6 with address fe80::873b:8f5b:617c:9e05. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface veth841e5fa.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::873b:8f5b:617c:9e05 on veth841e5fa.. Apr 16 01:20:27 RPi4 dhcpcd[444]: vethdfbc788: carrier acquired Apr 16 01:20:27 RPi4 dhcpcd[444]: vethdfbc788: IAID 20:7e:6e:cd Apr 16 01:20:27 RPi4 dhcpcd[444]: vethdfbc788: adding address fe80::988c:f6b:d169:8c9f Apr 16 01:20:27 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface vethdfbc788.IPv6 with address fe80::988c:f6b:d169:8c9f. Apr 16 01:20:27 RPi4 avahi-daemon[395]: New relevant interface vethdfbc788.IPv6 for mDNS. Apr 16 01:20:27 RPi4 avahi-daemon[395]: Registering new address record for fe80::988c:f6b:d169:8c9f on vethdfbc788.. Apr 16 01:20:27 RPi4 containerd[523]: time="2022-04-16T01:20:27.957868342+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v> Apr 16 01:20:28 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-bde5883f51bbc3421b30e626f9ccafb55ea0f5c8afa5e6ab9b583548a13c3f7f-runc.05HlWK.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-bde5883f51bbc3421b30e626f9ccafb55ea0f5c8afa5e6ab9b583548a13c3f7f-runc.05HlWK.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[1]: Started libcontainer container bde5883f51bbc3421b30e626f9ccafb55ea0f5c8afa5e6ab9b583548a13c3f7f. Apr 16 01:20:28 RPi4 containerd[523]: time="2022-04-16T01:20:28.123540010+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v> Apr 16 01:20:28 RPi4 systemd[1]: Started libcontainer container ab3f514a7e8b5f89153d3a90702420a94e6d6c36745e166df1e5f0a8fb088c3d. Apr 16 01:20:28 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-ab3f514a7e8b5f89153d3a90702420a94e6d6c36745e166df1e5f0a8fb088c3d-runc.Eu4qZQ.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-ab3f514a7e8b5f89153d3a90702420a94e6d6c36745e166df1e5f0a8fb088c3d-runc.Eu4qZQ.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[1]: run-docker-runtime\x2drunc-moby-ab3f514a7e8b5f89153d3a90702420a94e6d6c36745e166df1e5f0a8fb088c3d-runc.Eu4qZQ.mount: Succeeded. Apr 16 01:20:28 RPi4 dhcpcd[444]: vethdfbc788: soliciting an IPv6 router Apr 16 01:20:28 RPi4 dhcpcd[444]: veth841e5fa: soliciting a DHCP lease Apr 16 01:20:28 RPi4 dhcpcd[444]: veth6918e05: soliciting a DHCP lease Apr 16 01:20:28 RPi4 dhcpcd[444]: vethe1dc48c: soliciting a DHCP lease Apr 16 01:20:28 RPi4 dhcpcd[444]: veth77f63fc: soliciting an IPv6 router Apr 16 01:20:28 RPi4 dhcpcd[444]: veth0e4987e: soliciting a DHCP lease Apr 16 01:20:28 RPi4 dhcpcd[444]: veth91d775b: soliciting an IPv6 router Apr 16 01:20:28 RPi4 containerd[523]: time="2022-04-16T01:20:28.402915225+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v> Apr 16 01:20:28 RPi4 dhcpcd[444]: veth1bacf9e: soliciting an IPv6 router Apr 16 01:20:28 RPi4 dhcpcd[444]: veth5fcf0f4: soliciting an IPv6 router Apr 16 01:20:28 RPi4 dhcpcd[444]: veth170dc51: soliciting a DHCP lease Apr 16 01:20:28 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-4dfd883539a93f1177ac8007b94b85e3df3088193c5a2d3e7d3b6ff9df54d57d-runc.4Cls3o.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[1]: run-docker-runtime\x2drunc-moby-4dfd883539a93f1177ac8007b94b85e3df3088193c5a2d3e7d3b6ff9df54d57d-runc.4Cls3o.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-4dfd883539a93f1177ac8007b94b85e3df3088193c5a2d3e7d3b6ff9df54d57d-runc.4Cls3o.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[1]: Started libcontainer container 4dfd883539a93f1177ac8007b94b85e3df3088193c5a2d3e7d3b6ff9df54d57d. Apr 16 01:20:28 RPi4 dhcpcd[444]: veth5fcf0f4: soliciting a DHCP lease Apr 16 01:20:28 RPi4 avahi-daemon[395]: Registering new address record for fe80::c036:3fff:fe3a:98a5 on veth0e4987e.. Apr 16 01:20:28 RPi4 dhcpcd[444]: vethdfbc788: soliciting a DHCP lease Apr 16 01:20:28 RPi4 containerd[523]: time="2022-04-16T01:20:28.643825230+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v> Apr 16 01:20:28 RPi4 dhcpcd[444]: veth91d775b: soliciting a DHCP lease Apr 16 01:20:28 RPi4 systemd[1]: Started libcontainer container d98305b0b10a65e7ed1ac2d0b197e077a4d5aa3125ee19d700e99ffdde2e2d48. Apr 16 01:20:28 RPi4 systemd[1]: run-docker-runtime\x2drunc-moby-d98305b0b10a65e7ed1ac2d0b197e077a4d5aa3125ee19d700e99ffdde2e2d48-runc.57Mcaf.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-d98305b0b10a65e7ed1ac2d0b197e077a4d5aa3125ee19d700e99ffdde2e2d48-runc.57Mcaf.mount: Succeeded. Apr 16 01:20:28 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-d98305b0b10a65e7ed1ac2d0b197e077a4d5aa3125ee19d700e99ffdde2e2d48-runc.57Mcaf.mount: Succeeded. Apr 16 01:20:28 RPi4 dhcpcd[444]: veth1bacf9e: soliciting a DHCP lease Apr 16 01:20:28 RPi4 dhcpcd[444]: veth77f63fc: soliciting a DHCP lease Apr 16 01:20:28 RPi4 dhcpcd[444]: veth170dc51: soliciting an IPv6 router Apr 16 01:20:28 RPi4 dhcpcd[444]: veth841e5fa: soliciting an IPv6 router Apr 16 01:20:28 RPi4 avahi-daemon[395]: Registering new address record for fe80::28a4:c1ff:fe9d:68cb on veth91d775b.. Apr 16 01:20:28 RPi4 containerd[523]: time="2022-04-16T01:20:28.903666037+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v> Apr 16 01:20:28 RPi4 systemd[1]: Started libcontainer container b12bb0dece86097f53425b02489c0027b2b60857a898c65f6b697ea17119f3d5. Apr 16 01:20:28 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface br-9b221860107e.IPv6 with address fe80::42:11ff:feeb:73d5. Apr 16 01:20:28 RPi4 systemd[713]: run-docker-runtime\x2drunc-moby-b12bb0dece86097f53425b02489c0027b2b60857a898c65f6b697ea17119f3d5-runc.SVQHo9.mount: Succeeded. Apr 16 01:20:28 RPi4 avahi-daemon[395]: New relevant interface br-9b221860107e.IPv6 for mDNS. Apr 16 01:20:28 RPi4 systemd[1]: run-docker-runtime\x2drunc-moby-b12bb0dece86097f53425b02489c0027b2b60857a898c65f6b697ea17119f3d5-runc.SVQHo9.mount: Succeeded. Apr 16 01:20:28 RPi4 avahi-daemon[395]: Registering new address record for fe80::42:11ff:feeb:73d5 on br-9b221860107e.. Apr 16 01:20:28 RPi4 systemd[31201]: run-docker-runtime\x2drunc-moby-b12bb0dece86097f53425b02489c0027b2b60857a898c65f6b697ea17119f3d5-runc.SVQHo9.mount: Succeeded. Apr 16 01:20:29 RPi4 dhcpcd[444]: vethb8062b7: carrier lost Apr 16 01:20:29 RPi4 avahi-daemon[395]: Interface vethb8062b7.IPv6 no longer relevant for mDNS. Apr 16 01:20:29 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface vethb8062b7.IPv6 with address fe80::4a33:bce1:b4fa:58. Apr 16 01:20:29 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::4a33:bce1:b4fa:58 on vethb8062b7. Apr 16 01:20:29 RPi4 dhcpcd[444]: vethb8062b7: deleting address fe80::4a33:bce1:b4fa:58 Apr 16 01:20:29 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered disabled state Apr 16 01:20:29 RPi4 kernel: eth0: renamed from vethb8062b7 Apr 16 01:20:29 RPi4 dhcpcd[444]: vethb8062b7: removing interface Apr 16 01:20:29 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered blocking state Apr 16 01:20:29 RPi4 kernel: br-9b221860107e: port 1(veth98776f0) entered forwarding state Apr 16 01:20:29 RPi4 dhcpcd[444]: veth98776f0: carrier lost Apr 16 01:20:29 RPi4 dhcpcd[444]: veth98776f0: deleting address fe80::b74:d7b7:8d90:2707 Apr 16 01:20:29 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::b74:d7b7:8d90:2707 on veth98776f0. Apr 16 01:20:29 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth98776f0.IPv6 with address fe80::b74:d7b7:8d90:2707. Apr 16 01:20:29 RPi4 avahi-daemon[395]: Interface veth98776f0.IPv6 no longer relevant for mDNS. Apr 16 01:20:29 RPi4 dhcpcd[444]: veth98776f0: carrier acquired Apr 16 01:20:29 RPi4 dhcpcd[444]: veth98776f0: IAID 16:41:3a:fa Apr 16 01:20:29 RPi4 dhcpcd[444]: veth98776f0: adding address fe80::b74:d7b7:8d90:2707 Apr 16 01:20:29 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth98776f0.IPv6 with address fe80::b74:d7b7:8d90:2707. Apr 16 01:20:29 RPi4 avahi-daemon[395]: New relevant interface veth98776f0.IPv6 for mDNS. Apr 16 01:20:29 RPi4 avahi-daemon[395]: Registering new address record for fe80::b74:d7b7:8d90:2707 on veth98776f0.. Apr 16 01:20:29 RPi4 avahi-daemon[395]: Interface vethe1dc48c.IPv6 no longer relevant for mDNS. Apr 16 01:20:29 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface vethe1dc48c.IPv6 with address fe80::5d79:91d7:6c76:e693. Apr 16 01:20:29 RPi4 dhcpcd[444]: vethe1dc48c: carrier lost Apr 16 01:20:29 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::5d79:91d7:6c76:e693 on vethe1dc48c. Apr 16 01:20:29 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered disabled state Apr 16 01:20:29 RPi4 kernel: eth0: renamed from vethe1dc48c Apr 16 01:20:29 RPi4 dhcpcd[444]: vethe1dc48c: deleting address fe80::5d79:91d7:6c76:e693 Apr 16 01:20:29 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered blocking state Apr 16 01:20:29 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered forwarding state Apr 16 01:20:29 RPi4 dhcpcd[444]: vethe1dc48c: removing interface Apr 16 01:20:30 RPi4 dhcpcd[444]: veth1bacf9e: carrier lost Apr 16 01:20:30 RPi4 avahi-daemon[395]: Interface veth6918e05.IPv6 no longer relevant for mDNS. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth6918e05.IPv6 with address fe80::ff4:7507:2afa:42e. Apr 16 01:20:30 RPi4 systemd[1]: docker-ab3f514a7e8b5f89153d3a90702420a94e6d6c36745e166df1e5f0a8fb088c3d.scope: Succeeded. Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 2(veth0e4987e) entered disabled state Apr 16 01:20:30 RPi4 dhcpcd[444]: veth1bacf9e: deleting address fe80::3d8b:cf6a:5811:b67c Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::ff4:7507:2afa:42e on veth6918e05. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::3d8b:cf6a:5811:b67c on veth1bacf9e. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth1bacf9e.IPv6 with address fe80::3d8b:cf6a:5811:b67c. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Interface veth1bacf9e.IPv6 no longer relevant for mDNS. Apr 16 01:20:30 RPi4 kernel: eth0: renamed from veth6918e05 Apr 16 01:20:30 RPi4 dhcpcd[444]: dhcp_readbpf: veth6918e05: Network is down Apr 16 01:20:30 RPi4 dhcpcd[444]: veth6918e05: removing interface Apr 16 01:20:30 RPi4 containerd[523]: time="2022-04-16T01:20:30.190487666+01:00" level=info msg="shim disconnected" id=ab3f514a7e8b5f89153d3a90702420a94e6d6c36745e166df1e5f0a8fb0> Apr 16 01:20:30 RPi4 containerd[523]: time="2022-04-16T01:20:30.190645276+01:00" level=warning msg="cleaning up after shim disconnected" id=ab3f514a7e8b5f89153d3a90702420a94e6d6c> Apr 16 01:20:30 RPi4 containerd[523]: time="2022-04-16T01:20:30.190729516+01:00" level=info msg="cleaning up dead shim" Apr 16 01:20:30 RPi4 dockerd[621]: time="2022-04-16T01:20:30.192913483+01:00" level=info msg="ignoring event" container=ab3f514a7e8b5f89153d3a90702420a94e6d6c36745e166df1e5f0a8fb> Apr 16 01:20:30 RPi4 dhcpcd[444]: veth6918e05: deleting address fe80::ff4:7507:2afa:42e Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 2(veth0e4987e) entered blocking state Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 2(veth0e4987e) entered forwarding state Apr 16 01:20:30 RPi4 avahi-daemon[395]: Interface veth77f63fc.IPv6 no longer relevant for mDNS. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth77f63fc.IPv6 with address fe80::6ab4:fab1:9272:3322. Apr 16 01:20:30 RPi4 containerd[523]: time="2022-04-16T01:20:30.291832220+01:00" level=warning msg="cleanup warnings time=\"2022-04-16T01:20:30+01:00\" level=info msg=\"starting > Apr 16 01:20:30 RPi4 dhcpcd[444]: dhcp_readbpf: veth77f63fc: Network is down Apr 16 01:20:30 RPi4 dhcpcd[444]: veth1bacf9e: carrier acquired Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::6ab4:fab1:9272:3322 on veth77f63fc. Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 5(veth170dc51) entered disabled state Apr 16 01:20:30 RPi4 kernel: eth0: renamed from veth77f63fc Apr 16 01:20:30 RPi4 dhcpcd[444]: veth1bacf9e: IAID 3b:55:c7:47 Apr 16 01:20:30 RPi4 dhcpcd[444]: veth1bacf9e: adding address fe80::3d8b:cf6a:5811:b67c Apr 16 01:20:30 RPi4 dhcpcd[444]: veth77f63fc: removing interface Apr 16 01:20:30 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth1bacf9e.IPv6 with address fe80::3d8b:cf6a:5811:b67c. Apr 16 01:20:30 RPi4 avahi-daemon[395]: New relevant interface veth1bacf9e.IPv6 for mDNS. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Registering new address record for fe80::3d8b:cf6a:5811:b67c on veth1bacf9e.. Apr 16 01:20:30 RPi4 dhcpcd[444]: veth77f63fc: deleting address fe80::6ab4:fab1:9272:3322 Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 5(veth170dc51) entered blocking state Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 5(veth170dc51) entered forwarding state Apr 16 01:20:30 RPi4 dhcpcd[444]: veth98776f0: soliciting a DHCP lease Apr 16 01:20:30 RPi4 dhcpcd[444]: veth0e4987e: carrier lost Apr 16 01:20:30 RPi4 dhcpcd[444]: veth0e4987e: deleting address fe80::7d2:c6f2:daf:7e40 Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::7d2:c6f2:daf:7e40 on veth0e4987e. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth0e4987e.IPv6 with address fe80::7d2:c6f2:daf:7e40. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Joining mDNS multicast group on interface veth0e4987e.IPv6 with address fe80::c036:3fff:fe3a:98a5. Apr 16 01:20:30 RPi4 dhcpcd[444]: veth98776f0: soliciting an IPv6 router Apr 16 01:20:30 RPi4 dhcpcd[444]: veth0e4987e: carrier acquired Apr 16 01:20:30 RPi4 dhcpcd[444]: veth0e4987e: IAID 3f:3a:98:a5 Apr 16 01:20:30 RPi4 dhcpcd[444]: veth170dc51: carrier lost Apr 16 01:20:30 RPi4 avahi-daemon[395]: Interface vethdfbc788.IPv6 no longer relevant for mDNS. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface vethdfbc788.IPv6 with address fe80::988c:f6b:d169:8c9f. Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered disabled state Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::988c:f6b:d169:8c9f on vethdfbc788. Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 6(veth841e5fa) entered disabled state Apr 16 01:20:30 RPi4 kernel: vethe1dc48c: renamed from eth0 Apr 16 01:20:30 RPi4 kernel: eth0: renamed from vethdfbc788 Apr 16 01:20:30 RPi4 avahi-daemon[395]: Interface veth5fcf0f4.IPv6 no longer relevant for mDNS. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth5fcf0f4.IPv6 with address fe80::71ab:a7e3:90d2:5db1. Apr 16 01:20:30 RPi4 dhcpcd[444]: veth170dc51: deleting address fe80::4a42:7464:5274:c411 Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::71ab:a7e3:90d2:5db1 on veth5fcf0f4. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Interface veth1bacf9e.IPv6 no longer relevant for mDNS. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth1bacf9e.IPv6 with address fe80::3d8b:cf6a:5811:b67c. Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered disabled state Apr 16 01:20:30 RPi4 kernel: device veth1bacf9e left promiscuous mode Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 3(veth1bacf9e) entered disabled state Apr 16 01:20:30 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered disabled state Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::3d8b:cf6a:5811:b67c on veth1bacf9e. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Withdrawing address record for fe80::4a42:7464:5274:c411 on veth170dc51. Apr 16 01:20:30 RPi4 avahi-daemon[395]: Leaving mDNS multicast group on interface veth170dc51.IPv6 with address fe80::4a42:7464:5274:c411. Apr 16 01:20:30 RPi4 kernel: eth0: renamed from veth5fcf0f4 Apr 16 01:20:31 RPi4 avahi-daemon[395]: Interface veth170dc51.IPv6 no longer relevant for mDNS. Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 6(veth841e5fa) entered blocking state Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 6(veth841e5fa) entered forwarding state Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered blocking state Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 4(veth91d775b) entered forwarding state Apr 16 01:20:31 RPi4 dhcpcd[444]: veth1bacf9e: soliciting a DHCP lease Apr 16 01:20:31 RPi4 dhcpcd[444]: veth1bacf9e: if_getmtu: No such device Apr 16 01:20:31 RPi4 dhcpcd[444]: veth1bacf9e: soliciting an IPv6 router Apr 16 01:20:31 RPi4 dhcpcd[444]: veth0e4987e: soliciting an IPv6 router Apr 16 01:20:31 RPi4 dhcpcd[444]: dhcp_readbpf: vethdfbc788: Network is down Apr 16 01:20:31 RPi4 systemd-udevd[2853]: vethe1dc48c: Failed to query device driver: No such device Apr 16 01:20:31 RPi4 systemd-udevd[2853]: vethe1dc48c: Failed to get link config: No such device Apr 16 01:20:31 RPi4 systemd[31201]: run-docker-netns-b9c3023a9ea4.mount: Succeeded. Apr 16 01:20:31 RPi4 systemd[1]: run-docker-netns-b9c3023a9ea4.mount: Succeeded. Apr 16 01:20:31 RPi4 systemd[713]: run-docker-netns-b9c3023a9ea4.mount: Succeeded. Apr 16 01:20:31 RPi4 systemd[713]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0-merged.mount: Succeeded. Apr 16 01:20:31 RPi4 systemd[1]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0-merged.mount: Succeeded. Apr 16 01:20:31 RPi4 systemd[31201]: var-lib-docker-overlay2-66fd703b6183b363e99ded8082d7cd15979aad9084ef6713a10803abcb6105f0-merged.mount: Succeeded. Apr 16 01:20:31 RPi4 dhcpcd[444]: veth0e4987e: soliciting a DHCP lease Apr 16 01:20:31 RPi4 dhcpcd[444]: vethdfbc788: removing interface Apr 16 01:20:31 RPi4 dhcpcd[444]: vethdfbc788: deleting address fe80::988c:f6b:d169:8c9f Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 3(veth938b3f8) entered blocking state Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 3(veth938b3f8) entered disabled state Apr 16 01:20:31 RPi4 kernel: device veth938b3f8 entered promiscuous mode Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 3(veth938b3f8) entered blocking state Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 3(veth938b3f8) entered forwarding state Apr 16 01:20:31 RPi4 dhcpcd[444]: dhcp_readbpf: veth5fcf0f4: Network is down Apr 16 01:20:31 RPi4 kernel: br-9b221860107e: port 3(veth938b3f8) entered disabled state Apr 16 01:20:31 RPi4 dhcpcd[444]: dhcp_readbpf: veth1bacf9e: Network is down Apr 16 01:20:31 RPi4 dhcpcd[444]: veth5fcf0f4: removing interface Apr 16 01:20:31 RPi4 dhcpcd[444]: veth5fcf0f4: deleting address fe80::71ab:a7e3:90d2:5db1 Apr 16 01:20:31 RPi4 dhcpcd[444]: veth1bacf9e: removing interface Apr 16 01:20:31 RPi4 dhcpcd[444]: veth1bacf9e: deleting address fe80::3d8b:cf6a:5811:b67c Apr 16 01:20:31 RPi4 dhcpcd[444]: veth5e22b4a: waiting for carrier

confuserated commented 2 years ago

Also:

docker logs grafana standard_init_linux.go:228: exec user process caused: exec format error

confuserated commented 2 years ago

does this mean the wrong version of the code is being pulled?

Paraphraser commented 2 years ago

I hate to say this but I have developed some really deep misgivings about the quality and consistency of Grafana's test regime.

You are correct when you surmise that the wrong version of the code is being pulled. If you take a look on DockerHub you'll see that "latest" was only built for "amd64" so that's what's being pulled and, of course, won't run.

This is not the first time this has happened. Personally, I gave up about two months ago and pinned to Grafana 8.3.4 but I did that to solve a secondary problem where later versions of Grafana didn't "play nice" with Safari on my iDevices. On Discord, people have recommended pinning to "main". If you look at the same DockerHub page, you'll see "main" a few rows down being built for "amd64", "armv7" and "arm64".

If the concept of "pinning" doesn't make sense, in IOTstack the starting point for Grafana is:

grafana:
  container_name: grafana
  image: grafana/grafana
  restart: unless-stopped
  user: "0"
  ports:
    - "3000:3000"
  environment:
    - TZ=Etc/UTC
    - GF_PATHS_DATA=/var/lib/grafana
    - GF_PATHS_LOGS=/var/log/grafana
  volumes:
    - ./volumes/grafana/data:/var/lib/grafana
    - ./volumes/grafana/log:/var/log/grafana

That service definition gets copied into your ~/IOTstack/docker-compose.yml where, depending on what you want Grafana to do for you, you often wind up adding more environment variables, so yours might not quite look like that.

The critical element is:

  image: grafana/grafana

The absence of a tag implies "latest", as in:

  image: grafana/grafana:latest

You can try either of the following:

If you make the change and then:

$ cd ~/IOTstack
$ docker-compose up -d grafana

it should improve the situation.

If you want to chase-up this "bug" yourself, the place to do it is grafana/grafana. Currently reporting over 2,000 open issues…

You could also just add a thumbs-up in Issue 47676.

Hope this helps.

confuserated commented 2 years ago

Thanks very much, that's super helpful and I'm sure that's my problem. I'll have to test that once I've had some sleep 🫥

...moments later, actually I couldn't sleep, techie OCD, it works great, thank you very much.

Paraphraser commented 2 years ago

Having explained about Grafana and (hopefully) gotten you past that problem, there are some other things that struck me in your initial post - which can definitely wait until you've had some sleep.

You said "Home Assistant Server". Can I ask how you built your system? Did you:

  1. Start with Home Assistant's pre-built image and add IOTstack to it, or
  2. Start with Raspberry Pi OS Bullseye and follow home-assistant/supervised-installer, or
  3. some other method?

Until very recently, I offered #2 in PiBuilder but I took it out 10 days ago for the reasons explained here.

That decision began with PiBuilder issue 4.

I'm not at all convinced that HA is ever again going to play nice with IOTstack on the same machine. For me, their decision to start claiming port 53 was the killer. That will wrong-foot anyone who wants to run another DNS service like PiHole or AdGuardHome.

But, if you've got another method that solves all these problems and plays nice with IOTstack then I'd really like to hear about it because there's a reasonable demand to be able to run HA and IOTstack on the same Pi.

When I look through your journalctl output, I see a lot of chatter which makes me think you might not have the first and third recommended system patches in place.

I also see a lot of IPv6. Do you use and rely on IPv6? If not, I've found that my Pis are far more stable and generate far less network chatter if I just turn it off.

I wore the job title of "network consultant" some years ago so it actually pains me to say that. I always thought the day would come when IPv6 would be the one protocol to rule them all. Decades later and we're still not there.

Paraphraser commented 2 years ago

Oh, techie OCD - I recognise that one!

confuserated commented 2 years ago

🤪 you've given me lots to play with there, really must sleep this morning tho'!

I use 3. tho' I think, I run vanilla Pi OS and then add a docker image of HA with no supervisor as I can't see a need for it for me, plus I run 2 pi zeros with pihole on them

Paraphraser commented 2 years ago

Ah! So that's "Home Assistant Container" (which you can get by selecting Home Assistant in the IOTstack menu, and is fully compatible with IOTstack), not "Supervised Home Assistant". Gotcha.

confuserated commented 2 years ago

Yep, thanks again for your help, I implemented your suggestions as well and all is good with the world again 🤩, I think I should probably close this issue now, is that the correct etiquette?

confuserated commented 2 years ago

I should just add I think, that I get around some of the things supervisor gives me by having ESPHome installed in the HA volume (also as a Docker container) which means I can use it as a file editor for the configuration.yaml as well the ESPHome configs, a little odd I know but it works.