Internet outage –
A problem with the Ntelos network caused the problem. At 7:20 they had no estimate of when the outage would be resolved.
FS Server problems
Utilization was 86%, and the server show typical signs of being hung. Rebooted and did not load Sophos Sweep, but did load NovaNet.
Fileserver ST crashed
Debug screen with “multiple abends on processor 0” message at top. Re-enabled logical processors from BIOS setup and restarted. Server hit 46% utilization and became unresponsive within 10 min. Swapped ACPIDRV for MPS14 in STARTUP.NCF. Server is now back to original config, and processors 1-3 are offline.
ST server hung at 46% cpu
Novell server ST hung at 46% CPU. When the second processor was stopped, CPU was 93%. No idea why this happened. All else seemed to be normal. Sweep and novastor was running. Server had to be powered off to get it operational again.
ST server to be worked on
ST server needs to be taken down to disable hyperthreading.
_______________
Logical processors were disabled in the bios. Startup.ncf was modified to remove acpidrv.psm and replaced that with mps14.psm. This should allow multiprocessor function and not allow hyperthreading of logical processors.
Dan
Calendar: server unavailable
The calendar server was unresponsive via the network or the console. A “spurious interrupt” message appeared on the console. After a reboot, everything appears fine.
FSAPPS server to be rebooted
FSAPPS server needs to be rebooted to install new drivers for the NIC.
FS server to be rebooted
FS server needs to be rebooted to install new drivers for the NIC.
Web server slow performance
Any connections to the web server or www.emu.edu would have possibly had slow response times or be disconnected during this time. We have solved the immediate problem and are continuing to monitor the system. [ref #14398]
Web server unresponsive
update 3pm——–
Found a recursive link situation that caused our internal search spider to crash the system. Backups was not the main problem after all.
——————
Any web pages, web databases, and FTP connections would have experienced problems throughout this time.
As of 5AM there was some performance problems because of a unexpected timing of a backup process. In trying to correct other failed processes caused by this, the system went down because of running out of memory.