Moderator: Qbik Staff
Pascal wrote:When the engine was in a "frozen" state, could you still log-in with GateKeeper and even shut it down ?
Pascal wrote:Was there a specific error message you got from the client ?
Pascal wrote:The main thing I'm trying to determine is if it is a lock-up inside the software (Dead-lock) or if it is a problem with internet connectivity.
pecos wrote:I'm pretty sure it's not an Internet connectivity issue. As I said, sometimes the client machine can connect (using NAT) when the server machine cannot. If I uncheck the http proxy in Opera I can sometimes (but not always) connect that way when Wingate is not responding.
Pascal wrote:This test with Opera, is it on the client or on the server ? 99% of the time you should be able to get out from the server if your browser is not set to proxy.
Hopefully it reaches that state again soon, because if you can grab (a) a screenshot in TaskManager showing the resource utilisation for WinGate (Or just write it down) and (b) a capture of netstat -an to show us how many sockets are in-use, that would be a usefull thing.
pecos wrote:I've never seen Wingate using much more than 5% of the CPU or 5,600K of memory in Task Manager, even when locked up. I'm not sure how to get a capture of netstat, sorry. But I just ran it and see quite a few ports listed as "Listening" and two as "Established."
netstat -an > capture.txt
It'd only be a concern if there were 100s or 1000s of connections listed with CLOSE_WAIT, TIME_WAIT or similar.
pecos wrote:If I uncheck the http proxy in Opera I can sometimes (but not always) connect that way when Wingate is not responding.
Pascal wrote:99% of the time you should be able to get out from the server if your browser is not set to proxy.
Pascal wrote:riaanjvr has the same problem and seems to have found a work-around. You could try that in the interim, while we nail it down in the code.
pecos wrote:Thanks, I hadn't seen that post before. I already had caching disabled, but I applied his other suggestions about the file size and the blank filter. I'll be interested to see if these changes make any difference.
pecos wrote:I'll let you know how it goes.
I'd be happy to run the debug kit. I ran one some time ago with version 4 trying to solve a similar problem.
--Tom
adrien wrote:Have you recently looked for viruses on your network? Things like the MS blaster virus can wreak a bit of havoc if left unchecked.
If you get a file called LockAnalysisDumpFileEng.txt created in the WinGate directory, email it to me directly
One other thing to check. If WinGate is not actually locking up, but instead is ceasing to respond for a while, that normally indicates a DNS issue in the WinGate DNS resolver.
2. Make sure that the DNS servers specified are all known good DNS servers.
pecos wrote:Andrew,
I don't quite understand the point of putting such information in a log either.
Thanks for pointing out the Norton Antivirus part. I must have missed that when I looked before. Since I generally keep logging tuned off I'm not sure how much it'll help me, but I'll give it a try.
Users browsing this forum: No registered users and 9 guests