-
Incident report
-
Resolution: Duplicate
-
Trivial
-
None
-
6.2.9
-
None
Upon upgradeing to 6.2.9, the Asterisk AMI integration becomes broken / unreliable. Worked with lower versions.
Asterisk template: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/tel/asterisk_http?at=refs%2Fheads%2Frelease%2F6.2
Steps to reproduce:
- Upgrade 6.2.x to 6.2.9
- Navigate to Latest Data
- The template's GetStats item (JavaScript collecting all metrics) generates the error below in the Info column
Result:
{{{{Preprocessing failed for: HTTP/1.1 200 OK..Server: Asterisk/18.16.0..Date: Thu, 30 Mar 2023 06:35:34 GMT..Cache-Control: no...}}}} {{{{1. Failed: Error: log exceeds the maximum size of 8388608 bytes.}}}} {{{{at [anon] (zabbix.c:83) internal}}}} {{{{at [anon] () native strict preventsyield}}}} {{{{at [anon] (function:10)}}}} {{{{at [anon] (function:294) preventsyield}}}}
Consequently, the related Items contains data sporadically. The whole template becomes unreliable.
No AMI related changes were introduced on the Asterisk before the incident started to happen.
I noticed similar Zabbix tickets with other recent versions too, and not just with the Asterisk template. This might be a bit more widespread issue with some recent Zabbix internal (memory?) limit changes...
Zabbix server: Ubuntu 20.04.6 LTS in Azure VM
Zabbix DB: 8.0.32-0ubuntu0.20.04.2 (Ubuntu) colocated
Asterisk host: CentOS 7.8
- duplicates
-
ZBX-22492 "Error: log exceeds the maximum size of 8388608 bytes." logged
- Closed