Re: [cobalt-users] Re: Logging CPU temp

["Richard Donahue" <sales@xxxxxxxxxxxxx>]

> Subject: Re: [cobalt-users] Re: Logging CPU temp
>
>
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > On Thursday 15 April 2004 05:01 pm, Richard Donahue wrote:
> > > > How can I log my CPU temp? My RaQ4 sometimes crashes at 4:02 AM.
I've
> > > > removed the scripts that I installed to run in cron.daily and
> everything
> > is
> > > > fine. I added a couple (logcheck.sh and chkrootkit.sh) back to
> > cron.daily
> > > > and it crashed again this morning. Someone said I should check my
fans
> > and
> > > > CPU temp because it may be causing the server to restart. I never
get
> > any
> > > > warning messages, and the logs don't show anything useful that I can
> > see.
> > > > The CPU temp is always around 35C when I check it.
> > >
> > > You would only get a message if the fan temp was high when Active
> Monitor
> > runs
> > > (at :00, :15, :30, and :45).
> > >
> > > I'd bet something in your logcheck.sh is making it choke. If it's
> > overtemping
> > > that easily, then a fan or some bad memory may be your culprit.
> > >
> > > To log the temp, you'd have to run a script that parsed the output of
> > >
> > > cat /proc/cpuinfo
> > >
> > > and wrote the temp info to a file or something.
> >
> > The memory has been a concern lately. I thought it may have been due to
> the
> > 16622.pkg, but maybe it's a bad chip.
> >
> > Thanks,
> >
> > Rich
> > EBS
> Also had one a week or two ago do the same thing never overheated but died
> during logrotate
> Believe that was due to hardware. NIC or MB. Swaped drive to another unit
> and it quit.
> David
>

Good idea. Thanks.

Rich
EBS