syslog full after a few days


Recommended Posts

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

Link to comment

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.

 

Link to comment

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

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.