Ad Widget

Collapse

After 3.4.6 upgrade all agents are unreachable

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mellis
    Senior Member
    • Oct 2017
    • 145

    #1

    After 3.4.6 upgrade all agents are unreachable

    I did a 3.2.6 to 3.4.6 upgrade. Now after about an hour, all agents become unreachable.

    I found this as a bug but it said it should have been fixed at 3.4.1rc1. This is the second install I have seen this issue.

    I have php 5.6.31, mariadb 10.0.33 and Zabbix 3.4.6.

    If I restart the Zabbix Server it will clear up in 20mins but then stops working.

    When I look in the logs I do not see any errors.

    I have 1 server, 275 agents. 35611 items 11339 trigers

    The servers config:
    StartPollers=52
    StartPollersunreachable=8
    StartTrappers=48
    StartPingers=12
    Start Escalators=26
    CacheSize=42M
    StartDBSynces=6
    HistoryCacheSize=64M
    HistoryIndexCacheSize=18M
    TraendCacheSize=24M
    ValueCacheSize=36M
    TimeOut=30

    I did not have any issues with the 3.2.6.
  • kaspars.mednis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2017
    • 349

    #2
    So you say everything works in the beginning, and then agents becomes unreachable after some time on Zabbix 3.4.6 ?

    What are your history syncer usage in Zabbix internal processes busy graph ?

    may be caused by https://support.zabbix.com/browse/ZBX-13343

    Regards,
    Kaspars

    Comment

    • mellis
      Senior Member
      • Oct 2017
      • 145

      #3
      Thanks

      We had to roll back to the 3.2 and the issue went away.

      I am looking at setting up a national system in 50 data centers each with 600 to 5000 devices/host to monitor. Really did not have time to trouble shoot the 3.4.

      But Thanks

      Comment

      • kaspars.mednis
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Oct 2017
        • 349

        #4
        As far as i know this problem does not persist in 3.4.4, so you can upgrade to that version, or wait till 3.4.7

        But of course, if you do not need new functionality you can stay safe on 3.2

        Just be warned, that 3.2 is already end of support so no new patches will be released.

        3.4 will be supported untill 4.0 LTS comes out.




        Regards,
        Kaspars

        Comment

        Working...