Page 1 of 1

WingFTP Server Service eating up processor

Posted: Wed Feb 09, 2011 5:08 pm
by mferanda
I have a sporadic yet reoccurring issue with the Wing FTP Server service. The service seems to eat more and more processor as time goes by – sometimes once a month, sometimes twice a month, other times it wont happen for several months. It’s a strange 25% usage increment than slowly increasing percent by percent. The first time this happened, the service actually completely locked up my server as I notice the service starts with a high priority.
The only connection used is SFTP and we have an extremely minimal amount of connections. For the most part, I’m the only person who really utilizes the entire FTP service with other accounts used extremely infrequently.
Any ideas would be appreciated as I’m tired of babysitting this service.

This has actually gone on since I've owned the product and has crossed many upgrades at this point. It happened on a Windows 2003 box and now Windows 2008.

Thanks

WingFTP v3.7.5

Re: WingFTP Server Service eating up processor

Posted: Thu Feb 10, 2011 5:04 am
by FTP
When the cpu usage goes up, will it fall down after a while?

Re: WingFTP Server Service eating up processor

Posted: Thu Feb 10, 2011 5:55 am
by mferanda
No, and doesnt slowly move up.

I've never watched it actually increase, but the process usage is always a solid number like 25%, then the normal process usage on top of that. For example, if normal usage is around 0-5%, then the service will now take up 25-30%. After enough time goes by, the base will pop up from 25% to 50% then 75% and eventually kill the server at 100%.

The only fix at the moment is to restart the service before it eats up the server.

Re: WingFTP Server Service eating up processor

Posted: Thu Feb 10, 2011 9:04 am
by FTP
OK, I see. You had better compress the entire folder "/Log" into a zip file, then send it to us via email. Thanks!

Re: WingFTP Server Service eating up processor

Posted: Mon Mar 07, 2011 9:52 am
by FTP
The latest version 3.8.0 already fixed this issue, please upgrade to it.