5.2.3 locking up

[llupin]

I installed 5.2.3 on Feb 24. All seemed fine for the first week or so. As of late last week Wingate has been locking up on a daily basis. the W2K server event logs don't show anything other than this one entry:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 3/9/2004
Time: 5:32:08 PM
User: N/A
Computer: PROXY
Description:
The Qbik WinGate Engine service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.

Typically users report then inablity to load a page. When I try to log on to Gatekeeper it rejects the logon. If I try to stop Wingate it just hangs. I have to restart the machine to get it running again.

[neil]

This could very well be corruption of the history files. To rectify this, try stopping the engine (generally easiest straight after a reboot), deleting History.cdx and History.dbf from the WinGate directory, and then re-starting the engine. You may also need to purge your cache.

Regards

Neil

[llupin]

Thanks for the suggestion. It has been working since I posted this. I don't use the cache but went ahead and deleted the history at your suggestion. I'll see how it goes from here.

thanks :)

[llupin]

It locked up this morning. No events were logged. It just stops responding. It will hang if I try to stop the engine and I can't log on to gatekeeper.

I did delete the history files yesterday.

[Pascal]

That sounds like a deadlock. Would it be possible for you to enable deadlock detection ? This is a registry setting that will help us track down exactly where the problem occurs. If you can, the registry keys are:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Settings
Values: UseDeadlockDetection
CheckLockPrecendence

Both of these are REG_DWORD types and should have the value of 1.

Note - all applicable warnings about editing the registry, etc. apply. Make sure you have an appropriate backup / system restore point before doing so. The debug output are in two files called LockAnalyserDumpFileEng.txt and LockAnalyserDumpFileGK.txt. We are more specifically interested in the LockAnalyserDumpFileEng.txt.

[llupin]

I may be fooling myself but it seems to behave itself as long as I leave the admin logged on to gatekeeper on the server. I have left it logged on so I could see if there was anything unusual about its state when the lock up occurred.

I have added the two keys and will leave it running without being logged on. I see that it created a Lock AnalyserDumpFileEng.txt but not the other one yet. I'll send the file when it locks up again.

thanks

[Pascal]

Thank you. One thing to note though - leaving GateKeeper logged in does increase the amount of work that WinGate does (Because it indicates all activity to GateKeeper)

[saubrey]

For the very first time, for me, 5.2.2 shut down expectectedly with the same error in the Windows' event log. My server stayed running and I was able to restart Wingate without having to re-boot.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 3/18/2004
Time: 20:16:08 PM
User: N/A
Computer: server2
Description:
The Qbik WinGate Engine service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.