Remote Administrator Service

G'day All,
I just noticed an odd problem on one server running the Remote Administrator service.
The server is a Win2K DC, with 750MB Memory, 1.5 GB Page file, and the nod32ra service has been using about 1.3GB of VM! This isn't the first time either. Of course the quick fix is restart the service and it drops back down to about 10Mb, and I could set a schedule to do this every few hours or so. But that's not a solution, it's a bandaid......
Anyone else having this problem? it's only for 97 Clients.
I thought, as per a prevoius thread it may have been the logfiles but they are only set for 30 days, and only the infected files, not "list all files".....

Regards, Ben.

 

Hi beng:

Is this version 1.05 of the RA Server?

 

Ben - No problem here - The RAService on my master server is only running at 25MB or so after being up for around 47 days since the last reboot.

Hardware: Dual Xeon w/ NT4, 2GB RAM, RAID 5 (Overkill hardware due to SQL, not NOD)
Software: SQL7 & large database, NOD32, RA v1.0.4, Metering software, a few other things.

Running a pretty much basic default installation of NOD and RA Server.

 

5.9MB for nod32ra.exe on our system.

RA 1.05, 20 clients

Win2003, 512MB RAM, 1GHz PIII, Domain Controller

Uptime 12 days

 

Hmm well, the version is 1.05 so that's not it. still increasing though 42MB System Mem and 197MB VM after 12hrs. Anyone using it on Win2K SP4?
It seems to be working flawlessly other than that....
Checked for anything weird in the logs, and did dscover some odd things,
Firstly since yesterday nothing strange, normal startup type messages, but previously once every 10 seconds or so:
[2004-11-18 07:58:33.994] V1 [41968c160002] <SERVERMGR_ERROR> ServerThread: could not create thread for a new connection (port 2222)
This goes on for days... approx 4 days after the last restart so lets see what happens on the 16th?

Update:
Plot thickens, did a nbtstat on the Win2K server and found multiple (about 50) connections to port 2222 from a single remote workstation.
Will get to that workstation tomorrow (Win98 client in a branch office) and see what the story is!
But that would explain the mem usage pattern, and the log errors, once the connection limit was reached, bang!

Cheers Ben