[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RAQ Alert Message
- Subject: Re: [cobalt-users] RAQ Alert Message
- From: DBugger <dbugger@xxxxxxxxxxx>
- Date: Thu Feb 10 17:33:35 2000
- Organization: WebMost
Ahoy Dan,
Thursday, February 10, 2000, 11:51:21 AM, you wrote:
D> I got this message from my RAQ2:
D> "The CPU in the Cobalt server is overloaded; it is attempting to do too many
D> things at the same time. An amber light means that there are 3 times as
D> many tasks waiting to be executed as are actually running, and a red light
D> means that there are 6 times as many. Consider moving some of the services
D> to other Cobalt servers, or reduce the complexity of the CGI scripts running
D> on the Cobalt server itself."
D> When I got the message, I logged into the GUI and everything was normal.
D> "Over the past fifteen minutes, the CPU has been lightly loaded [ load
D> average 0.59 ]"
D> "Over the past fifteen minutes, virtual memory has been lightly used [ 2.27
D> swaps/second ] "
D> Running "top" I see:
D> 11:41am up 20 days, 6:24, 1 user, load average: 0.22, 0.08, 0.31
D> 38 processes: 37 sleeping, 1 running, 0 zombie, 0 stopped
D> CPU states: 1.3% user, 1.7% system, 0.0% nice, 97.0% idle
D> Mem: 31064K av, 26996K used, 4068K free, 14164K shrd, 1272K buff
D> Swap: 130748K av, 7164K used, 123584K free 12372K cached
D> Any ideas on where to look to see what was happening, maybe FTP logs, from
D> 11:00 AM when the message was sent by the server?
D> --
I received the exact same message last month, and again this month.
First was at five a.m., when nothing particularly was running, the other
was at 11:30 a.m., when the logs also showed some light activity. Like
you, I also checked the whiz-bang GUI, which showed nothing extraordinary,
and top, which showed all normal. This second time, I asked my VAR to
follow through with Cobalt. They got back a week later with a very
vague reply, which basically reiterated the message from the server.
One sensible thing they did suggest was that (if mail relay is open) the
overload may have occurred as a result of a spammer overloading the
mail. You might look at that.
--
Aloha
Davis