Author Topic: loggerd - HIGH CPU  (Read 2545 times)

roswitina

  • Zen Apprentice
  • *
  • Posts: 48
  • Karma: +1/-0
    • View Profile
loggerd - HIGH CPU
« on: January 28, 2013, 09:45:55 am »
Hello!

I use Zentyal 3.0 as a KVM - Client in PROXMOX 2.2 (www.proxmox.com) with 2 GByte RAM.
Because the cpu load was very high, I have zentyal on Friday restarted in the morning.
after two days, the CPU load is increased again.
I've found with htop that the burden of

/ usr / share / zentyal / loggerd

proceeds.

I have installed all updates.

What can I do?

Rosi

Ps: second picture after reboot.
« Last Edit: January 28, 2013, 10:42:10 am by roswitina »

roswitina

  • Zen Apprentice
  • *
  • Posts: 48
  • Karma: +1/-0
    • View Profile
Re: loggerd - HIGH CPU
« Reply #1 on: January 31, 2013, 08:40:56 am »
I found this --> http://trac.zentyal.org/ticket/5080#comment:14
I will reply afte some testing.

rosi

Sam Graf

  • Guest
Re: loggerd - HIGH CPU
« Reply #2 on: February 02, 2013, 02:47:40 pm »
Some of us who experienced this problem earlier have not seen it since a fix was released. I mention that just so you can keep in mind that what you find during additional testing may not directly relate to earlier bug reports.

roswitina

  • Zen Apprentice
  • *
  • Posts: 48
  • Karma: +1/-0
    • View Profile
Re: loggerd - HIGH CPU
« Reply #3 on: February 05, 2013, 01:53:48 pm »
I can't download the fix from the link.
I changed the configuration as in the following posting:

Until we fix it, you can disable the consolidation process  in /etc/zentyal/logs.conf . To do change the configuration key 'disable_consolidation' to 'yes'

Thats what i do.

Rosi

Sam Graf

  • Guest
Re: loggerd - HIGH CPU
« Reply #4 on: February 05, 2013, 02:04:09 pm »
The fix is now in the regular distribution, to my knowledge, and has been for some time. If your server is up to date, you should already have the fix. There should be no need to disable the consolidation process. In my case I experienced this problem last year, when it was encountered, but have not seen it since and have done no manual configuration.