Author Topic: [SOLVED]almost 100% CPU usage? Is this normal  (Read 5042 times)

virtualstefan13

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
[SOLVED]almost 100% CPU usage? Is this normal
« on: December 08, 2010, 04:07:12 pm »
Hi everyone,

Is it normal for Zentyal to have almost 100% cpu usage?  (See attached file). I've got 1 machine connected to it (So far)




I've got a sempron LE 1200 with 4 gig of RAM.  

This server is purely for internet gateway(with a little bit of traffic shaping), so I've installed the following modules.  Here are the list:

network
firewall
antivirus
Events
monitor
traffic shaping
user and groups
http proxy.

Thank you.
« Last Edit: December 08, 2010, 06:38:40 pm by virtualstefan13 »

Josep

  • Zen Samurai
  • ****
  • Posts: 255
  • Karma: +6/-0
    • View Profile
Re: almost 100% CPU usage? Is this normal
« Reply #1 on: December 08, 2010, 04:49:40 pm »
I'm sure you already know the answer: no it's not normal.
Immediate suggestion: from the shell prompt type "sudo service ebox restart"
Next step:try to figure out what might have caused the issue (is it the first time? is there any clue in the logs? did you apply some change prior to this event?)

bamalam

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: almost 100% CPU usage? Is this normal
« Reply #2 on: December 08, 2010, 05:13:21 pm »
From the top output you can see the process ID of the problem process. We can see that it is some perl command that is run under the ebox user.

I suggest you use:
   ps wwaux | grep ebox
at the command prompt to find the full command line of the process that is causing you problems. This may give further clues.

Regards,

bamalam

virtualstefan13

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: almost 100% CPU usage? Is this normal
« Reply #3 on: December 08, 2010, 05:21:29 pm »
It's my first time implementing zentyal.  And eventually thought that it was not normal (and I needed confirmation).

Thank you for the advices.  I'll try to follow it.

I'll be back to let you know of the result.

Thank you.

virtualstefan13

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: almost 100% CPU usage? Is this normal
« Reply #4 on: December 08, 2010, 05:28:09 pm »
Tried to use ps wwaux | grep ebox and here is the result.

I'm an amatuer user and its kinda hard pointing the fault in here.  Can you guide me? 


Josep

  • Zen Samurai
  • ****
  • Posts: 255
  • Karma: +6/-0
    • View Profile
Re: almost 100% CPU usage? Is this normal
« Reply #5 on: December 08, 2010, 05:53:18 pm »
It's kind of hard to view the screenshot ... still, it looks like EventDaemon.pm is the culprit.
Wild guess here: have you created some event notification? If you had created an event that is triggered for very small values (say: notify me whenever the CPU is above 0%) it would keep try notifying you constantly, and this would lead to such a high CPU usage.

Try stopping the events daemon with: sudo service ebox events stop

virtualstefan13

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: almost 100% CPU usage? Is this normal
« Reply #6 on: December 08, 2010, 06:19:43 pm »
Yep,  You were right.  event daemon was causing my 100% cpu utilization problem.  Disabled it and rebooted the system and its normal now. Now I've got 1-0% of cpu usage...

and now I've got another problem where the content filtering is not working.  I guess it has something to do with the ones that I disabled.

oh well.  I think the problem has been resolved.  thanks to your wwaux | grep ebox command.  ;D

bamalam

  • Zen Apprentice
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: [SOLVED]almost 100% CPU usage? Is this normal
« Reply #7 on: December 08, 2010, 10:05:47 pm »
Nice to know that it is not 100% usage now. Well done for marking it as SOLVED  :) . I guess you could try the content filtering problem as a separate topic.

christian

  • Guest
Re: [SOLVED]almost 100% CPU usage? Is this normal
« Reply #8 on: December 09, 2010, 11:46:07 am »
Well, it's solved... for the time being  ;)  I mean that event daemon is not supposed to consume that much.
I know it doesn't help but be informed that I'm facing same issue since a while and decided to disable this module too but I did not spend time investigating on the root cause  :-[ this is not yet my priority.