[ZBX-5851] Zabbix server dont log in level 3 that buffer is full when is problem with write history to db Created: 2012 Nov 14 Updated: 2017 May 30 Resolved: 2012 Dec 24 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Paweł Święcki | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | buffers, history, logging | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux x86_64 + oracle DB 11.2.0.3 |
||
| Description |
|
In normal case when I have problem with db - zabbix inform in log level 3 but not in this case. I have problem with tablespace of History and zabbix server cant write history to DB and it history buffer is full. When buffer is full the zabbix server process is still running (don't die) but also dont log anything. You can only see there is a problem on web gui or get some random alerts from agents that they are not available. When I switch to log lever 4 and restart server it , after a while i can see in log such lines: 14700:20121113:204218.888 History buffer is full. Sleeping for 1 second. IMHO it should log "History buffer is full." on all levers of logging maybe also send email to zabbix admins like DB problems appear. |
| Comments |
| Comment by richlv [ 2012 Nov 14 ] |
|
history buffer being full is not considered a "critical" problem, zabbix server does not shut down - it is hoped that it is a temporary performance problem. if zabbix server would log that, it might spam the log constantly... maybe server could log about this in a throttled manner, like every 10 or 30 seconds. but then some generic throttled logging would be desirable, so it's not reimplemented for each case when we might want such functionality |
| Comment by Paweł Święcki [ 2012 Nov 14 ] |
|
Yes but hypothetically if the problem exist for example 30 min or few hours??? In normal logs you dont have any information, that db isn't updated from that time and monitoring don't work You can only see this on gui , but what if you don't look at gui 24h/7 ? Maybe it is better way to check from zabbix server site that it isn't working ? So it could log something about problem ? Maybe it also should inform about DB problem? |
| Comment by Paweł Święcki [ 2012 Nov 14 ] |
|
Maybe it is a way to check if history in buffer didn't change for period example 10 min So it will be example when db don't allowed insert history It also will don't catch case when zabbix buffer is too small - performance problem (db too slow or too much data in period) Maybe you will give better resolution |
| Comment by Alexei Vladishev [ 2012 Dec 24 ] |
|
Setup a trigger which would alert you if the buffer is full or nearly full for 30 minutes. Zabbix health can be easily monitored using internal items: http://blog.zabbix.com/monitoring-how-busy-zabbix-processes-are/457/ For a quick start just download and activate 'Template App Zabbix Server' which comes with Zabbix 2.0.0 and newer releases. I am closing it, feel free to reopen. |