Ad Widget

Collapse

zabbix server crash

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dmitriy Kirhlarov
    Member
    • Jun 2007
    • 40

    #1

    zabbix server crash

    FreeBSD 7.0-20071107-SNAP
    zabbix-1.4.4,1
    postgresql-server-8.2.5_2

    After 2 week zabbix server die. Log file:
    42484:20080112:040021 Connection to database 'zabbix' failed: FATAL: the database system is in recovery mode

    42484:20080112:040021 Query::select oid from pg_type where typname = 'bytea'
    42484:20080112:040021 Query failed:Result is NULL
    42482:20080112:040021 Connection to database 'zabbix' failed: FATAL: the database system is in recovery mode

    42482:20080112:040021 Query::select oid from pg_type where typname = 'bytea'
    42482:20080112:040021 Query failed:Result is NULL
    42490:20080112:040021 Query::select httptestid,name,applicationid,nextcheck,status,del ay,macros,agent from httptest where status=0 and nextcheck<=1200110421 and mod(httptestid,5)=3 and httptestid>=100000000000000*0 and httptestid<=(100000000000000*0+99999999999999)
    42490:20080112:040021 Query failed:PGRES_FATAL_ERROR:PANIC: stuck spinlock (0x803ad1920) detected at dynahash.c:980
    server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.

    42489:20080112:040021 Query::select httptestid,name,applicationid,nextcheck,status,del ay,macros,agent from httptest where status=0 and nextcheck<=1200110421 and mod(httptestid,5)=2 and httptestid>=100000000000000*0 and httptestid<=(100000000000000*0+99999999999999)
    42489:20080112:040021 Query failed:PGRES_FATAL_ERROR:server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.

    42488:20080112:040021 Query::select count(*),min(nextcheck) from httptest t where t.status=0 and mod(t.httptestid,5)=1 and t.httptestid>=100000000000000*0 and t.httptestid<=(100000000000000*0+99999999999999)
    42488:20080112:040021 Query failed:PGRES_FATAL_ERROR:server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.

    42487:20080112:040021 Query::select httptestid,name,applicationid,nextcheck,status,del ay,macros,agent from httptest where status=0 and nextcheck<=1200110421 and mod(httptestid,5)=0 and httptestid>=100000000000000*0 and httptestid<=(100000000000000*0+99999999999999)
    42487:20080112:040021 Query failed:PGRES_FATAL_ERROR:server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.

    42491:20080112:040021 Query::select count(*),min(nextcheck) from httptest t where t.status=0 and mod(t.httptestid,5)=4 and t.httptestid>=100000000000000*0 and t.httptestid<=(100000000000000*0+99999999999999)
    42491:20080112:040021 Query failed:PGRES_FATAL_ERROR:server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.

    42474:20080112:040021 Query::select i.itemid,i.key_,h.host,h.port,i.delay,i.descriptio n,i.nextcheck,i.type,i.snmp_community,i.snmp_oid,h .useip,h.ip,i.history,i.lastvalue,i.prevvalue,i.ho stid,h.status,i.value_type,h.errors_from,i.snmp_po rt,i.delta,i.prevorgvalue,i.lastclock,i.units,i.mu ltiplier,i.snmpv3_securityname,i.snmpv3_securityle vel,i.snmpv3_authpassphrase,i.snmpv3_privpassphras e,i.formula,h.available,i.status,i.trapper_hosts,i .logtimefmt,i.valuemapid,i.delay_flex,h.dns from hosts h, items i where i.nextcheck<=1200110421 and i.status in (0,3) and i.type not in (2,7,9) and h.status=0 and h.disable_until<=1200110421 and h.errors_from=0 and h.hostid=i.hostid and mod(i.itemid,9)=7 and i.key_ not in ('status','icmpping','icmppingsec','zabbix[log]') and h.hostid>=100000000000000*0 and h.hostid<=(100000000000000*0+99999999999999) order by i.nextcheck
    42474:20080112:040021 Query failed:PGRES_FATAL_ERROR:server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.

    42464:20080112:040021 One child process died. Exiting ...
    42464:20080112:040023 ZABBIX Server stopped
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    It looks like problems happening on PostgreSQL side.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • Dmitriy Kirhlarov
      Member
      • Jun 2007
      • 40

      #3
      Originally posted by Alexei
      It looks like problems happening on PostgreSQL side.
      Yep. It was deadlock on zfs.

      Comment

      Working...