[ZBX-25711] Zabbix-Server crash signal:11(SIGSEGV) Created: 2024 Dec 10 Updated: 2024 Dec 11 Resolved: 2024 Dec 11 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 6.4.20 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Alexander Plotnikov | Assignee: | Zabbix Development Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix-server 6.4.20, Ubuntu 22.04.5 LTS (5.15.0-126-generic), PHP-FPM 8.2, PostgreSQL 17.2, TimescaleDB 2.17.2, Nginx 1.18. |
||
| Attachments: |
Screenshot_1.png
Screenshot_2.jpg
zabbix_server.log
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Exactly at 00:00, errors were found in the zabbix server log. The frontend, the database worked, but the data on the graph, the latest data was not displayed. All proxies and agents have become unavailable. Errors in the zabbix server log are presented in the attached file. There were a lot of "hanging" PIDs at the time of the crash (screenshot 2). Stopping the zabbix server service (systemctl) did not help, the stop hung. The only way to solve the situation was to restart the virtual machine. |
| Comments |
| Comment by Alexander Vladishev [ 2024 Dec 11 ] |
|
This is a duplicate of |