hello I am sorry to report that ClamWin will not run with the replacement clamwin.zip file provided, it fails to launch at system start and trying to manually launch also fails. Restoring the clamwin.zip file to the orig version restored program operation (albeit with bug still in effect).

clamwin1.log file (i believe this to be from the orig clamwin.zip run as I can't see a change after the abortive attempts to run clamwin with the replacement clamwin.zip)..



I will be going to bed shortly (as it is after 11PM here in San Diego) but I'll check again tomorrow to see if i can do/try anything else to attempt to assist with this.

thank you again for your efforts certainly.

This might seem silly, as I know next to nothing about Python and have not read that far into of the other code in that file but I assume that

is later checked to determine whether the job should run again immediately. If this is the case, should it really be set to True in the exception handler? This suggests that, if ever an error occurs parsing the date, the job will run again straight away, which looks like the cause of this issue.

Also, rather than build up the time from composite, would it make more sense to do something like:

The upload interrupted half way for some reason, please try the new file (it might be necessary to change your system clock a day or two back as the problem is going to disappear very soon by itself)

The opposite, if the scheduled task has _runMissed = false and _scheduleMissed = true - then the task shouldn't run.



Thanks, I had no idea about timedelta when I wrote that code.

ah gotcha..i have downloaded clamwin.zip again and enabled clamwin + scheduled scans here is the clamwin1.log

so far so good system hasn't been rendered inoperable by multiple instances ..

Alch, I didn't get a chance to try your replacement clamwin.zip file because the year-day is now greater than the week-day. So the problem has gone away on its own again. I did manage to get you a snippet of ClamWin1.log after the problem started:

Just happened to me today - froze my mail server. Tried installing the .zip file and it didn't work. Is no one else posting about this because they don't have the issue any more? I am running the latest clamwin. After having to restart the server more than 5 times from the power switch I renamed clamscan.exe until I get an answer on this!

the scheduler issue was only confined to the New Year period.You can try deleting %tmp%\ClamWin_Scheduler_Info and see if it helps

Well, apparently it is not confined to the New Year period or I am having another issue. I tried deleting the file but I still get multiple copies of clamscan.exe showing up in my task manager and it bought my mail server to it's knees again. Is there anything else I can look for? The date is correct on the server.

this must be a different issue because the one discussed in this thread earlier only happened within the first week of 2010.

A couple of questions:
1) How are you using clamwin on the server? Do you just use the builtin clamwin scheduler to scan at the set interval?
2) What are your scheduled scan settings?
3) Please paste %temp%clamwin1.log as straight after you get multiple instances (do not open clamwin before you do so or it will overwrite the log file)

Of course, now that I am waiting for it to do it again it hasn't done it! I am using the clamwin scheduler, I have three drives - one I scan daily and the other two weekly. So there are three schedules set up. I will post the log file if it does it again. Thanks.

It did it again. I managed to kill the processes and rename clamscan.exe so it won't do it again. Here is the clamwin1.log right after I killed the processes:

Scheduling task (66068, 273, 1024, 1) for: Fri Feb 19 08:36:00 2010
Scheduling task (<__main__>, 'C:\\', 'Daily C Scan', 1) for: Fri Feb 19 00:30:00 2010
schedTime: (2010, 2, 18, 1, 30, 0, 3, 49, -1)
Scheduling task (<__main__>, 'E:\\', 'Weekly E Scan', 1) for: Thu Feb 25 01:30:00 2010
schedTime: (2010, 2, 19, 1, 30, 0, 4, 50, -1)
Scheduling task (<__main__>, 'F:\\', 'Weekly F Scan', 1) for: Fri Feb 19 01:30:00 2010
Scheduling task (66068, 1047, 0, 2) for: Thu Feb 18 13:31:21 2010
Scheduler <built>((66068, 273, 1024, 1)), frequency :Daily terminated
Scheduler <function>((<__main__>, 'C:\\', 'Daily C Scan', 1)), frequency :Daily terminated
Scheduler <function>((<__main__>, 'E:\\', 'Weekly E Scan', 1)), frequency :Weekly terminated
Scheduler <function>((<__main__>, 'F:\\', 'Weekly F Scan', 1)), frequency :Weekly terminated
Scheduler <built>((66068, 1047, 0, 2)), frequency :Daily terminated

I don't see anything wrong in this logfile other than 'Daily C Scan' is not likely to finish before 'Weekly F Scan' and two clamscan.exe processes will run in paralell.

How many did you kill?

I had to kill about 8 copies. This was after shutting the machine down via the power switch because it was pinned - I am not sure how many copies were running then.