Ad Widget

Collapse

Status of some hosts and triggers stuck

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jherazob
    Junior Member
    • Sep 2011
    • 20

    #1

    Status of some hosts and triggers stuck

    In the continued series of adventures of the server migration (from a server on our LAN running Ubuntu 11.04 with Zabbix 1.8.3 to a dedicated server with Debian Stable 6.03 and Zabbix 1.8.6 manually backported from Debian Testing, all with a PostgreSQL 8.4 database which was entirely migrated from one server to the other), i've hit a couple more snags:
    • There's a server where the majority of triggers stay in "Unknown" state, shown in the triggers page with the red X and "Zabbix was restarted" on the mouseover. It's been like this since yesterday.
    • There's a few hosts, happily collecting information and working fine, but the hosts list shows them as unavailable (the red Z to the right). A mouseover reveals "Got empty string from [IPADDRESS]. Assuming that agent dropped connection because of access permissions", despite the fact that it's collecting information and is not shown as unavailable in the dashboard.

    How do i get those unstuck? Is there some query i can send to Postgres to manually reset those states and leave them to work as they're supposed to?

    Also, is there a way to programatically check if there's more inconsistencies like this to fix them? or is this something one of those things you must check manually?
  • jherazob
    Junior Member
    • Sep 2011
    • 20

    #2
    Update on the problem

    It was decided that the error probably was some version mismatch, so the new server was reinstalled with the same Ubuntu version as the old one (11.04) and the database imported there too.

    The problem persists.

    I manually cleared that error ("UPDATE triggers SET value=0, error='' WHERE error LIKE '%Zabbix was restarted%';"), and everything went well for a while. Then i decided to check if a service restart would replicate the problem, and did one.

    All back to the same error.

    I thought it was because of desynchronized clocks, so i installed ntpdate on them and updated them all against the same server. It made no difference.

    I sincerely don't know what's happening, or how to fix it. Please, if somebody has an idea of how to solve this, please let me know.

    Comment

    • lgalford
      Junior Member
      • Aug 2014
      • 21

      #3
      Did you find a solution

      hi,

      Did you find a solution for this problem I had the same issue and have not been able to fix it. please help

      Comment

      Working...