Fix Common Problems Warning: /var/log is getting full (currently 53 % used)

[bobalot]

Hi,

 

I received the following warning through the Fix Common Problems plugin:

 

Quote

/var/log is getting full (currently 53 % used)

 

With the advice:

 

Quote

Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your Diagnostics.

 

My uptime is only 3 months.

 

I thought it might be mover log spamming (I read some previous posts with this error), but it wasn't that.

 

I can't work out what is causing this issue.

 

I have attached the Diagnostics file.

 

Any help would be appreciated.

tower-diagnostics-20230410-1537.zip

[itimpi]

looks like you may have a docker container continually crashing and trying to restart.    You should be able to work out which one by examining their logs and/or stopping them until the messages stop appearing in your log every few minutes.

 

 

[bobalot]

4 hours ago, itimpi said:

looks like you may have a docker container continually crashing and trying to restart.    You should be able to work out which one by examining their logs and/or stopping them until the messages stop appearing in your log every few minutes.

 

 

I deleted a few dockers I wasn't using any more and fixed a few that had various issues (not talking to each other, VPN was not working, etc.).

 

How do I tell the problem is sorted? Also how would I clear the var/logs?

[itimpi]

Just now, bobalot said:

How do I tell the problem is sorted? Also how would I clear the var/logs?

By the fact that the repeating message stops appearing in the syslog every few minutes (there is a button at the top right of the GUI to display the syslog).   The syslog is in RAM and gets cleared when you reboot.

[bobalot]

38 minutes ago, itimpi said:

By the fact that the repeating message stops appearing in the syslog every few minutes (there is a button at the top right of the GUI to display the syslog).   The syslog is in RAM and gets cleared when you reboot.

Cheers. I restarted and it cleared the error.

 

Regarding the syslog, is repeating message you are referring to:

 

"port X (XXXXXX) entered blocking state"

"port X (XXXXXX) entered forwarding state"

"port X (XXXXXX) entered disabled state"?