Access.log constantly filling up after CMK 2.0 upgrade

Upgraded our CMK Enterprise 1.6 to 2.0. Currently running 2.0.0P3 on a Check_MK virt1 1.4.13.

Problem: /var/log/apache2/access.log keeps filling up. Once the log fills up the /rw/ partition, CMK becomes very unresponsive and checks start failing.

The access.log is filling up with the following:

1.2.3.4 - - [19/Apr/2021:09:39:01 +0200] “POST /SITE/check_mk/ajax_figure_dashlet_data.py HTTP/1.1” 200 1774 “http://2.2.2.2/SITE/check_mk/dashboard.py” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36”
1.2.3.4 - - [19/Apr/2021:09:39:01 +0200] “POST /SITE/check_mk/ajax_figure_dashlet_data.py HTTP/1.1” 200 2053 “http://2.2.2.2/SITE/check_mk/dashboard.py” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36”

The 1.2.3.4 is one client that is logged into the dashboard.
There are 2 other clients that are logged in, but does not generate an event in the access.log.

Bumping. Still occuring on a daily basis

It is possible that inside your system is some old incompatible piece of extension to the web interface. Can you have a look at the log file in “~/var/log/web.log”?

I’m experiencing the same issue, logging 42 entries per second, but it seems to be only one user that is causing the issue. As soon as they kill their CMK console browser, the issue stops. At some point in the future after they start up their browser again, the issue resumes.
I’m running OMD - Open Monitoring Distribution Version 2.0.0p9.cre
123.456.789.012 - - [03/Oct/2021:15:40:01 -0400] “POST /akc/check_mk/ajax_figure_dashlet_data.py HTTP/1.1” 200 1288
123.456.789.012 - - [03/Oct/2021:15:40:01 -0400] “POST /akc/check_mk/ajax_figure_dashlet_data.py HTTP/1.1” 200 996

I had the same issue with Checkmk 2.0.
The problem arises only when a user has the “Main Dashboard” open. It disappears after switching to other dashboards like “Host & Service problems”.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.