[ZBX-19532] zabbix server crashes when performing 5.4 upgrade Created: 2021 Jun 09  Updated: 2024 Apr 10  Resolved: 2021 Jun 17

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 5.4.0
Fix Version/s: 5.4.2rc1, 6.0.0alpha1, 6.0 (plan)

Type: Problem report Priority: Blocker
Reporter: Oleksii Zagorskyi Assignee: Andrejs Kozlovs
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File 541-zabbix-server-crashing.log     PNG File initial-issue.png    
Issue Links:
Causes
caused by ZBXNEXT-6289 Convert screens to dashboards (server) Closed
Duplicate
Team: Team C
Sprint: Sprint 77 (Jun 2021)
Story Points: 0.125

 Description   

During 5.2 -> 5.4 upgrade we are constantly getting this error when starting zabbix server:

 66474:20210608:143714.393 Starting Zabbix Server. Zabbix 5.4.0 (revision 5059e20a75).
 66474:20210608:143714.393 ****** Enabled features ******
 66474:20210608:143714.393 SNMP monitoring:           YES
 66474:20210608:143714.393 IPMI monitoring:           YES
 66474:20210608:143714.393 Web monitoring:            YES
 66474:20210608:143714.393 VMware monitoring:         YES
 66474:20210608:143714.393 SMTP authentication:       YES
 66474:20210608:143714.393 ODBC:                      YES
 66474:20210608:143714.393 SSH support:               YES
 66474:20210608:143714.393 IPv6 support:              YES
 66474:20210608:143714.393 TLS support:               YES
 66474:20210608:143714.393 ******************************
 66474:20210608:143714.393 using configuration file: /etc/zabbix/zabbix_server.conf
 66474:20210608:143714.454 current database version (mandatory/optional): 05030094/05030094
 66474:20210608:143714.454 required mandatory version: 05040000
 66474:20210608:143714.454 starting automatic database upgrade
*** stack smashing detected ***: terminated

Before we got this crash, we performed some deletions in database manually. Will be described in comments.



 Comments   
Comment by Andrejs Kozlovs [ 2021 Jun 17 ]

Available in:

Generated at Tue Apr 01 12:30:45 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.