[ZBX-25488] Proxy crash ERROR: nested transaction detected. Please report it to Zabbix Team. Created: 2024 Nov 01 Updated: 2024 Nov 01 Resolved: 2024 Nov 01 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P) |
| Affects Version/s: | 7.0.4 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Kim Jongkwon | Assignee: | Zabbix Support Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix Server & Proxy：7.0.3 |
||
| Issue Links: |
|
||||||||
| Description |
|
Zabbix proxy trapper process is repeatedly crashing due to this errors, Could you look into a fix to prevent the crash? We’re observing in this logs include issues with active checks not being sent some reasons and “nested transaction detected” messages 698652:20241017:120351.033 cannot send list of active checks to "xx.xx.xx.xx": host [xxxxx] not found 698652:20241017:120351.040 cannot send list of active checks to "xx.xx.xx.xx": host [xxxxx] not found 698652:20241017:120351.046 cannot send list of active checks to "xx.xx.xx.xx": host [xxxxx] not found 698652:20241017:120351.053 cannot send list of active checks to "xx.xx.xx.xx": host [xxxxx] not found 698652:20241017:120351.059 cannot send list of active checks to "xx.xx.xx.xx": host [xxxxx] not found 698652:20241017:120351.066 cannot send list of active checks to "xx.xx.xx.xx": host [xxxxx] not found 698652:20241017:120351.072 cannot send list of active checks to "xx.xx.xx.xx": host [xxxxx] not found 698652:20241017:120351.087 ERROR: nested transaction detected. Please report it to Zabbix Team. zabbix_proxy: trapper #4 [processing data]: db.c:1036: zbx_db_begin_basic: Assertion `0' failed. 698643:20241017:120351.161 One child process died (PID:698652,exitcode/signal:6). Exiting ... 702830:20241017:140325.686 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected 702830:20241017:140325.692 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected 702830:20241017:140325.699 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected 702830:20241017:140325.705 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected 702830:20241017:140325.712 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected 702830:20241017:140325.719 failed to accept an incoming connection: connection rejected, getpeername() failed: [107] Transport endpoint is not connected 702830:20241017:140325.753 ERROR: nested transaction detected. Please report it to Zabbix Team. zabbix_proxy: trapper #5 [processing data]: db.c:1036: zbx_db_begin_basic: Assertion `0' failed. 702820:20241017:140326.843 One child process died (PID:702830,exitcode/signal:6). Exiting ... There seem to be multiple “host not found” and “connection rejected” errors before the trapper crashes. FYI: PostgreSQL error logs are "unexpected EOF on client connection with an open transaction" in Japanese 2024-10-17 12:03:51.161 JST [698682] LOG: トランザクションを実行中のクライアント接続で想定外のEOFがありました 2024-10-17 14:03:25.835 JST [702860] LOG: トランザクションを実行中のクライアント接続で想定外のEOFがありました |