Logs filling up

[smaster]

Hello,

My logs have been filling up and I'm not sure why.

You can check the diagnostics that I've provided, but I believe this may be the problem:

Quote

Jul  5 21:37:59 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf9cdf5d: link becomes ready
Jul  5 21:37:59 Tower kernel: br-c7df69fa4ce5: port 50(vethf9cdf5d) entered blocking state
Jul  5 21:37:59 Tower kernel: br-c7df69fa4ce5: port 50(vethf9cdf5d) entered forwarding state
Jul  5 21:37:59 Tower kernel: br-c7df69fa4ce5: port 50(vethf9cdf5d) entered disabled state
Jul  5 21:37:59 Tower kernel: veth98843ac: renamed from eth0
Jul  5 21:37:59 Tower kernel: br-c7df69fa4ce5: port 50(vethf9cdf5d) entered disabled state
Jul  5 21:37:59 Tower kernel: device vethf9cdf5d left promiscuous mode
Jul  5 21:37:59 Tower kernel: br-c7df69fa4ce5: port 50(vethf9cdf5d) entered disabled state
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered blocking state
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered disabled state
Jul  5 21:38:59 Tower kernel: device veth5df03af entered promiscuous mode
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered blocking state
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered forwarding state
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered disabled state
Jul  5 21:38:59 Tower kernel: eth0: renamed from vethe7b671f
Jul  5 21:38:59 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5df03af: link becomes ready
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered blocking state
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered forwarding state
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered disabled state
Jul  5 21:38:59 Tower kernel: vethe7b671f: renamed from eth0
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered disabled state
Jul  5 21:38:59 Tower kernel: device veth5df03af left promiscuous mode
Jul  5 21:38:59 Tower kernel: br-c7df69fa4ce5: port 50(veth5df03af) entered disabled state
Jul  5 21:39:59 Tower kernel: br-c7df69fa4ce5: port 50(vethde89419) entered blocking state
Jul  5 21:39:59 Tower kernel: br-c7df69fa4ce5: port 50(vethde89419) entered disabled state
Jul  5 21:39:59 Tower kernel: device vethde89419 entered promiscuous mode
Jul  5 21:39:59 Tower kernel: br-c7df69fa4ce5: port 50(vethde89419) entered blocking state
Jul  5 21:39:59 Tower kernel: br-c7df69fa4ce5: port 50(vethde89419) entered forwarding state
Jul  5 21:39:59 Tower kernel: br-c7df69fa4ce5: port 50(vethde89419) entered disabled state
Jul  5 21:39:59 Tower kernel: eth0: renamed from veth9b590a8

 

Any idea on how I can fix this?

 

Thank you!

tower-diagnostics-20220706-0921.zip

Edited July 6, 2022 by sergio.calheno

[trurl]

Why do you have 300G docker.img?

[smaster]

2 hours ago, trurl said:

Why do you have 300G docker.img?

 

I don't remember changing this, but since you asked it must not be default. What do you recommend I change it to?

Also, do you think that is the root of the problem? I'm asking, since this is something that started happening more recently and I believe that size must've been changed a very long time ago, for me not to remember.

 

Thanks!

Edited July 6, 2022 by sergio.calheno

[trurl]

20G is default but you are using a little more than that. Set it to 40G and if it grows you have some docker misconfigured.

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

 

Not the reason for filling your logs. Might be related to your dockers though. While you have docker disabled, check syslog to see if those entries stop

[smaster]

 

Does this mean it's already at 80GB? If not, how do I change it to 40GB?

 

Also, your assumption was correct. There is a docker constantly filling up the logs. Is there a fast way to check which one or must I go at it one by one?

 

Thank you for your help.

[trurl]

It means you set it to 80G sometime after you created it at 300G, but since you never recreated it, it is still 300G. See my wiki links above

[smaster]

1 hour ago, trurl said:

It means you set it to 80G sometime after you created it at 300G, but since you never recreated it, it is still 300G. See my wiki links above

 

I have checked the links and I have one question:

I can see that there is a way to reinstall containers, however does that apply to containers in which I have various instances of? How would I go about doing that?

I'm a bit fearful of wiping my docker setup to then have to manually recreate the various instances of some containers I have...

I believe there was nothing mentioning that in the wiki.

 

Thanks again for your time.

[Squid]

28 minutes ago, sergio.calheno said:

I can see that there is a way to reinstall containers, however does that apply to containers in which I have various instances of? How would I go about doing that?

So long as there is a template (ie: if you can click on the icon within the docker tab and there's an "Edit" option), Apps, Previous Apps will show it.

[smaster]

1 hour ago, Squid said:

So long as there is a template (ie: if you can click on the icon within the docker tab and there's an "Edit" option), Apps, Previous Apps will show it.

 

Thank you for your reponse.

Before I delete the docker.img file, as a last ditch effort would it be possible for me to stop all my dockers and one by one find out which is causing the problem? Or is this a more deep-rooted issue that can only be fixed by a wipe?

 

Thanks.

[trurl]

38 minutes ago, sergio.calheno said:

stop all my dockers and one by one find out which is causing the problem? Or is this a more deep-rooted issue that can only be fixed by a wipe?

I doubt recreating docker.img will fix the logging issue so go ahead and see if you can figure that out.

[smaster]

I finally found the culprit! 

For anyone finding this thread, the container causing my logs to be overflowed was:

Rimgo by Joshndroid's Repository.

 

Thanks for your assistance!

Edited July 7, 2022 by sergio.calheno