-
Problem report
-
Resolution: Fixed
-
Critical
-
6.0.28rc1, 6.0.28
-
None
-
RHEL 8.9/LTS 6.0.26
-
Sprint candidates, S24-W12/13
-
0.125
Steps to reproduce:
- Use Zabbix Server with 40k NVPS/33M items and 19M triggers/38 Proxies
Result:
DETAIL: User query might have needed to see row versions that must be removed.
[select it.itemid,it.tag,it.value from item_tag it,item_discovery id where it.itemid=id.itemid and id.parent_itemid=9358248]
2118468:20240229:195423.718 [Z3005] query failed: [0] PGRES_FATAL_ERROR:FATAL: connection was terminated due to conflict with recovery
DETAIL: User was holding a relation lock for too long.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
FATAL: server conn crashed?
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
[commit;]
2118468:20240229:195423.718 ERROR: nested transaction detected. Please report it to Zabbix Team.
zabbix_server: lld worker #5 [processed 2 LLD rules, idle 35.715661 sec during 36.058101 sec]: db.c:1061: zbx_db_begin: Assertion `0' failed.
1715494:20240229:195423.758 One child process died (PID:2118468,exitcode/signal:6). Exiting ...
1715494:20240229:195424.427 PROCESS EXIT: 2118468
1715519:20240229:195424.427 HA manager has been paused
zabbix_server [1715494]: Error waiting for process with PID 2118468: [10] No child processes
1715519:20240229:195434.117 HA manager has been stopped
1715494:20240229:195434.515 syncing trend data...
1715494:20240229:195737.528 syncing trend data done
1715494:20240229:195744.352 Zabbix Server stopped. Zabbix 6.0.26 (revision 623853f)
Expected:
No nested transaction.
- caused by
-
ZBX-23012 Slow query from LLD worker
-
- Closed
-