Ad Widget

Collapse

Problems after upgrade 1.8 to 2.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • leonidasklein
    Junior Member
    • Oct 2011
    • 17

    #1

    Problems after upgrade 1.8 to 2.0

    Hello, I upgraded Zabbix following a procedure on Zabbix website and using yum on CentOS 6.

    The upgrade occured correctly, but now I'm having some problems with zabbix. Lots of erros on Zabbix Server LOG, Templates that I have previously installed aren't working anymore.

    Some errors on Zabbix LOG:
    These I assume are templates error

    snmp_build: unknown failure 1849:20140522:102041.360 SNMP item [dell_bp_temp] on host [SERVER-NAME] failed: first network error, wait for 15 seconds
    snmp_build: unknown failure 1847:20140522:102042.893 SNMP item [dell_bp_temp] on host [SERVER-NAME] failed: first network error, wait for 15 seconds
    snmp_build: unknown failure 1853:20140522:102051.628 SNMP item [dell_bp_temp] on host [SERVER-NAME] failed: another network error, wait for 15 seconds
    snmp_build: unknown failure 1853:20140522:102056.823 SNMP item [dell_bp_temp] on host [SERVER-NAME] failed: another network error, wait for 15 seconds

    These I don't understand, because zabbix seams to be working:

    1855:20140522:102440.703 cannot send list of active checks to [127.0.0.1]: host [Zabbix server] not found

    Can someone help?

    I'm regreating I had updated, I should keep using zabbix 1.8...
  • leonidasklein
    Junior Member
    • Oct 2011
    • 17

    #2
    Upgrade Zabbix-Proxy

    I upgraded zabbix proxy to 2.0 because I read it was proxy 1.8 and server 2.0 were incompatible.

    now I'm receiving other errors

    On the server:
    Autoregistration data from active proxy on [10.20.1.4] failed: proxy [Zabbix proxy] not found

    On The proxy:
    Heartbeat message failed
    cannot send list of active checks to [X.X.X.X]: host [XXXXXX] not found

    If i look on the painel it seams OK, that is very strange!!!

    Comment

    • aib
      Senior Member
      • Jan 2014
      • 1615

      #3
      Check .conf files.
      looks like you faced up with incompatibility of config files.
      Sincerely yours,
      Aleksey

      Comment

      • leonidasklein
        Junior Member
        • Oct 2011
        • 17

        #4
        Perfect!

        Perfect! it is working now, I still have other issues. But I'll post them on diferent topics.

        I replaced the .conf files with .conf.rpmnew and it started working.

        Thank you so much

        Comment

        Working...