Getting closer to solving lockup

[Mixy!]

Ok, im stil having the random "lockup" problem as described in my previous post. MQSEQ2 added extra error logging to the client (seperate box in this case) and as it turns out, there are no odd errors on the client. (I just get the standard in / out messages right before it dies)

I've noticed a problem on my host box though. Shortly after the client dies, i get a "Delayed write error" in windows XP. It ususally says "Windows could not save the information e:\Everquest\$ms" or something odd like that. Then in the event viewer i get an error log that says "An error was detected on device \Device\Harddisk0\D during a paging operation."

Now i know you're going to say my HDD is screwed up, but im certian it is not. I've run several low level diagnostics on it, and benchmarked with Sandra for 24 hours with no errors. It's a WD 4meg buffer Caviar edition.

I've also terminated any other applications on my host box to try to eliminate any possible interference. Im down to running EQ w/ EQW, myseq server, and MQ.

Im assuming that the reason the delayed write error is happening is because something is getting "hooked" (for lack of a better term) and not being released properly. Like when you try to save a document that is in use.

Is there any way we could add some error logging to the server?

Im using the new years build of MQ. Myseq 1.15.16, the 1.11 server, and eqw beta 2.35A. I dont think it's the eqw, because i've been using that version for a long time with no problems.

-Mixy!

[Blind Aviator]

When MySEQ was first released I was also using EQW... Whenever I ran EQW in conjunction with myseq server I had nothing but problems...

Try running EQ/myseq without EQW and see what happens then... Won't hurt anything and takes little time to test...

BA

[Mixy!]

Ok, i tried that and i dont seem to get the delayed write failed msg. (So far) However myseq still dies on me.

-Mixy!

[MQSEQ2]

I run EQW all the time (that's the only way I can remotely program and test when I'm not at home).

The Server doesn't write anything to disk so any Disk I/O errors would be OS related. Now if you are running low on Harddrive space and/or don't have alot of available memory (generally HD space) it would cause exessive paging to the Harddrive. But with 4 Meg Cache it should be able to handle it.

What Network Card are you using?

Do you have QoS (Quality of Service) loaded (Remove if you do)?

Have you tried 1.15.17 Client (there more logging in there)?

Post/mail me your latest log files.

I don't want to spend to much time tryin to mess with the 1.x Server since I'm trying to move to the 2.0 Client/Server.

[Mixy!]

Ok, as i said earlier, the EQw didnt seem to help my problem at all.

I have dual 40Gig HDD's, one runs EQ the other is the OS. Both have 20+gig free. The client has a 10gig HDD with 1gig free.

My network card on the server is onboard, Realtec RTL8139/810X it's the 10/100 that comes with the Abit IT7 Max2 V2. In the client it's a 10/100 d-link. I have a linksys router.

I dont know what QoS is.. if i had to manualy install it, then i definately dont have it. If it comes with wondows xp, then i cant find it on the system anywhere.

Im going to upgrade today to the 1.15.17 client and take some logs.

My log files are like 30meg, so i wont mail them, but i will post one instance of where it crashed:

01/03/2004 19:58:58:73 - Exiting in CSocketClient.Receive()
01/03/2004 19:58:58:74 - Exiting in CSocketClient.ReceiveComplete()
01/03/2004 19:58:58:95 - Entering in CSocketClient.Send(Byte[])
01/03/2004 19:58:58:95 - Exiting in CSocketClient.Send(Byte[])
01/03/2004 19:58:58:95 - Entering in CSocketClient.SendComplete()
01/03/2004 19:58:58:95 - CSocketClient.SendComplete(): GetNetworkStream.EndWrite()
01/03/2004 19:58:58:95 - Exiting in CSocketClient.SendComplete()
01/03/2004 19:58:58:95 - Entering in CSocketClient.ReceiveComplete()
01/03/2004 19:58:58:95 - Entering in CSocketClient.Dispose()
01/03/2004 19:58:58:95 - Entering in CSocketClient.Disconnect()
01/03/2004 19:58:58:96 - Exiting in CSocketClient.Disconnect()
01/03/2004 19:58:58:96 - Exiting in CSocketClient.Dispose()
01/03/2004 19:58:58:96 - Entering in CSocketClient.Dispose()
01/03/2004 19:58:58:96 - Entering in CSocketClient.Disconnect()
01/03/2004 19:58:58:96 - Exiting in CSocketClient.Disconnect()
01/03/2004 19:58:58:96 - Exiting in CSocketClient.Dispose()
01/03/2004 19:58:58:96 - Exiting in CSocketClient.ReceiveComplete()
01/03/2004 20:00:47:41 - Entering in CSocketClient.CSocketClient()
01/03/2004 20:00:47:41 - Exiting in CSocketClient.CSocketClient()
01/03/2004 20:00:47:41 - Entering in CSocketClient.Connect()
01/03/2004 20:00:47:41 - Entering in CSocketClient.Receive()
01/03/2004 20:00:47:41 - Exiting in CSocketClient.Receive()
01/03/2004 20:00:47:42 - Entering in CSocketClient.Connect()
01/03/2004 20:00:47:69 - Entering in CSocketClient.Send(Byte[])
01/03/2004 20:00:47:69 - Exiting in CSocketClient.Send(Byte[])
01/03/2004 20:00:47:69 - Entering in CSocketClient.SendComplete()
01/03/2004 20:00:47:69 - CSocketClient.SendComplete():


The space between 19:58, and 20:00 is where the client died on me.

This may not be a myseq problem at all, as i do run MQ too. I'll post some error logs with 1.15.17 today if the problem continues.

I dont think it's network lag that causes it, because it dosnt correspond to any ingame lag.

-Mixy!

[MQSEQ2]

QoS is located in the Network property area (where you see the NIC and TCP/IP) . QoS is insalled automatically and to uninstall it you need to hilte the QoS option then click Uninstall. If you ever wanted to add it back just click Install and choose it, no biggie.

Try setting both NICs to 100/half duplex to see if this is a NIC/Router issue. Have you every flashed your LinkSys router?

[Mixy!]

Here is the error log with the last few seconds brfore the client died with 1.15.17.

01/04/2004 15:59:45.68 - Entering ProcessGroundItems()
01/04/2004 15:59:45.68 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.68 - Entering ProcessGroundItems()
01/04/2004 15:59:45.68 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.69 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.69 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.69 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.69 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.69 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.69 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.69 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.69 - Entering ProcessGroundItems()
01/04/2004 15:59:45.70 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.70 - Entering ProcessGroundItems()
01/04/2004 15:59:45.70 - Exiting ProcessGroundItems()
01/04/2004 15:59:45.70 - Entering ProcessSpawnList()
01/04/2004 15:59:45.70 - Exiting ProcessSpawnList()
01/04/2004 15:59:45.81 - Entering in CSocketClient.Receive()
01/04/2004 15:59:45.82 - Entering in CSocketClient.Send(Byte[])
01/04/2004 15:59:45.82 - Exiting in CSocketClient.Send(Byte[])
01/04/2004 15:59:45.82 - Exiting in CSocketClient.Receive()
01/04/2004 15:59:45.82 - Exiting in CSocketClient.ReceiveComplete()
01/04/2004 15:59:45.82 - Entering in CSocketClient.SendComplete()
01/04/2004 15:59:45.82 - CSocketClient.SendComplete(): GetNetworkStream.EndWrite()
01/04/2004 15:59:45.82 - Exiting in CSocketClient.SendComplete()
01/04/2004 15:59:45.83 - Entering in CSocketClient.ReceiveComplete()
01/04/2004 15:59:45.98 - Entering in CSocketClient.Dispose()
01/04/2004 15:59:45.98 - Entering in CSocketClient.Disconnect()
01/04/2004 15:59:45.98 - Exiting in CSocketClient.Disconnect()
01/04/2004 15:59:45.98 - Exiting in CSocketClient.Dispose()
01/04/2004 15:59:45.98 - Entering in CSocketClient.Dispose()
01/04/2004 15:59:45.98 - Entering in CSocketClient.Disconnect()
01/04/2004 15:59:45.98 - Exiting in CSocketClient.Disconnect()
01/04/2004 15:59:45.98 - Exiting in CSocketClient.Dispose()
01/04/2004 15:59:45.98 - Exiting in CSocketClient.ReceiveComplete()

-Mixy!

[Mixy!]

The QoS option was not checked. I'll try to set my NIC's down a bit to see if that helps. That error log make any sense to ya?

-Mixy!

[MQSEQ2]

Totally remove QoS even tho it's not checked it adds overhead.

I'm running out of options until 2.x comes out.

[Mixy!]

Need any help with server 2.0? I downloaded the demo and got it to talk between my two boxes a few months ago. I cant offer much as far as programming is concirned, buy if you need any testing help i can aid in that.

-Mixy!

BTW- I removed the QoS, i'll post an update tonite.

[MQSEQ2]

Once I get some of these Client issues resolved I will start working on the 2.x stuff again. It shouldn't take to long to switch it now that I have the Client pretty much setup.