This is caused by a biobug which is exacerbated by certain types of network issue on the client side. What happens is a player logs out and the server does not detect it properly, and hence it cannot completely shut down.
We know who is causing it this time and I am going to try to have the DMs track him or her down to fix it.
If you know the player whose playername is 'Hooked on Phonics', he needs to fix whatever his router or network problem is. He is causing these server hangs. He has not answered any DM communications in-game.
If he doesn't get this fixed Real Soon we will probably have to take drastic measures.
Im so sorry about this, ive only just realised people are trying to get hold of me. I Pm'd Acaos. I have no idea what could be causing this, as im not at home and dont have access to the router as its my girlfreinds brothers (wireless). If theres anything i can do on my side to sort this im obliged to do so, and am really sorry! If it cant ill just stop playing till i get home.
Game Account - Hooked On Phonics / LGP80
Malix Vupella †RM† - x2 Ploder waiting for Reinc ED 209 †RM† - x2 Malad Pariah Safron †RM† - x2 Malb Monk Scary Mary †RM† - x1 CoT waiting for reinc Little John †RM†- Nessus Staffy Quaide Priestly †RM† - Nessus Turner Ruth Lesley Fine †RM† - Nessus Lash Murbella †RM† - Nessus Sorc Sid the Sadistic Sod †RM† - Malad PM
Today's extended downtime was a combination of database index corruption (no data loss - the index just got corrupted) plus one of the files in our NWN installation got corrupted and had to be replaced. We're not aware of any actual loss (other than, of course, your valuable playing time).
Sorry for the inconvenience.
On the bright side, the extended downtime gave me an opportunity to confer with our sysadmin and I'm putting in a tweak to our server config that might help to reduce lag. I also put in a potential fix for the hang-on-reset problem we've been experiencing. Oh, and I named all the servers 117, because that's more fun. ;D
(The everything-being-called-117 should be fixed after a reset).