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.
Category Archives: File Server
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
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.
Electronic Library Catalog Failure
The library electronic catalog system (Sadie) is not functioning. It appears that a catastrophic hardware failure may have occurred about 7:30pm, Fri, 10/29. Information Systems techs are aware of the problem but have limited resources available to diagnose and fix the problem during weekend hours. It is likely that the server will remain off-line until sometime on Monday, 11/1. This outage log will be updated as new information becomes available.
————————————-
Sirsi back on line by 11:15pm, 10/29. Work-around found for the server startup problem. Further testing needed, but for now the system is running.
UPS hardware, UPS software or UPS control cable may be cause of problem. Server is currently running WITHOUT UPS control cable connected.
FS outage
FS Novell file server needed to be rebooted.
CPU was at 1%, disk requests were very high. Initially there was console access, then that hung as well. Disk lights showed no activity even though disk requests were high. Sweep was not loaded.
Had to power off the server and restart it. All seemed well after that.
Novastor was reloaded, sweep was not.
OCS server outage
For unknown reasons the OCS server stopped responding to copier authentication requests. The problem has been resolved.
FS server unavailable
Server FS was unresponsive, and utilization was high for one processor. Timesync was lost, and NovaNet couldn’t contact the database server. Busiest threads were “NN Sup 2”, “DB Monitor” and “Server 23”. The last file scanned by Sweep was at 3:03 a.m. The server appeared to be fine after rebooting. Sweep was not reloaded.
FSAPPS server crash
The server showed high utilization (server thread) and was sluggish/unresponsive from clients. It would not shut down cleanly, so a reboot was forced. The last file scanned by Sophos was at 11:07, which seems like a large time gap. Server is operational following the reboot.
FS server crash/hung
Novell server FS hung again.
CPU at 24%, Appears to be Sophos again.
This time it was run as “sweep -bindery”. The info on the sweep screen was as follows:
file: userdata….
time: 22:05 on 20 sept 04
user: server process
address: local server
normally it had:
user: unknown
Address:
Powered off server, brought it back up.
DJ