Ad Widget

Collapse

Zabbix 1.8.2 - deadlock on PostgreSQL

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • petr5250
    Junior Member
    • Apr 2010
    • 5

    #1

    Zabbix 1.8.2 - deadlock on PostgreSQL

    Hello,
    I've installed Zabbix 1.8.2 several weeks ago, and I'm experiencing DB deadlocks, which occurs on randomly. Here is PostgreSQL log:

    Code:
    2010-05-16 19:58:55 CESTERROR:  deadlock detected
    2010-05-16 19:58:55 CESTDETAIL:  Process 28227 waits for ExclusiveLock on tuple (11,17) of relation 1571149337 of database 1569403200; blocked by process 28220.
    2010-05-16 19:58:55 CESTSTATEMENT:  update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-16 19:58:57 CESTERROR:  current transaction is aborted, commands ignored until end of transaction block
    2010-05-16 19:58:57 CESTSTATEMENT:  select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-16 19:58:57 CESTERROR:  current transaction is aborted, commands ignored until end of transaction block
    2010-05-16 19:58:57 CESTSTATEMENT:  select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-16 19:58:57 CESTERROR:  current transaction is aborted, commands ignored until end of transaction block
    2010-05-16 19:58:57 CESTSTATEMENT:  select max(eventid) from events where eventid between 0 and 99999999999999
    2010-05-16 19:58:57 CESTERROR:  current transaction is aborted, commands ignored until end of transaction block
    2010-05-16 19:58:57 CESTSTATEMENT:  insert into ids (nodeid,table_name,field_name,nextid) values (0,'events','eventid',0)
    2010-05-16 19:58:57 CESTERROR:  current transaction is aborted, commands ignored until end of transaction block
    ...
    Can anyone help me?

    Thanks
    Petr

    Zabbix server 1.8.2
    Postgres SQL 8.2.0
    Last edited by petr5250; 17-05-2010, 23:09.
  • sersad
    Senior Member
    • May 2009
    • 518

    #2
    И я поймал такую же ошибку

    2010-05-17 08:08:37 MSD STATEMENT: update ids set nextid=nextid+45 where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: select max(eventid) from events where eventid between 0 and 99999999999999
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: insert into ids (nodeid,table_name,field_name,nextid) values (0,'events','eventid',0)
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid'
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: select max(eventid) from events where eventid between 0 and 99999999999999
    2010-05-17 08:08:37 MSD ERROR: current transaction is aborted, commands ignored until end of transaction block
    2010-05-17 08:08:37 MSD STATEMENT: insert into ids (nodeid,table_name,field_name,nextid) values (0,'events','eventid',0)
    В лог начали валить подобные ошибки в течении 1 часа лог вырос до 7 гигов.

    Состояние Zabbix
    Параметр Значение Детали
    Zabbix сервер запущен Да -
    Количество узлов сети (контролируется/не контролируется/шаблоны/удалено) 309 167 / 81 / 61
    Количество элементов данных (активных/неактивных/не поддерживается)[trapper] 212567 100502 / 66169 / 45896
    Количество триггеров (активированных/деактивированных)[истина/неизвестно/ложь] 75610 49155 / 26455 [198 / 4077 / 44880]
    Количество пользователей 16 3
    Требуемое быстродействие сервера, новые значения в секунду 73 -
    Ошибка не понятна, так как eventid в таблице events bigint
    nextid в ids тоже bigint

    Zabbix server 1.8.2
    Postgres SQL 8.3
    Ubuntu server 9.10 AMD64
    Last edited by sersad; 17-05-2010, 07:15.

    Comment

    • sersad
      Senior Member
      • May 2009
      • 518

      #3
      I need help!
      Zabbix Server 1.8.2 (revision 11211).
      PostgreSQL 8.3.10
      Last edited by sersad; 17-05-2010, 11:10.

      Comment

      • petr5250
        Junior Member
        • Apr 2010
        • 5

        #4
        Anything new to this issue?

        Comment

        • sersad
          Senior Member
          • May 2009
          • 518

          #5
          I made autovacuum with DB and change postgress config

          Comment

          • sersad
            Senior Member
            • May 2009
            • 518

            #6
            In ver 1.8.5 deadlock which happens on random criteria.
            Any idea?

            Comment

            Working...