A problem occurred during the night on one of EMU’s mail servers that prevented delivery of new messages. No messages were lost, however, they were just delayed until the problem was fixed.
You may have received warning messages informing you that your message couldn’t be sent for four hours. If so, you do not need to resend your message. It will be delivered normally.
Novell server FS hung again.
CPU at 24%, just ran dellmgr, executed stormgr and it hung. No similar files in sweep log.
Powered off server, brought it back up.
Novastore was reloaded. Sweep is NOT loaded yet.
DJ
On Friday evening a database problem occurred on the mail server. The server was brought back online but the original database issue had not been entirely resolved and errors were occurring. The server was available intermittently during this outage while a more effective solution was put in place.
We are experiencing another long-distance service outage, we have contacted our carrier (Qwest) and expect to have it resolved this morning.
If you need to call long distance and have an EMU calling card you should use that until the system is resolved.
=================
2:00pm, Mon, 8/23: Our trouble ticket has escalated throughout the day with Qwest, we are now at their highest level. Qwest is working with other companies at this time to resolve the outage. We hope to have this resolved yet today, but we cannot give a definitive time as to when it will be fixed.
=================
5:00pm, Mon, 8/23: Received notification from Qwest that a Verizon representative will be here at 8:00 A.M Tuesday (8/24) to test the local loop with the Central Office here in town. Until then, service will be unavailable.
=================
11:20am, Tue, 8/24: Verizon appears to have fixed the problem. Service seems to be working again. There appears to have been a bad connection on Verizons connection between our termination point and the local central office.
The email database on the mail server has been corrupted. Repairs are ongoing as of 6:07PM.
As of 7 PM, the problem has been discovered and fixed. It seems to be working normally.
Novell server FS hung again.
CPU at 24%, restore job was running, new volume was added 1 hour before, no similar files in sweep log.
Powered off server, brought it back up, then restarted server again for a clean boot.
Novastore was reloaded, restore job restarted. Sweep is NOT loaded yet.
DJ
We are currently experiencing intermittent long distance outages due to circuit problems with our carrier. We hope to have the problem resolved by the morning of 8/20.
Problem was resolved around 8:30 this morning but we kept a trouble ticket open with Qwest until this afternoon in case the problem persisted. No problems were reported, ticket has been closed.
Setting up an extension for php may have caused a segmentation fault for all Apache sessions. Stop and Start required.
FS server was not responding when I got here this AM. Server utilization was stuck at 22%, no ABEND problems, sweep was loaded.
Sweep log stated the last files accessed were: a bunch from userdata:data/infosys/_staff/sachsg/program/labsetup….
The last file was userdata:data/stulife/housing/housing/floorp~1.pdf
The user was stulife_upld.noprive.g.emu
last access location: unknown
time of modification for the file (found after reboot) 8/12 2:22AM
Appears to have used FTP to transfer the file. I checked the file – not corrupted – and saved it elsewhere on userdata just fine.
Powered off server and rebooted – server came up fine. Reloaded novastor and sweep(with options).
DJ