Hi,

Today I openend my computer and found that the ui was basically unresponsive (Core i5,4Gb RAM,Windows7). After some looking around, turns out there are a lot of clamwin threads running doing a scheduled scan.
Now, that's all well and good but I want to do some work. So, I wanted to stop this. First tried to click the Clamwin tray button to start it up. Nothing. Then RMC start it up. Nothing. After a long while ClamWin started up but it turns out that all the running tasks are unknown to the UI. So you can't do anything about it.
Ok, now I found the stop scheduled tasks function. I select it. Nothing
I select it again, nothing
Ok, now I'm totally pissed off. I start killing Clamwin process threads. Initially it looks good. I can do something in the ui again without infinite delays. Then I suddenly see a tray popup from Clamwin sayng it's running its scheduled scan.

I mean seriously, WTF? How do I stop this puppy from scanning when it's in the way?

Kind regards,

Marc

Ok, finally decided to accept that I wouldn't be able to use my computer for a while.
When I got back to it, it had gone to sleep.

It wouldn't start up again. I assume that it gone to sleep while ClamWin was still going and wake up was pretty much impossible because it was too busy continuing all this scanning.
I rebooted. And what greeted me after it started up again?: Starting scheduled scan of drive c!

Lovely. Getting pretty close to uninstall this $$%^$%^$^7 now

This is an old bug; unfortunately it is still not solved (I encounter too)!
See also:
- https://forums.clamwin.com/viewtopic.php?t=1988 (main thread)
- https://forums.clamwin.com/viewtopic.php?t=2669
Due to date/week-of-year interpretation scans are started, one after each other, to infinity.

Remedie (to avoid further 'crashes')
- temporary disable all scheduled scans until 8 January (or change system-date to 8 jan.)
After 8 January the problem will not occure anymore till 1 January next year (if the problem isn't solved by ...).

Remedie (to enable computer again):
- kill all ClamScan.exe processes (in Windows Taskmanager)

The problem was fixed at the beginning of 2010 and I just tested the scheduler and found no problems.

It would be helpful if you could provide the following info:

1) What is Clamwin Version you are running?
2) When is the scheduler configured to scan and when did the problem started to occur (date/time)
3) Can you post the contents of %TEMP%\clamwin1.log when the multiple clamscan processes are started?
4) Can you email to alch at clamwin dot com the following files:
- %APPDATA%\.clamwin\clamwin.conf
- %APPDATA%\.clamwin\ScheduledScans
- %TEMP%\ClamWin_Scheduler_Info

I am having the same problem - and have had this problem before. I am running 0.96.5. I am running this same version on multiple PCs but only one is locking up?

could you provide the info as in my post above for the machine that is locking up?

The same thing is happening on my machine. (I just signed up in the forum to report this.)

Closing ClamTray and its child ClamScan.exe processes via Procexp solves the problem.

Downloading from Firefox and scanning using Fireclam with ClamWin's ClamScan.exe is not causing problems.

Thank you,

I am emailing them now. Thanks for your help

My 2003 Windows Server has multiple c\scan of clamscan.exe, so many that it keeps me from using the computer. I see it is an old bug from the posts I read. Do I really need to change the date to 1/8 to fix it, seems strange why that would do anything. Can someone fix the bug?

1) What is Clamwin Version you are running?

Latest release I uninstaleld and reinstalled, same problem.

2) When is the scheduler configured to scan and when did the problem started to occur (date/time)

Drive C sceduled to run at 11 am

3) Can you post the contents of %TEMP%\clamwin1.log when the multiple clamscan processes are started?

Where would this file be on a 2003 Windows machine?

4) Can you email to alch at clamwin dot com the following files:
- %APPDATA%\.clamwin\clamwin.conf
- %APPDATA%\.clamwin\ScheduledScans
- %TEMP%\ClamWin_Scheduler_Info

No idea where to find these files.

I had to uninstall clamwin to get my server back working. Can not change the date as it is a working server.I guess I can wait till 1/9/11 and reinstall.

You only need to wait until tomorrow (Monday) this year and it will be fixed next year (the change in source code I did at the beginning of 2010 did not make it to the binary code).

Today I started the sceduled scans again, as advised: no problems!
I'm awaiting the new version to have the problem solved definitive.
Thanks Alch!

Guys, allow me to bring the old, original thread on this issue back from the dead: https://forums.clamwin.com/viewtopic.php?t=1988 Multiple clamscan.exe killing CPU on a scheduled scan



Alch, I write code now and then but am by no means a full-time developer. Just curious, why didn't the fixed source code make it into the binary?

Timestamp on the python source file was 01/01/09 for some reason, even though it was changed in 2010 and distutils did not pick it up as changed for recompilation into a new .pyo file. The timestamp is fixed now

Wow dude! You and timestamps! Hopefully you see the irony here. You couldn't fix a time and date interpretation problem in ClamWin because distutils botched the timestamp of the source file!

BTW, look at the date I joined this forum. That goes to show you how long this issue has haunted me. This is the third New Years and there have been a couple Daylight Savings Times when this happened too.