by AltTeo » Mar 01 06 11:03 pm
I have the same problem. As I tried to work around this problem, I found some key moments.
Wingate service used about 1.5 Gb of memory after saveral days of running and internet connection becomes accidental (not every time).
I took a similar system and tried to recreate the situation. The problem was found in ... Sheduler! I'm using a ProxyInspector and it creates some actions in Wingate sheduler. The main of it is purging history.
So it is all about history file HISTORY.DBF. If it is greater than 3-4 MB than Wingate becomes unstable.
To solve the problem you should use Wingate sheduler for periodicaly purging history. But my problem is that sheduler DO NOT start events sometimes (maybe it does not accept names of events other than in english, maybe it does not start an event if it's sheduled at 00.00). To solve the problem I made a windows sheduler event that stops wingate, deletes history.dbf and history.cdx (in wingate directory), and starts wingate... It seems to work, but I want Wingate to work correct.
So continue investigating....