June 24, 20215 yr I noticed that syslog is getting spammed by these kind of messages: Jun 23 02:12:56 Mammon kernel: device vethefce2a1 entered promiscuous mode Jun 23 02:12:56 Mammon kernel: docker0: port 11(vethefce2a1) entered blocking state Jun 23 02:12:56 Mammon kernel: docker0: port 11(vethefce2a1) entered forwarding state Jun 23 02:12:56 Mammon kernel: docker0: port 11(vethefce2a1) entered disabled state Jun 23 02:12:56 Mammon kernel: eth0: renamed from veth7517c37 Jun 23 02:12:56 Mammon kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethefce2a1: link becomes ready Jun 23 02:12:56 Mammon kernel: docker0: port 11(vethefce2a1) entered blocking state Jun 23 02:12:56 Mammon kernel: docker0: port 11(vethefce2a1) entered forwarding state Jun 23 02:12:58 Mammon avahi-daemon[28202]: Joining mDNS multicast group on interface vethefce2a1.IPv6 with address fe80::7411:22ff:fe89:2687. Jun 23 02:12:58 Mammon avahi-daemon[28202]: New relevant interface vethefce2a1.IPv6 for mDNS. Jun 23 02:12:58 Mammon avahi-daemon[28202]: Registering new address record for fe80::7411:22ff:fe89:2687 on vethefce2a1.*. Jun 23 02:12:58 Mammon kernel: veth7517c37: renamed from eth0 Tried to pinpoint the culprit, thought it was 'Transmission_VPN' docker, but after stopping the docker it continued. So unfortunately i couldn't find it with my limited knowledge of Unraid . Is there anyone who can help me in the right direction to solve this? Much appreciated. mammon-diagnostics-20210624-1042.zip
June 24, 20215 yr The problem container has ID 8a49c72ca63f2abb0a1377cb1d795dac4f10e3167cd3582351deaa48aa277d99. If you go to the Docker page of the GUI and turn on Advanced mode the first 12 hexadecimal digits of the ID of each container are displayed. Does that help you to locate it?
June 24, 20215 yr Author Thnx @John_M, learned something today But it seems like it is Transmission_VPN that is spamming syslog... need to look further into that since its working properly for downloads.
June 24, 20215 yr It seems to be re-starting every minute or so. You said that if you stop that particular container the error messages continue? Try setting it not to auto-start, then reboot, start the array, wait for a while with it not running and if the error messages do indeed continue then post new diagnostics. You might have another problem that's hidden in all the noise. I have no experience of Transmission_VPN so you should check its support thread to see if there are any known issues and then check its configuration and/or re-install it.
June 24, 20215 yr Author Thnx for the tip. I just found this in the logs WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected. & Checking port... Port is open: Yes ####################### SUCCESS ####################### Port: 53621 Expiration Thu Aug 26 11:00:52 CEST 2021 ####################### Entering infinite while loop Every 15 minutes, check port status Port is open: Yes ####################### SUCCESS ####################### Port: 53621 Expiration Thu Aug 26 11:00:52 CEST 2021 ####################### Entering infinite while loop Every 15 minutes, check port status Getting a step closer to the cause / solution for it. If is still need help ill post on the support thread. Thnx @John_M
Archived
This topic is now archived and is closed to further replies.