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

Looks like the problem is gone now. Can anyone else confirm?

I saw that problem both yesterday and today (1/1/2009) on my Win XP Pro system.

Once I rebooted, and the processes restarted 'automatically'.
Then I deactivated all scheduled scans, and rebooted again.
Once I manually started ClamTray the issue returned.

I left my machine with clamscans running last night, the same processes were running
this morning (10PM to 9AM or so), only two drives.

Killed all processes by and again.started clamtray, but haven't had the stamina to re-start
scanning my drives.

I too am having this problem. On most of our computers, I have scheduled scans for Mondays and Thursdays (so each machine scans twice a week). They are both setup as weekly scans, obviously. We were closed last Thursday for Christmas; the problem started on Monday with "Out of virtual memory" messageboxes and 10 or more clamscan.exe instances. We were closed again today for New Year's; I'll see if the problem returns in the next week.

As far as narrowing down the problem, I've set Windows to show dates as the ISO-standard 2008-12-31, not the non-sortable 12/31/2008 format. Does anybody else with this problem use the default 12/31/2008 format, or are all of us in this thread having the problem because we use a non-default date format?

Also, how can I stop ClamWin from running missed scans? I didn't realize that ClamWin did this, but it explains a lot of our computer problems. For instance, it explains why computers that were manually shut down are painfully slow during business hours the following day. There should really be a "Run missed scans later" checkbox under preferences...

The error solved in oct. is back.
What keeps you from adding an option to disable running missed scans!?

I'm running scan jobs from windows sceduler now, to prevent any of these missed job behaviors.

By design missed scans were not supposed to be run. But where is code there are bugs...
Please delete %temp%\ClamWin_Scheduler_Info file and restart clamtray. It should fix it until the end of 2009 and the problem should disappear.
It will be fixed in the next release.

I can confirm that the repeat running is no longer happening since 1st January.

I can also confirm that the fault has cleared.

I have re-set the Scheduled Scans back up to monthly and it is running a dream again, no more 100% CPU useage.

Thanks to all involved.

just cheked this on my XP-machine and the problem did NOT dissapear (today is Jan 2nd.)
Gregor

on my XP SP III it runs nice

but

on my WIN 2K Server reinstalled old CLAMWIN 0.93 and 0.93.1 ...

All works fine until i'm making 'Configure Scheduler'.

After that needs about 5 minutes then the first schedule starts (should start on monday 5th but today is 2nd of January).

After a while the next schedule starts and so on until no more other traffic on the server.

Total breakdown after 25-30 minutes.

regards

wuetschi/2

I'm running Windows Vista Home Premium and I still have the problem on January 2. I updated to 0.94.1, removed %temp%\ClamWin_Scheduler_Info, rebooted, and it still does it. The only way to make the problem go away completely is to remove both of my scheduled scans. Disabling them does not fix it. Is there something else I can try?

Thanks,

nprenger

please paste %temp%\clamwin1.log after the problem appears (do not open clamwin or clamwin configuration as it will overwrite the log)

please paste %temp%\clamwin1.log after the problem appears (do not open clamwin or clamwin configuration as it will overwrite the log)[/quote]

Here it is...

System Locale: ('en_US', 'cp1252')
Default Encoding: cp1252
command line path:
(blank lines eliminated)
Scheduler <built>((66198, 273, 1024, 11)), frequency :Daily terminated
Scheduler <built>((66198, 1047, 0, 12)), frequency :Daily terminated
Scheduling task (66198, 273, 1024, 13) for: Sat Jan 03 02:00:00 2009
couldn't parse time, self._startTime = 02:30:00. self._weekDay = 0
Error: time data did not match format: data=-2 2009 02:30:00 fmt=%j %Y %H:%M:%S
Scheduling task (<__main__>, 'C:\\', 'Weekly C:\\ Drive Scan', 1) for: Fri Jan 02 10:15:12 2009
Scheduling task (66198, 1047, 0, 14) for: Sat Jan 03 00:12:21 2009
running task <function>(<__main__>, 'C:\\', 'Weekly C:\\ Drive Scan', 1) on: 02-01-09 10:15:12. Frequency is: Weekly

Scanning: "C:\\"
clamscan.exe command line: "C:\Program Files\ClamWin\bin\clamscan.exe" --tempdir "c:\users\user\appdata\local\temp" --keep-mbox --stdout --database="C:\ProgramData\.clamwin\db" --log="c:\users\user\appdata\local\temp\tmpp2zzrn" --no-mail --infected --max-files=500 --max-scansize=150M --max-recursion=5 --max-filesize=100M --remove --recursive --exclude="[^\]*\.dbx$" --exclude="[^\]*\.tbb$" --exclude="[^\]*\.pst$" --exclude="[^\]*\.dat$" --exclude="[^\]*\.log$" --exclude="[^\]*\.evt$" --exclude="[^\]*\.nsf$" --exclude="[^\]*\.ntf$" --exclude="[^\]*\.chm$" --kill "C:\\"
"C:\Program Files\ClamWin\bin\clamscan.exe" --tempdir "c:\users\user\appdata\local\temp" --keep-mbox --stdout --database="C:\ProgramData\.clamwin\db" --log="c:\users\user\appdata\local\temp\tmpp2zzrn" --no-mail --infected --max-files=500 --max-scansize=150M --max-recursion=5 --max-filesize=100M --remove --recursive --exclude="[^\]*\.dbx$" --exclude="[^\]*\.tbb$" --exclude="[^\]*\.pst$" --exclude="[^\]*\.dat$" --exclude="[^\]*\.log$" --exclude="[^\]*\.evt$" --exclude="[^\]*\.nsf$" --exclude="[^\]*\.ntf$" --exclude="[^\]*\.chm$" --kill "C:\\" --memory
couldn't parse time, self._startTime = 02:30:00. self._weekDay = 0
Error: time data did not match format: data=-2 2009 02:30:00 fmt=%j %Y %H:%M:%S
Scheduling task (<__main__>, 'C:\\', 'Weekly C:\\ Drive Scan', 1) for: Fri Jan 02 10:17:12 2009

Thanks.
What timezone ate you in?

US Central Time Zone.