Hey, I’ve been having the problem on and off all summer, every time I check the logs and it looks fine. this is the normal journalctl logs I get
Oct 28 03:56:28 Paisley-Park syncthing[1663]: [HYS7C] 2023/10/28 03:56:28 INFO: Listen (BEP/tcp): TLS handshake: tls: first record does not look like a TLS handshake
Oct 28 04:00:01 Paisley-Park systemd[1]: Started Logrotate Service.
Oct 28 04:00:01 Paisley-Park systemd[1]: logrotate.service: Deactivated successfully.
Oct 28 04:02:34 Paisley-Park eb9849514a8b[2118]: 2023-10-28 08:02:34 INFO discord.gateway Shard ID None has successfully RESUMED session c1f769a498ef6833e6fb1cae6c661e70.
As you can see, nothing really looks wrong. However this is how it changes when I add the kernel logs
Oct 27 19:50:26 Paisley-Park kernel: NET: Registered PF_PACKET protocol family
Oct 27 19:50:28 Paisley-Park kernel: r8169 0000:06:00.0 enp6s0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 27 19:50:28 Paisley-Park kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 27 19:50:32 Paisley-Park kernel: NFSD: Using nfsdcld client tracking operations.
Oct 27 19:50:32 Paisley-Park kernel: NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
Oct 27 19:50:32 Paisley-Park kernel: Initializing XFRM netlink socket
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 1(vethe4dfab3) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 1(vethe4dfab3) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: device vethe4dfab3 entered promiscuous mode
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 1(vethe4dfab3) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 1(vethe4dfab3) entered forwarding state
Oct 27 19:50:33 Paisley-Park kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-b6c28844d835: link becomes ready
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 1(vethe4dfab3) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 1(veth5c81243) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 1(veth5c81243) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: device veth5c81243 entered promiscuous mode
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 1(veth5c81243) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 1(veth5c81243) entered forwarding state
Oct 27 19:50:33 Paisley-Park kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-c5a700268362: link becomes ready
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 1(veth5c81243) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 2(veth9d47089) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 2(veth9d47089) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: device veth9d47089 entered promiscuous mode
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 2(veth9d47089) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 2(veth9d47089) entered forwarding state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 2(veth358a632) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 2(veth358a632) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: device veth358a632 entered promiscuous mode
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 2(veth358a632) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 2(veth358a632) entered forwarding state
Oct 27 19:50:33 Paisley-Park kernel: br-b6c28844d835: port 2(veth9d47089) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 2(veth358a632) entered disabled state
Oct 27 19:50:33 Paisley-Park kernel: eth0: renamed from vethe61f30a
Oct 27 19:50:33 Paisley-Park kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5c81243: link becomes ready
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 1(veth5c81243) entered blocking state
Oct 27 19:50:33 Paisley-Park kernel: br-c5a700268362: port 1(veth5c81243) entered forwarding state
Oct 27 19:50:34 Paisley-Park kernel: eth0: renamed from veth5a86fe6
Oct 27 19:50:34 Paisley-Park kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe4dfab3: link becomes ready
Oct 27 19:50:34 Paisley-Park kernel: br-b6c28844d835: port 1(vethe4dfab3) entered blocking state
Oct 27 19:50:34 Paisley-Park kernel: br-b6c28844d835: port 1(vethe4dfab3) entered forwarding state
Oct 27 19:50:34 Paisley-Park kernel: eth0: renamed from vethf0a7539
Oct 27 19:50:34 Paisley-Park kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9d47089: link becomes ready
Oct 27 19:50:34 Paisley-Park kernel: br-b6c28844d835: port 2(veth9d47089) entered blocking state
Oct 27 19:50:34 Paisley-Park kernel: br-b6c28844d835: port 2(veth9d47089) entered forwarding state
Oct 27 19:50:34 Paisley-Park kernel: eth1: renamed from veth8c9bd81
Oct 27 19:50:34 Paisley-Park kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth358a632: link becomes ready
Oct 27 19:50:34 Paisley-Park kernel: br-c5a700268362: port 2(veth358a632) entered blocking state
Oct 27 19:50:34 Paisley-Park kernel: br-c5a700268362: port 2(veth358a632) entered forwarding state
To be honest I don’t understand why this would happen, the kernel logs stop hours before the last system log.