Ad Widget

Collapse

Zabbix_server keeps shutting down after upgrade

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Niven
    Junior Member
    • Apr 2005
    • 20

    #1

    Zabbix_server keeps shutting down after upgrade

    Hi

    I have just performed an upgrade from Zabbix1.0 to 1.1beta7. I ran through the dpatches including all the alpha patches.

    Whenever i start zabbix_server it starts then shutsdown. Zabbix Log below

    002173:20060301:173931 Starting zabbix_server. ZABBIX 1.1beta7.
    002175:20060301:173931 server #1 started [Alerter]
    002176:20060301:173931 server #2 started [Timer]
    002178:20060301:173931 server #3 started [ICMP pinger]
    002180:20060301:173931 server #4 started [Escalator]
    002184:20060301:173931 server #6 started [Trapper]
    002185:20060301:173931 server #7 started [Trapper]
    002187:20060301:173931 server #8 started [Trapper]
    002189:20060301:173931 server #9 started [Trapper]
    002173:20060301:173931 server #0 started [Housekeeper]
    002173:20060301:173931 ZABBIX server is up.
    002190:20060301:173931 server #10 started [Trapper]
    002180:20060301:173932 Query::select escalationlogid,triggerid, alarmid, escalationid, level, adminlevel, nextcheck, status from escalation_log where status=0 and nextcheck<=1141234771
    002180:20060301:173932 Query failed:Table 'zabbix.escalation_log' doesn't exist [1146]
    002173:20060301:173932 One server process died. Shutting down...
    002173:20060301:173932 ZABBIX server is down.

    I read that the escalation_log is something not to worry about. The odd thing is it obviously worked for a while as i can see the latest data did update at leat once. But now it just wont start.

    Thanks in advance
  • bbrendon
    Senior Member
    • Sep 2005
    • 870

    #2
    sounds like you need an escalation_log table or the permissions on the new one aren't correct. try the query manually.
    Unofficial Zabbix Expert
    Blog, Corporate Site

    Comment

    • Niven
      Junior Member
      • Apr 2005
      • 20

      #3
      Its one of those "the clue is in the question", i created the escalations_log table using the the code in 1.1beta5 schema.sql and problem fixed.

      Thanks for you help

      Comment

      Working...