[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RaQ3 stopped responding
- Subject: Re: [cobalt-users] RaQ3 stopped responding
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Wed Jun 12 10:17:00 2002
- Organization: nobaloney.net
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Albert Csaba wrote:
> Thank you for your answer.
> As it turned out, after the 4th reboot they emailed me
> that a fan is not working correctly and they are
> replacing it. Since then it works fine.
That may or may not have been the entire problem; our systems, which run
in extremely cold data rooms, can run with only one fan; we had one
system run with no fans for a while, until on-order fans arrived. But
as I said, our data rooms run pretty cold.
> Unfortunately, I can't install chkrootkit because of
> this error (which I get when trying to "make" most of
> the programs):
>
> [root@ns chkrootkit-0.35]# make sense
> gcc -DHAVE_LASTLOG_H -o chklastlog chklastlog.c
> In file included from /usr/include/signal.h:300,
> from chklastlog.c:41:
> /usr/include/bits/sigcontext.h:28: asm/sigcontext.h:
> No such file or directory
> make: *** [chklastlog] Error 1
Hmmm... I've never seen this happen on any other RaQ3. Are you
up-to-date with your updates? Does anyone know if there's a hack out
that disables the ability to install chkrootkit?
> I'm checking for a system attack the commands from
> knowledgebase, which didn't pointed out any attack.
>
> And for cat /proc/meminfo I'm getting this, which I
> guess is normal:
>
> total: used: free: shared: buffers:
> cached:
> Mem: 31444992 26763264 4681728 34324480 1187840
> 12599296
> Swap: 134692864 23658496 111034368
> MemTotal: 30708 kB
> MemFree: 4572 kB
> MemShared: 33520 kB
> Buffers: 1160 kB
> Cached: 12304 kB
> SwapTotal: 131536 kB
> SwapFree: 108432 kB
I'm presuming your RaQ3 has only 32 megabytes of memory. Let's just
nicely say that's not enough.
And only four megabytes of free memory; that's not enough either. We
reboot our systems when MemFree gets that low, unless it goes back up
again within a few minutes.
I know that rebooting shouldn't be necessary, it's a good way to get
memory back up.
Check this again immediately after a reboot, and see what the MemFree
line says.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net, P. O. Box 52672, Riverside, CA 92517
voice: +1 909 778-9980 * fax: +1 909 548-9484