UPDATE
[2008-08-27 11:08:00 | mark kraitchman]
It appears that cronus is having a hard drive problem…
UPDATE
[2008-08-28 11:39:36 | mark kraitchman]
There continues to be some problems with
DNS, NIS and time services from cronus & rhea at times.
Investigation continues.
UPDATE
[2008-08-29 16:37:42 | Mark Kraitchman]
The sporadic problems with DNS, NIS and time services from cronus and rhea may have ended.
The system adminstrators of the system that appeared to be making the most DNS requests from cronus has been configured in a more robust and friendly way so that it is no longer making DNS requests from cronus.
The sporadic problems with DNS and NIS service may have caused:
* Slow logins to systems in the departmental NIS domain
* Web applications to run slowly on web servers in EECS
* Slow connections to remote web servers
* Slow directory changes on systems in the departmental NIS domain
* Slow long directory listings
cronus has been upgraded to running some newer (named) software instead of the older version of software supplied by the vendor.
We will continue to monitor the status of cronus and rhea, please continue to report any observed problems to help@eecs.
(*We apologize for the delay in publishing this update, our publishing software was having some problems. — Ed.*)
UPDATE
[2008-09-02 08:25:25 | Lars Rohrbach]
cronus has become unresponsive again, perhaps since about 1:00 a.m. this morning.
UPDATE
[2008-09-03 14:01:39 | Mark Kraitchman]
cronus.eecs was rebuilt, and normal network services resumed as of about 4:04 pm.
Resolved as of 2008-09-02 16:04:00