Ad Widget

Collapse

Server goes wild after Mysql backup

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Buzz
    Junior Member
    • Aug 2007
    • 17

    #1

    Server goes wild after Mysql backup

    Hi,

    Each time I do a backup of my Mysql DB, when the backup is finished, the zabbix_server processes monopolize the CPU of the machine :

    top - 14:45:39 up 22 days, 47 min, 3 users, load average: 4.71, 4.06, 2.75
    Tasks: 123 total, 6 running, 117 sleeping, 0 stopped, 0 zombie
    Cpu(s): 4.3%us, 8.7%sy, 86.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.2%si, 0.0%st
    Mem: 2060008k total, 2042608k used, 17400k free, 20872k buffers
    Swap: 2104472k total, 92k used, 2104380k free, 1735980k cached

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    9003 zabbix 30 5 18028 1404 784 R 49 0.1 4:22.74 zabbix_server
    8999 zabbix 30 5 18028 1404 784 R 49 0.1 4:22.85 zabbix_server
    9001 zabbix 30 5 18028 1404 784 R 45 0.1 4:22.81 zabbix_server
    9007 zabbix 30 5 18028 1404 784 R 44 0.1 4:30.70 zabbix_server

    When I shutdown/restart the zabbix_server processes, everything comes back to normal , until the next backup.

    I tried using mysqldump and mysqlhotcopy; I even tried to use nice to lower the priority of the backup process, but with no luck.

    Then I tried to strace the zabbix_server process, and here's what I got :
    ....
    ....
    accept(4, 0x7fff8f3ef2a0, [25200205213204496]) = -1 EBADF (Bad file descriptor)
    read(4, 0x7fff8f3ef308, 5) = -1 EBADF (Bad file descriptor)
    accept(4, 0x7fff8f3ef2a0, [25200205213204496]) = -1 EBADF (Bad file descriptor)
    ....
    ....
    infinitely .....


    I'm running Zabbix 1.4.4 on SUSE Linux Enterprise Server 10 (x86_64), Kernel 2.6.16.21 and Mysql 5.0.18.


    Did anyone hit the same problem ?
    Any clue would be highly appreciated !

    Regards,
    Buzz.
  • jml
    Junior Member
    • Jan 2008
    • 4

    #2
    Sounds a lot like this:

    Comment

    • Buzz
      Junior Member
      • Aug 2007
      • 17

      #3
      Hi jml,

      Yes, that was the same problem.

      I applied the magic patch, and tried a backup. After the backup, everything was back to normal . Great patch, indeed !

      Many thanks for your quick answer !

      Have a nice day,
      Buzz.

      Comment

      Working...