ClamWin Free Antivirus :: View topic - Multiple clamscan.exe killing CPU on a scheduled scan

Posted: Fri Jan 02, 2009 8:58 pm

We are also having the same problem even after we have followed the previous advice of deleting the %temp%ClamWin_Scheduler_Info

Our clients are all in the EST

Posted: Sat Jan 03, 2009 1:43 am

The problem should be gone after January 7th, there is a bug in calculating a next scheduled run for weekly scans when a year_day is less than a week_day.
Could all who still have a problem do a quick test and temporarily set the computer clock after January 7th, then restart clamtray.exe and see if the problem is gone?

Posted: Sat Jan 03, 2009 3:31 am

alch wrote:

The problem should be gone after January 7th, there is a bug in calculating a next scheduled run for weekly scans when a year_day is less than a week_day.
Could all who still have a problem do a quick test and temporarily set the computer clock after January 7th, then restart clamtray.exe and see if the problem is gone?

I set my calendar to the 8th and the problem seems to have gone away. I will hold off on setting up scheduled scans until the 8th. Thanks for your help!

nprenger

Posted: Tue Jan 06, 2009 8:54 am

I have checked all my machines and they are all OK now.

Posted: Tue Dec 29, 2009 1:05 pm

I am experiencing this issue now, with v0.95.3. I found this forum thread and can see that it appears to match what is occuring on my servers. I have a weekly schedule configured and am seeing the date-format error message described.

Please can I re-alert you to this issue, as it was raised by others over a year ago and the given responses of "delete this temp file" or "disable your schedules for a couple of weeks" and "it'll be OK for the next year" don't really cut it when next year comes around and everyone has forgotten...

Below is the ClamWin1.log file from two of my many affected servers:

Code:

schedTime: (2009, 12, 29, 12, 54, 41, 1, 363, -1)
Scheduling task (131096, 273, 1024, 1) for: Tue Dec 29 12:54:41 2009
Scheduling task (131096, 273, 1024, 1) for: Tue Dec 29 21:00:00 2009
couldn't parse time, self._startTime = 00:00:00. self._weekDay = 6
Error: time data did not match format: data=368 2009 00:00:00 fmt=%j %Y %H:%M:%S
Scheduling task (<__main__>, 'C:\\', 'Scheduled scan of C:\\', 1) for: Tue Dec 29 12:54:41 2009
An error occured whilst reading last scheduled run from ClamWin_CheckVer_Time. Error: [Errno 2] No such file or directory: 'c:\\users\\admini~1\\appdata\\local\\temp\\1\\ClamWin_CheckVer_Time'
using random checkversion time 13:44:07
Scheduling task (131096, 1047, 0, 2) for: Tue Dec 29 13:44:07 2009

and one from a process I killed:

Code:

System Locale: ('en_GB', 'cp1252')
Default Encoding: cp1252
command line path:
<NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL><NUL>
Scanning: "C:\\"
clamscan.exe command line: "C:\Program Files (x86)\ClamWin\bin\clamscan.exe" --tempdir "c:\users\cncadm1n\appdata\local\temp\1" --keep-mbox --stdout --database="C:\ProgramData\.clamwin\db" --log="c:\users\cncadm1n\appdata\local\temp\1\tmpcucnzi" --no-mail --infected --max-files=50000 --max-scansize=4096M --max-recursion=999 --max-filesize=4096M --recursive --exclude="[^\]*\.mdf$" --exclude="[^\]*\.ldf$" --exclude="[^\]*\.ndf$" --kill "C:\\"
"C:\Program Files (x86)\ClamWin\bin\clamscan.exe" --tempdir "c:\users\cncadm1n\appdata\local\temp\1" --keep-mbox --stdout --database="C:\ProgramData\.clamwin\db" --log="c:\users\cncadm1n\appdata\local\temp\1\tmpcucnzi" --no-mail --infected --max-files=50000 --max-scansize=4096M --max-recursion=999 --max-filesize=4096M --recursive --exclude="[^\]*\.mdf$" --exclude="[^\]*\.ldf$" --exclude="[^\]*\.ndf$" --kill "C:\\" --memory
couldn't parse time, self._startTime = 00:00:00. self._weekDay = 6
Error: time data did not match format: data=368 2009 00:00:00 fmt=%j %Y %H:%M:%S
Scheduling task (<__main__>, 'C:\\', 'Scheduled scan of C:\\', 1) for: Tue Dec 29 12:25:34 2009
running task <function>(<__main__>, 'C:\\', 'Scheduled scan of C:\\', 1) on: 29-12-09 12:25:34. Frequency is: Weekly

Scanning: "C:\\"
clamscan.exe command line: "C:\Program Files (x86)\ClamWin\bin\clamscan.exe" --tempdir "c:\users\cncadm1n\appdata\local\temp\1" --keep-mbox --stdout --database="C:\ProgramData\.clamwin\db" --log="c:\users\cncadm1n\appdata\local\temp\1\tmpw-a1iy" --no-mail --infected --max-files=50000 --max-scansize=4096M --max-recursion=999 --max-filesize=4096M --recursive --exclude="[^\]*\.mdf$" --exclude="[^\]*\.ldf$" --exclude="[^\]*\.ndf$" --kill "C:\\"
"C:\Program Files (x86)\ClamWin\bin\clamscan.exe" --tempdir "c:\users\cncadm1n\appdata\local\temp\1" --keep-mbox --stdout --database="C:\ProgramData\.clamwin\db" --log="c:\users\cncadm1n\appdata\local\temp\1\tmpw-a1iy" --no-mail --infected --max-files=50000 --max-scansize=4096M --max-recursion=999 --max-filesize=4096M --recursive --exclude="[^\]*\.mdf$" --exclude="[^\]*\.ldf$" --exclude="[^\]*\.ndf$" --kill "C:\\" --memory
couldn't parse time, self._startTime = 00:00:00. self._weekDay = 6
Error: time data did not match format: data=368 2009 00:00:00 fmt=%j %Y %H:%M:%S
Scheduling task (<__main__>, 'C:\\', 'Scheduled scan of C:\\', 1) for: Tue Dec 29 12:27:34 2009
Exit Code: 1
Email alert to me@example.org has been sent successfully.
Cleanup for process 0000041c
removing temp dir clamav-ac8e63692acc05fa2b74f314c74193c6.0000041c.clamtmp
removing temp file clamav-1d646753bbb44ec502bada424b7bf1ed.0000041c.clamtmp
removing temp file clamav-7c0a869412d39ada769e6d5685256837.0000041c.clamtmp

Posted: Wed Dec 30, 2009 4:08 pm

We are also having this problem on all 15 of our laptops which I believe started for us on Dec. 28. Any solutions to this problem would be appreciated.

Posted: Wed Dec 30, 2009 5:43 pm

Had as many as 15 until I figured out that these were the forcefully stopped scans fro earlier.

Posted: Thu Dec 31, 2009 4:22 pm

Same thing here. I have a daily and a weekly scan scheduled in clamwin. I had 40+ clamscan instances running...

Posted: Fri Jan 01, 2010 1:49 pm

alch wrote:

The problem should be gone after January 7th, there is a bug in calculating a next scheduled run for weekly scans when a year_day is less than a week_day.
Could all who still have a problem do a quick test and temporarily set the computer clock after January 7th, then restart clamtray.exe and see if the problem is gone?

That fixed it here on several machines.
Thanks.

Posted: Sat Jan 02, 2010 6:04 pm

Yep I too am having this problem. Clamscan starts out by launching *I think* 2 instances of clamscan when the balloon appears in WinXP (with latest updates from Microsoft - it updates automagicaly). I upgraded to Clamwin-0.95.3.setup.exe in hopes to solve this and ... sadly Sad

no it did not work.

Each clam scan launched throttles my processor and eats into memory (3GB) as new clamscans are launched until my HDD begins thrashing around and windows asks to increase the HDD cache size which of course won't help. This is then where ClamWin stops acting like virus projection software and becomes part of the problem (bringing a computer to it's knees).

I have disabled clamscan and cannot use this software until this is corrected. If there is a problem with time date, where references are made above that date times in the future (next year) could also cause issue then I ask for a feature request (facetious)

1) A little calendar in ClamWin with blackout days
or
2) auto uninstaller and popup to install some other open source virus software.

Please fix this and let me know when I can start running my scans with a new version, one that will not have the same problem next year... or the year after... or the year after that. You get the idea.

Posted: Sun Jan 03, 2010 6:55 am

One year later I am having the same problem, even with 0.95.1 and 0.95.3 (last year I used 0.94). I currently have ClamWin disabled on two computers.

alch wrote:

I suspect this error in the scheduler code has been introduced by the fix of Daylight Savings bug. The issue should disappear after January 1st. Please report if it is still happening.

I sincerely apologise for all the trouble and I will fix the bug so it doesn't bother you again at the end of 2009.

Regards,
Alch

Alch, did you ever fix the code to deal with the New Year's problem that appeared after the DST problem was fixed? If so, was the fix released in 0.95.1, 0.95.2, or 0.95.3? I can't seem to find the full change logs for those three versions.

Posted: Sun Jan 03, 2010 11:54 pm

voidxor wrote:

One year later I am having the same problem, even with 0.95.1 and 0.95.3 (last year I used 0.94). I currently have ClamWin disabled on two computers.

alch wrote:

I suspect this error in the scheduler code has been introduced by the fix of Daylight Savings bug. The issue should disappear after January 1st. Please report if it is still happening.

I sincerely apologise for all the trouble and I will fix the bug so it doesn't bother you again at the end of 2009.

Regards,
Alch

Alch, did you ever fix the code to deal with the New Year's problem that appeared after the DST problem was fixed? If so, was the fix released in 0.95.1, 0.95.2, or 0.95.3? I can't seem to find the full change logs for those three versions.

The fix went into 0.95.2:
https://clamwin.svn.sourceforge.net/viewvc/clamwin/trunk/clamwin/py/Scheduler.py?r1=2553&r2=2732

I'll debug and find out what went wrong

Posted: Mon Jan 04, 2010 12:19 am

voidxor wrote:

One year later I am having the same problem, even with 0.95.1 and 0.95.3 (last year I used 0.94). I currently have ClamWin disabled on two computers.

alch wrote:

I suspect this error in the scheduler code has been introduced by the fix of Daylight Savings bug. The issue should disappear after January 1st. Please report if it is still happening.

I sincerely apologise for all the trouble and I will fix the bug so it doesn't bother you again at the end of 2009.

Regards,
Alch

Alch, did you ever fix the code to deal with the New Year's problem that appeared after the DST problem was fixed? If so, was the fix released in 0.95.1, 0.95.2, or 0.95.3? I can't seem to find the full change logs for those three versions.

The fix went into 0.95.2:
https://clamwin.svn.sourceforge.net/viewvc/clamwin/trunk/clamwin/py/Scheduler.py?r1=2553&r2=2732

I'll debug and find out what went wrong

Posted: Mon Jan 04, 2010 1:30 am

Hi I Have ClamWin on 2x win2k3R2 Servers and 1 of the 2 is having this issue for some reason the 2nd server seems fine but I've had to disable ClamWin on the other at this point.

please advise if I can provide you with any logs to aid your research into this issue.

Thank you much indeed.

and for (current issue not withstanding Very Happy

) y'alls work on clamwin.

Posted: Mon Jan 04, 2010 4:09 am

atarione wrote:

Hi I Have ClamWin on 2x win2k3R2 Servers and 1 of the 2 is having this issue for some reason the 2nd server seems fine but I've had to disable ClamWin on the other at this point.

please advise if I can provide you with any logs to aid your research into this issue.

Thank you much indeed.

and for (current issue not withstanding Very Happy

) y'alls work on clamwin.

I think I found the problem, please try to replace your %programfiles%\clamwin\lib\clamwin.zip with this one:
https://files.clamwin.com/y2010/clamwin.zip
and let us know how it went and paste %tmp%\clamwin1.log file (don't open clamwin prior to reading the log file as it will overwrite the old info)