Ad Widget

Collapse

Question on Upgrading Zabbex 3.4.15 up to 4.0+

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ZFPuhi
    Junior Member
    • Oct 2019
    • 10

    #1

    Question on Upgrading Zabbex 3.4.15 up to 4.0+

    Hello,

    My question is related to that we have some old production servers that are running CentOS 5 (ye I know), for which there aren't zaabix_agent packages. What is the possible update from 3.4 up to 4.0 without messing with those servers or the option is to keep 2 zabbix versions 3.4 and move for the rest of the servers to 4.0?

    Looking forward to hearing any ideas.

  • ZFPuhi
    Junior Member
    • Oct 2019
    • 10

    #2
    Hello,

    Sorry for bumping the topic but I wasn't able to find a way around that still.

    Any tips / suggestions will be appreciated.

    Comment

    • Atsushi
      Senior Member
      • Aug 2013
      • 2028

      #3
      The combination of Zabbix server and Zabbix agent versions can be monitored if Zabbix server is newer. For example, a combination of Zabbix server version 4.0 and Zabbix agent 3.4 is possible. However, it cannot be monitored using the new Zabbix 4.0 function on the Zabbix agent side.
      On CentOS 5, you may compile from source and install a new version of Zabbix agent.

      Comment

      • ZFPuhi
        Junior Member
        • Oct 2019
        • 10

        #4
        In this case I was able to indeedo update the:

        Zabbix server 3.4 up to 4.0.15
        Zabbix Proxy and agent updated from 3.4 to 4.0.15 this includes even those that where on a Centos 5 using commands such as:

        wget http://repo.zabbix.com/zabbix/4.0/rh...1.el5.i386.rpm
        /etc/init.d/zabbix-agent stop
        rpm -U zabbix-agent-4.0.15-1.el5.i386.rpm --nosignature


        Afterwards simply using 'diff -u <old config> <new config>.rpmnew' to see the changes and add the correct settings to the new file.

        Then simply /etc/init.d/zabbix-agent start and afterwards check it's log tail -f /var/log/zabbix/zabbix_agentd.log . All went good to be honest, the only small issues that I encountered was with the RPM command, needed to be with nosignature otherwise won't work correctly.

        Hope this helps anyone in the future.

        Comment

        Working...