Ad Widget

Collapse

zabbix 1.4.4, postgres backend problem

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

    #1

    zabbix 1.4.4, postgres backend problem

    zabbix server die this weekend with diagnose:
    2174:20080201:190029 Active parameter [vfs.fs.size[/data,total]] is not supported by agent on host [infra.mgmt.vega.ru]
    2172:20080201:190030 Active parameter [vfs.fs.inode[/data,free]] is not supported by agent on host [infra.mgmt.vega.ru]
    2173:20080201:190030 Query::insert into trends (clock,itemid,num,value_min,value_avg,value_max) values (1201892400,25302,1,358658.000000,358658.000000,35 8658.000000)
    2173:20080201:190030 Query failed:PGRES_FATAL_ERROR:ERROR: duplicate key violates unique constraint "trends_pkey"

    2173:20080201:190030 Query::update items set nextcheck=1201892490,prevvalue=lastvalue,lastvalue ='358658',lastclock=1201892430 where itemid=25302
    2173:20080201:190030 Query failed:PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of transaction block

    2173:20080201:190030 Query::select distinct function,parameter,itemid,lastvalue from functions where itemid=25302
    2173:20080201:190030 Query failed:PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of transaction block

    2172:20080201:190031 Active parameter [vfs.fs.inode[/data,total]] is not supported by agent on host [infra.mgmt.vega.ru]
    2158:20080201:190031 One child process died. Exiting ...
    2158:20080201:190033 ZABBIX Server stopped
  • Dmitriy Kirhlarov
    Member
    • Jun 2007
    • 40

    #2
    [QUOTE=Dmitriy Kirhlarov;30364]zabbix server die this weekend with diagnose:

    get this problem again:
    13832:20080204:160022 Query::insert into trends (clock,itemid,num,value_min,value_avg,value_max) values (1202140800,25232,1,1282932736.000000,1282932736.0 00000,1282932736.000000)
    13832:20080204:160022 Query failed:PGRES_FATAL_ERROR:ERROR: duplicate key violates unique constraint "trends_pkey"

    13832:20080204:160022 Query::update items set nextcheck=1202140882,prevvalue=lastvalue,lastvalue ='1282932736',lastclock=1202140822 where itemid=25232
    13832:20080204:160022 Query failed:PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of transaction block

    13832:20080204:160022 Query::select distinct function,parameter,itemid,lastvalue from functions where itemid=25232
    13832:20080204:160022 Query failed:PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of transaction block

    13820:20080204:160023 One child process died. Exiting ...
    13820:20080204:160025 ZABBIX Server stopped

    Comment

    • Dmitriy Kirhlarov
      Member
      • Jun 2007
      • 40

      #3
      other two crashes (zabbix 1.4.4 with postgres backend)

      Is it postgres problem or zabbix?

      4090:20080210:080218 Query::commit;
      4090:20080210:080218 Query failed:PGRES_FATAL_ERROR:PANIC: stuck spinlock (0x801900240) detected at lwlock.c:379
      server closed the connection unexpectedly
      This probably means the server terminated abnormally
      before or while processing the request.

      4090:20080210:080218 Query::select count(*),min(nextcheck) from items i,hosts h where h.status=0 and h.disable_until<1202630538 and h.errors_from=0 and h.hostid=i.hostid and i.status in (0,3) and i.type not in (2,7,9) and mod(i.itemid,9)=6 and i.key_ not in ('status','icmpping','icmppingsec','zabbix[log]') and h.hostid>=100000000000000*0 and h.hostid<=(100000000000000*0+99999999999999)
      4090:20080210:080218 Query failed:Result is NULL
      4081:20080210:080218 One child process died. Exiting ...
      4081:20080210:080220 ZABBIX Server stopped



      91378:20080211:160032 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_ty
      pe,h.errors_from,i.snmp_port,i.delta,i.prevorgvalu e,i.lastclock,i.units,i.multiplier,i.snmpv3_securi tyname,i.snmpv3_securitylevel,i.snmpv3_authpassphr ase,i.snmpv3_privpassphrase,i.formula,h.available, i.status,i.
      trapper_hosts,i.logtimefmt,i.valuemapid,i.delay_fl ex,h.dns from hosts h, items i where i.nextcheck<=1202745632 and i.status in (0,3) and i.type not in (2,7,9) and h.status=0 and h.disable_until<=1202745632 and h
      .errors_from=0 and h.hostid=i.hostid and mod(i.itemid,9)=5 and i.key_ not in ('status','icmpping','icmppingsec','zabbix[log]') and h.hostid>=100000000000000*0 and h.hostid<=(100000000000000*0+99999999999999) o
      rder by i.nextcheck
      91378:20080211:160032 Query failed:PGRES_FATAL_ERROR:server closed the connection unexpectedly
      This probably means the server terminated abnormally
      before or while processing the request.

      WARNING: terminating connection because of crash of another server process

      Comment

      Working...