The update download utility will not work. It just continues to cycle and cycle without any files being downloaded. This started with CWP 0.93.1. Has anyone else experienced this? Is there a workaround to load the flash drive with the current definition files?
[Later edit] After spending more time on this issue, and visiting the ClamWin site, and thinking about my past experiences, I think the issue is more complicated than just excess traffic. I have ClamWin Portable on two flash drives. One is a lightning fast Kingston, and the other is a somewhat slow Lenovo (but still one of the quality drives not the marketing kind). Since upgrading to 0.93.1, the Lenovo drive has NEVER completed the automatic updating, and the Kingston drive has ALWAYS completed the automatic updating. It doesn't matter if I pull one out and put the other in and then switch back, which should make a difference if it's only traffic. Inability to update is very common; take a look at the app's support forum (not the Portable Apps one). It could be something related to the hardware it's installed on....
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
the daily cvd to data/db. Sometimes there´s too much traffic on the mirrors and update fails http://www.clamav.net/
"Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis .." Friday Next -
"May The Schwartz be with You!" Yogurt the Yoda
Had the same problem! ClamWin on the hard drive updates with no problem and then trying to update the portable installation fails consistently. After various experiments, I deleted ClamWinPortable and reinstalled it and the initial DB download worked fine so I'm hoping that either the problem is solved or I can get ClamWinPortableDBUpdate to work. Dunno what the difference is in the Main.cld and Daily.cld for the "normal" installation and the .CVD files for the portable version but they're obviously not interchangeable.
Clarification,
Wtihout addressing your update problem, I'm not experiencing it myself, I thought i would clarify the db situation of the files.
The .cvd files are the initial download of the database,
Main.cvd and daily.cvd
on the next incremental update of either one (the main occurs about one every 3 months and the daily occurs, well, daily, actually several times a day) they are expanded (think decompressed) and updated.
main.cvd becomes main.cld
daily.cvd becomes daily.cld
Note that future updates would be .cld to .cld
The files are in fact interchangeable!
You can replace a main.cld with a smaller main.cvd
and
You can replace a daily.cld with a smaller daily.cvd
I do it all the time,
or you could also do it in reverse, but I'm not sure why you would want to.
I actually use the manual download of the daily.cvd over the current one as the method of updating on my flash drive, it just seems more efficient.
This of course does not explain why you are having problems self updating on your flash
Tim
Things have got to get better, they can't get worse, or can they?
I just missed the last post. I´d like to add the explanation for the mirrors.dat file.
Sometimes deleting the mirrors.dat file results in smooth updates (it´s built anew and perhaps with different mirrors that are working)-> could be a second cause for update failure..
"Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis .." Friday Next -
"May The Schwartz be with You!" Yogurt the Yoda
Thanks Tim. I'm slowly getting an appreciation of how this works. I just wish that mine did! To recap, the primary ClamWin installation on this hard drive updates fine but the portable installation on the thumb drive refuses. It reports that the MAIN.CVD file is up to date and then just stalls. A temporary folder is created in the ..Data\DB folder with a slew of DAILY files with the current date but the Daily.CVD (or CVD) file is not updated.
And hiding the mirrors.dat file solved nothing either. No new Mirrors.dat was created and the behaviour was unchanged.
I've just tried ClamWinPortableDBUpdate from http//www.clamup.co.nr/ and nothing has changed. Same behaviour as above except that I now have a tray icon to access the stalled process and must press Ctrl-C to abort it.
what does the clamup commandline window say?
had problems with latest stable clamup -> they were resolved by using the 0.3.3 prerelease http://mkonar.selfip.com/clam/downloads/v0.3.3-prerelease/
"Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis .." Friday Next -
"May The Schwartz be with You!" Yogurt the Yoda
the update works for me.
I like clam, seems good. I hope it keeps uptodate with latest threats.
i'm having problem when i click claimwin icon..
after i click it, there is a dialog box said that i'm not yet download virus definition database n it ask me whether i want to dwnld now or not..
after i click yes, the claimwin cannot update itself..
it says:
"ClamAV update process started at Wed Aug 13 16:21:18 2008
nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 211.239.150.206)
Trying host database.clamav.net (218.44.253.75)...
nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 218.44.253.75)
Trying host database.clamav.net (219.106.242.51)..."
and this thing continue over n over again..
"ClamAV update process started at Wed Aug 13 16:21:18 2008
nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 211.239.150.206)
Trying host database.clamav.net (218.44.253.75)...
nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 218.44.253.75)
Trying host database.clamav.net (219.106.242.51)...
nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 219.106.242.51)
Trying host database.clamav.net (219.117.246.122)...
nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 219.117.246.122)
Trying host database.clamav.net (222.124.18.201)..."
what is the problem actually?
I'm not behind a proxy (remember, I have no problem updating the ClamWin on this machine's hard drive; only the portable one on the thumb drive) and I have now upgraded to the July 21 version of ClamWinPortableDBUpdate and *still* get the same behaviour: it gets as far as telling me that the MAIN.CVD is up to date and then stalls. ClamWinPortableDBUpdate eventually advises that there is a problem needing attention and I have to abort. Help?
my updates run smoothly, seems that a server is at least connected, so I don´t think that it´s a firewall problem. What happens when you wait and open the updater window?
I sometimes get an error message talking about too many bogus loops, the updater tries one server after another and finally stops.
One last try check this http://www.clamav.net/support/mirror-problem
"Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis .." Friday Next -
"May The Schwartz be with You!" Yogurt the Yoda
Just to complete the circle here, I've identified the source of my problem but don't have a "fix". I got thinking about something I mentioned here earlier: the fact that the updating worked on a previous thumb drive. So, I just installed the PA Suite on another drive (Kingston DataTraveler like the first one) and everything works perfectly! I especially like the interface with ClamWinPortableDBUpdate.
The ClamWinPortable updates fine using any method I've tried on Kingston DataTraveler drives (I've tried both the 1GB and 2GB so far) but not on a Lexar 4GB. Dunno what Lexar does differently -- it comes with SecureII software but I'm not using it.
So, at least for now, Lexar is off my list for Portable Apps. Anyone have success with Lexar drives?
This failure of ClamWinPortable to update only on certain drives has been intriguing/bugging me! So I've now installed PAM on a 4GB Kingston and a 1GB Lexar. And guess what: the smaller Lexar will update (as long as you're patient as it's much slower) and the larger Kingston won't! So now I have collected these data points:
2GB Kingston - updates fine
4GB Kingston - won't update
4GB Lexar - won't update
1GB Lexar - updates eventually
This suggests that ClamWinPortable will only update on smaller drives, despite the lack of logic in that.
To recap, the lack of updating seems not to be related to connectivity (all tests done on an Acer laptop, XP Home, home LAN). All connect and verify the Main file but only the smaller drives download and actually update the Dailies. The larger drives stall at that point and leave behind a temporary folder with a bunch of 'daily' files in it.
Can anyone add to these data points, either confirming or disproving the theory? Better still, can anyone familiar with the ClamWinPortable update process suggest a fix for this?
Forgot to mention a 1GB Kingston which I believe was updating OK but I gave that one away so can't confirm.