[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Many many problems
> > I was logged on our Raq3, via telnet. All of a sudden, I saw the
> > following message :
> > "Broadcast message from root Fri Sep 8 17:10:57 2000
> >
> > The system is going down for system halt NOW !!".
> >
> > I was the only one logged on that machine, and I sure didn't shut it
> > down. The machine then rebooted (although it should have halted).
> > I tried to catch something in the logs, and the only thing I could
Similar strange thing happened to our Raq3 on the morning of the 8th - 4am
UK time when is was running the cron.daily -
from the file /var/log/messages:
Sep 8 04:10:23 (none) syslogd 1.3-3: restart.
Sep 8 04:10:24 (none) modprobe: can't locate module block-major-22
Sep 8 04:10:24 (none) modprobe: can't locate module block-major-22
Sep 8 04:10:24 (none) modprobe: can't locate module block-major-33
Sep 8 04:10:24 (none) modprobe: can't locate module block-major-33
Sep 8 04:10:24 (none) modprobe: can't locate module block-major-34
.
.
etc...
Basically the RAQ restarted itself. Is this part of the standard
cron.daily? There are other strange things on our server such as the
hostname resetting itself to "(none)" when the server restarts which
prevents httpd, the admserv httpd and smtp from starting up correctly. We
installed a temporary fix adding lines at the end of the start up scripts to
correct the hostname fault and restart httpd etc but the problem is
essentially still there.
The cron.daily stuff doesn't appear to have run at all since this reboot!!
The other problem we have is with the /var/log/maillog in that it won't
rotate!
Anyone have any suggestions other than the cobalt standard.. "you must've
broken it, use the OS restore CD", which we really want to avoid if possible
as it'd be an all-nighter putting all the sites and users back on :(
Thanks,
James McNeil