[ZBX-12330] Zabbix Proxy, Cannot get the database version. Exiting ... Created: 2017 Jun 30  Updated: 2017 Jul 02  Resolved: 2017 Jul 02

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 3.0.8
Fix Version/s: None

Type: Incident report Priority: Critical
Reporter: sai Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:
  1. cat /etc/*release
    Image:
    Built: Tue Mar 10 09:34:01 UTC 2015
    Patchset:
    LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
    Oracle Linux Server release 6.6
    Red Hat Enterprise Linux Server release 6.6 (Santiago)


 Description   

Hi Team,
We are trying to start zabbix proxy, got below error in proxy log file.
---------------------------------------------------
22052:20170630:144617.184 Starting Zabbix Proxy (active) [Zabbix proxy]. Zabbix 3.0.7 (revision 64609).
22052:20170630:144617.516 **** Enabled features ****
22052:20170630:144617.736 SNMP monitoring: NO
22052:20170630:144617.958 IPMI monitoring: NO
22052:20170630:144618.178 Web monitoring: NO
22052:20170630:144618.399 VMware monitoring: NO
22052:20170630:144618.622 ODBC: NO
22052:20170630:144618.850 SSH2 support: YES
22052:20170630:144619.184 IPv6 support: YES
22052:20170630:144619.407 TLS support: YES
22052:20170630:144619.632 **************************
22052:20170630:144619.853 using configuration file: /home/insplus/Fr_prod/proxy/etc/zabbix_proxy.conf
22052:20170630:144659.238 Cannot get the database version. Exiting ...
---------------------------------------------------------
This is in a Production environment, Please respond.

 Comments   
Comment by richlv [ 2017 Jun 30 ]

most likely the proxy database was incorrectly created or got corrupted.
please see http://zabbix.org/wiki/Getting_help for support options.

Comment by Glebs Ivanovskis (Inactive) [ 2017 Jul 02 ]

I agree with the comment above. No indication of a bug. Closing as Won't Fix.

Generated at Sat Dec 13 22:02:38 EET 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.