Author Topic: loggerd load CPU  (Read 1605 times)

chrystophe

  • Zen Apprentice
  • *
  • Posts: 21
  • Karma: +0/-0
    • View Profile
loggerd load CPU
« on: October 24, 2013, 11:06:27 am »
hello,

I have this service that takes me a lot of CPU load, I scoured a lot of support / various forums.
I disable the monitoring modules and events.
and I updated all packages in Zentyal ....

Here are some logs that speak more ...



Quote
#/var/log/zentyal/zentyal.log
    2013/10/20 17:37:49 ERROR> MyDBEngine.pm:146 EBox::MyDBEngine::_disconnect - There wasn't a database connection, check if database exists\n
    2013/10/20 17:37:51 ERROR> MyDBEngine.pm:146 EBox::MyDBEngine::_disconnect - There wasn't a database connection, check if database exists\n
    2013/10/20 17:37:54 ERROR> MyDBEngine.pm:146 EBox::MyDBEngine::_disconnect - There wasn't a database connection, check if database exists\n
    2013/10/20 17:37:56 ERROR> MyDBEngine.pm:146 EBox::MyDBEngine::_disconnect - There wasn't a database connection, check if database exists\n
    2013/10/20 17:37:58 ERROR> MyDBEngine.pm:146 EBox::MyDBEngine::_disconnect - There wasn't a database connection, check if database exists\n
    ....
    ....



Quote
    #/var/log/kern.log
    Oct 20 09:56:49 zentyal2 kernel: [1041435.650039] init: ebox.loggerd main process (19970) terminated with status 9
    Oct 20 09:56:49 zentyal2 kernel: [1041435.650156] init: ebox.loggerd main process ended, respawning
    Oct 20 09:56:52 zentyal2 kernel: [1041437.963558] init: ebox.loggerd main process (19984) terminated with status 9
    Oct 20 09:56:52 zentyal2 kernel: [1041437.963675] init: ebox.loggerd main process ended, respawning
    Oct 20 09:56:54 zentyal2 kernel: [1041440.280147] init: ebox.loggerd main process (19998) terminated with status 9
    Oct 20 09:56:54 zentyal2 kernel: [1041440.280264] init: ebox.loggerd main process ended, respawning
    Oct 20 09:56:56 zentyal2 kernel: [1041442.579196] init: ebox.loggerd main process (20012) terminated with status 9
    Oct 20 09:56:56 zentyal2 kernel: [1041442.579314] init: ebox.loggerd main process ended, respawning
    Oct 20 09:56:58 zentyal2 kernel: [1041444.886009] init: ebox.loggerd main process (20026) terminated with status 9
    Oct 20 09:56:58 zentyal2 kernel: [1041444.886151] init: ebox.loggerd main process ended, respawning
    Oct 20 09:57:01 zentyal2 kernel: [1041447.194552] init: ebox.loggerd main process (20040) terminated with status 9
    Oct 20 09:57:01 zentyal2 kernel: [1041447.194694] init: ebox.loggerd main process ended, respawning
    Oct 20 09:57:03 zentyal2 kernel: [1041449.504243] init: ebox.loggerd main process (20054) terminated with status 9
    Oct 20 09:57:03 zentyal2 kernel: [1041449.504386] init: ebox.loggerd main process ended, respawning
    Oct 20 09:57:05 zentyal2 kernel: [1041451.812516] init: ebox.loggerd main process (20068) terminated with status 9
    Oct 20 09:57:05 zentyal2 kernel: [1041451.812633] init: ebox.loggerd main process ended, respawning
    ....
    ....
    ....


I do not see too how to fix this problem at first? An idea here?