I have just started having this problem. I have a weekly schedule scan on Saturday morning. This last Saturday I missed turning on my laptop and missed the schedule. Since then ClamWin has been starting up multiple instances of clamscan.exe I deleted %temp%\Clamwin_Scheduler_Info file but this did not help. In ClamWin1.log it mentions the following:-


"System Locale: ('en_GB', 'cp1252')
Default Encoding: cp1252
command line path:
Scheduler <built>((66092, 273, 1024, 3)), frequency :Hourly terminated
Scheduler <function>((<__main__>, 'G:\\', 'Mercury Memory Card scan', 1)), frequency :Weekly terminated
Scheduler <built>((66092, 1047, 0, 4)), frequency :Daily terminated
Scheduling task (66092, 273, 1024, 5) for: Mon Dec 29 16:09:00 2008
couldn't parse time, self._startTime = 02:50:00. self._weekDay = 5
Error: time data did not match format: data=369 2008 02:50:00 fmt=%j %Y %H:%M:%S
Scheduling task (<__main__>, 'G:\\', 'Mercury Memory Card scan', 1) for: Mon Dec 29 15:15:43 2008
Scheduling task (66092, 1047, 0, 6) for: Tue Dec 30 15:06:51 2008"


It seems to no longer be able to parse the time data from my computer.
I changed the schedule to hourly and the problem seems to have stopped. However this then would mean that I can only set hourly or daily schedules but I want this to be a weekly schedule. Is there anything I can do to overcome this without having to run the schedules manually or daily.

Have had this problem on 4 servers so far. I am disabling schedules untill jan 1, since its reporting today as day 369 of 2008 (?!), if I'm reading the error line correctly.

Here are two %temp%\ClamWin1.log's:

Are you certain you have the latest version 0.94.1?

In the latest version clamwin does not run missed schedules for scans.

I have the latest version 0.94.1

I am having this problem. I don't have the temp file in question to delete. Tell me what info you need and I will provide it.

I curently have Clamwin disabled as it takes 100% cpu and runs at least 4 instances.

Thanks

I am also having the same issue. I'm running 0.94.1 and I do not have the temp file to delete. It just started an hour ago when I booted up my laptop. I'm running XP (32bit) SP3. Another issue, I schedule my weekly scans for Thursdays at 0230, it is currently Monday 8:30pm. I currently am not running Clamwin. I tried to restart the tray from the \bin folder, but the weekly scans started again for no reason. Any ideas what is going on?

I scheduled weekly on Sat. and Sun., One for drive C:, the other for drive D:
Everything is fine until the following thing happened:
1. 12/28 Clamwin found an infected file in IE cache and made a quarantine, the log is as in the following:

C:\Documents and Settings\user\Local Settings\Application Data\Mozilla\Firefox\Profiles\pm91k2xh.default\Cache\C287C23Fd01: JS.Agent-35 FOUND

2. 12/29 Window Xp made an automatic windows update and rebooted my PC in the early morning.
3. 12/29 The clamwin began to scan and scan again,...

The instances of clamscan may be up to 20. All of them can not finished scan and aborted accidently. This phenomena happened all day and I can not use my PC at all. So I restart my PC and deactivated all the scheduled scan. Now the PC come back to me. I can do my work as usual. I hope the description of my experience can help to find out what is going on, and find a way to fix it.

I am running 0.94.1 and since I changed the schedule to daily I have not had any problems. I just checked and after changing the schedule to weekly (changing nothing else) then after a couple of minutes Clamwin started running and repeated this every 3 or 4 minutes. As I was testing a scan with a memory card location then the scan was finished before the enxt started but when I use the scan of my C: drive then this is when multiple instances end up running. I then changed it back to daily and o problems.

Although I originally linked it to missing a scheduled scan I am ot sure that is valid. The schedule was missed on early morning of 27th Dec but I used the laptop several times on Saturday and Sunday and no multiple instances occurred. The problem started on Monday 29th Dec for the first time.

In the logs it definitely mentions not being able to parse the date/time so like darkmirage I am going to disable the schedules and see what happens on this Saturday (3rd Jan 2009) and will feedback what I find.

can it ever be switched back to weekly?

I am having same issues, same error in ClamWinlog1.txt

We just removed scanning for now as its a major pain to fix each machine. Either Windows update ran and patch messed up the date format that is causing this.

Greetings,

I am having the same problems on computers all over New Orleans. I by default install ClamWin on all the machines I offer support to. I schedule a weekly scan on all of them, Thursday and Friday on most machines.

Yesterday and today, I am getting calls from all over that computers are grinding to a halt, and they all have multiple versions of clamscan.exe. I am restarting each computer and exiting clamtray until I can find a solution. I am running 0.94.1, and on one machine I even uninstalled ClamWin and reinstalled a newly downloaded version, set it up for weekly scanning again and about 20 minutes later again multiple clamwin.exe processes started running.

From reading other posts, I am assuming this is happening because most machines were shut down last week when scheduled scans were supposed to happen. I hope someone can find an easy fix that I might be able to relay over the phone to clients.

thanks,
pax

Hi All

I to have the same issue with Clamwin running on two laptops running Windows XP with SP3, A laptop running Vista Premium and two desktop PC's running Windows XP with SP3.

All show the same symptoms, on boot, within minutes Clamwin attempted to scan C Drive, but fails, then it attempts to execute another scan, and so on. When you check Windows Task Manager in Processes you see multiple Clamscan.exe running, consuming 100% CPU Usage. As I have one machine set to send email notification on virus detection it sends a report that is blank on each Clamscan.exe that the Task Process is terminated within Task Manager.

At first on one machine I un-installed and re-installed Clamwin. The same thing occurred with multiple processes.

I have removed the scheduled scans, this appears to have resolved the issue for now.

Like others, I will watch this thread for further development or confirmation of a problem.

To others that have posted, at least you know �you are not alone�.

This is the first time I have ever had any problem with Clamwin. May I pass on my thanks and gratitude to the Clamwin team for an excellent product.

Tony

On one computer (WIN2003) I get every 2 minutes a new clamscan.exe task for each schedule. If I change schedule to daily - no problem. Apparently there is an issue with checking the time. Whenever a new tast appears I see:
---
couldn't parse time, self._startTime = 11:00:00. self._weekDay = 6
Error: time data did not match format: data=370 2008 11:00:00 fmt=%j %Y %H:%M:%S
Scheduling task (<__main__>, 'D:\\', 'DatenScan', 1) for: Tue Dec 30 22:30:31 2008
---
the last lines show the time intervall:
Scheduling task (<__main__>, 'D:\\', 'DatenScan', 1) for: Tue Dec 30 22:28:30 2008
Scheduling task (<__main__>, 'D:\\', 'DatenScan', 1) for: Tue Dec 30 22:30:31 2008
Scheduling task (<__main__>, 'D:\\', 'DatenScan', 1) for: Tue Dec 30 22:32:31 2008
Scheduling task (<__main__>, 'D:\\', 'DatenScan', 1) for: Tue Dec 30 22:34:32 2008
Scheduling task (<__main__>, 'D:\\', 'DatenScan', 1) for: Tue Dec 30 22:36:33 2008

In the last weeks I occasionally found that the computer had restarted. I can't remember exactly, but I think it allways happened two days after the scan was scheduled. Today I just by chance worked on the server and found it awfull slow - the reason were about 50 clamscan tasks with abt. 70MB RAM each. So a lot of tasks were shifted to the swap area on hd. After restart (reset button) the same situation occured about 2 hours later - this time I could kill the process structure clamtray which killed all clamscan processes as well and the allowed a 'clean' reboot'. Nevertheless - even after clearing the complete tmp folder - it again started to build tasks. After I found this thread I switched to daily which currently fixes the issue.

I made a crosscheck on a XP machine where there were no issues. I changed the daily scan to weekly and after about 5 minutes it started to create scan tasks every two minutes also.

Hope this helps
Gregor

I am having a similar issue. Clamscan.exe processes show up in too many instances, taking up RAM beyond available memory and taking up most of the CPU.

The last entry in the log is a manual scan. I killed all the processes, because if there's at least one, it multiplies. So the log doesn't show completed scans.

By the way, the system tray displayed a message it's doing my weekly scan, but the scan wasn't scheduled for today. If I start it manually, it starts and finishes fine.

Regards,
zratis

***


Scan Started Tue Dec 30 21:09:41 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


Scan Started Tue Dec 30 21:09:41 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


Scan Started Tue Dec 30 21:11:44 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


Scan Started Tue Dec 30 21:11:44 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


Scan Started Tue Dec 30 21:16:33 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


Scan Started Tue Dec 30 21:16:33 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***

WARNING: Can't open file C:\WINDOWS\System32\smss.exe, Permission denied

Scan Started Tue Dec 30 21:14:05 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


Scan Started Tue Dec 30 21:14:05 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***

WARNING: Can't open file c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorsn.dll, Permission denied

Scan Started Tue Dec 30 21:18:48 2008
-------------------------------------------------------------------------------


Scan Started Tue Dec 30 21:18:48 2008
-------------------------------------------------------------------------------


Scan Started Tue Dec 30 21:07:41 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


*** Scanned 56 processes - 399 modules ***
*** Computer Memory Scan Completed ***


Scan Started Tue Dec 30 21:07:41 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


*** Scanned 56 processes - 399 modules ***
*** Computer Memory Scan Completed ***


Scan Started Tue Dec 30 21:21:42 2008
-------------------------------------------------------------------------------


Scan Started Tue Dec 30 21:21:42 2008
-------------------------------------------------------------------------------


Scan Started Tue Dec 30 21:23:49 2008
-------------------------------------------------------------------------------


Scanning aborted...

----------- SCAN SUMMARY -----------
Known viruses: 87797
Engine version: 0.94.1
Scanned directories: 0
Scanned files: 0
Infected files: 0
Data scanned: 0.00 MB

Scan Started Tue Dec 30 21:23:50 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


Scan Started Tue Dec 30 21:38:49 2008
-------------------------------------------------------------------------------

*** Scanning Programs in Computer Memory ***
*** Memory Scan: using ToolHelp ***


*** Scanned 55 processes - 371 modules ***
*** Computer Memory Scan Completed ***


----------- SCAN SUMMARY -----------
Known viruses: 482988
Engine version: 0.94.1
Scanned directories: 0
Scanned files: 426
Infected files: 0
Data scanned: 167.09 MB
Time: 72.154 sec (1 m 12 s)

We are having a similar issue here at the school district. I have 3 machines so far ( many people out for Holiday) that say the computer constantly needs to be restarted. The scheduled scan of their Windows folder keeps poping up on the tray and when I check task manager ( win.XP SP2,3) there are at least 15 instances of the daily scan running. I tried to download the latest sig. files to see if this corrected the issue, it did not. I ended up removing the scheduled scans from set-up until a resolution is found.
I need to know what to try though because I have many other users with the same scheduled scans of their machines.

I also confirm that I began experiencing this problem for the first time after 25th December. I have a weekly scan schedule setup, and a scan job was due to run on 25th December. I did not start the computer on that day (being xmas) and when I restarted the machine on monday 27th it began running the "Thursday" scheduled scan.

Like everyone else has reported, it spawned 15-20 instances of the scan job and finally used up all my spare Temp file space.

I have not had any problems at all with clamwin before this incident.
I tried doing a number of things - without success - and eventually uninstalled and reinstalled the product (version 0.94.1). No joy. As soon as clamtray starts ..within a few minutes it once again begins the scheduled scan jobs - with same endless result.

I can run each of the scheduled job manually and they perform perfectly - but if I let the scheduler start the jobs, they never finish.
I have now deactivated the schedule and must assume this is a code bug . I will await a future fix.

Just one other thing - I am running clamwin on a win98 machine - and it has always worked perfectly prior this.