Ad Widget

Collapse

new deadlock issues in 1.6.3-pre

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • xs-
    Senior Member
    Zabbix Certified Specialist
    • Dec 2007
    • 393

    #1

    new deadlock issues in 1.6.3-pre

    Recently patches were submitted to fix some DM deadlock issues.
    It seems this introduced new deadlock issues or left some older issues unsolved.

    Here is a short part of log displaying these deadlog messages.
    12605:20090318:161500 [Z3005] Query failed: [1213] Deadlock found when trying to get lock; try restarting transaction [update functions set lastvalue='12445615' where itemid=100100000021090 and function='last' and parameter='0';
    12605:20090318:163546 [Z3005] Query failed: [1213] Deadlock found when trying to get lock; try restarting transaction [update functions set lastvalue='50.000722' where itemid=100100000020458 and function='last' and parameter='0';
    12605:20090318:164632 [Z3005] Query failed: [1213] Deadlock found when trying to get lock; try restarting transaction [update functions set lastvalue='0' where itemid=100100000021405 and function='min' and parameter='1800';
    12605:20090318:170522 [Z3005] Query failed: [1213] Deadlock found when trying to get lock; try restarting transaction [update functions set lastvalue='12451732' where itemid=100100000021117 and function='last' and parameter='0';
    12605:20090318:170726 [Z3005] Query failed: [1213] Deadlock found when trying to get lock; try restarting transaction [update functions set lastvalue='0.77' where itemid=100100000020099 and function='min' and parameter='600';
    12605:20090318:171539 [Z3005] Query failed: [1213] Deadlock found when trying to get lock; try restarting transaction [update functions set lastvalue='6379402' where itemid=100100000021132 and function='last' and parameter='0';
    12605:20090318:171744 [Z3005] Query failed: [1213] Deadlock found when trying to get lock; try restarting transaction [update functions set lastvalue='0.1328' where itemid=100100000020780 and function='min' and parameter='600';
  • Sasha
    Zabbix developer
    • Sep 2007
    • 60

    #2
    Hi!
    Thank you for reporting this problem.
    Please inform what OS, DB (including version) do you have.
    ZABBIX Developer
    Riga, Latvia

    Comment

    • xs-
      Senior Member
      Zabbix Certified Specialist
      • Dec 2007
      • 393

      #3
      My appologies, completely forgot to add info

      All nodes run the following:
      - Ubuntu 8.04TLS

      All nodes have a separate database server
      - Ubuntu 8.04 TLS
      - Mysql 5.0

      The pasted log is from one of the child nodes

      Comment

      • xs-
        Senior Member
        Zabbix Certified Specialist
        • Dec 2007
        • 393

        #4
        Issue still remains in 1.6.4

        Comment

        • jroberson
          Senior Member
          • May 2008
          • 124

          #5
          I just received this same/similar error myself while trying to add a new trigger to a template with about 50+ hosts assosiated. I tried it a few times and eventually got it to work by closing all other browsers that were logged into the Zabbix front-end. I tried it a few other times and it works as long as I don't have any other connections to the server. I only have one central Zabbix server at this time, so I'm not using distributed monitoring.

          Zabbix Info:
          Version 1.6.4
          hosts 62
          Number of items 3137
          Number of triggers 776

          OS: Centos 5.3
          MySQL :Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i686) using readline 5.0

          I am using DB_Syncers

          Comment

          Working...