PG2 "Blocking 0 IPs" Issue Exists In Peerblock

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Installed and updated Peerblock
2. Shows as "Blocking 0 IPs"

What is the expected output? What do you see instead? See above

What version of PeerBlock are you using? On what operating system? 32- or
64-bit? PeerBlock-Setup_v0.9.2.r86.exe on WinXP Home SP3 32-bit

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

Original issue reported on code.google.com by j_rot...@yahoo.com on 27 Aug 2009 at 5:58

Attachments:

• peerblock.log
• [Blocking 0 IPs.bmp](https://storage.googleapis.com/google-code-attachments/peerblock/issue-73/comment-0/Blocking 0 IPs.bmp)

[GoogleCodeExporter]

Could you open up the C:\Program Files\PeerBlock\lists\560054545.list file in 
notepad
and check its contents, and/or post it here?

Original comment by peerbloc...@gmail.com on 27 Aug 2009 at 6:05

[GoogleCodeExporter]

Here you go. Thanks.

Original comment by j_rot...@yahoo.com on 28 Aug 2009 at 1:03

Attachments:

• 560054545.list

[GoogleCodeExporter]

Hmm, other than a 7z header this .list file actually contains no data.

Looks like the peerblock.log is from a later run of the tool than when this 
file was
first downloaded, since it says it didn't attempt to update the list because not
enough time had passed yet.  This may be related to Issue #72, in that PeerBlock
probably tried downloaded the list but downloaded "garbage" of some sort, and 
then
decided to start using it anyway even though it hadn't validated that the list
actually contained useful data.

On the plus side, you've got an easy workaround - delete that list-file and 
restart
PeerBlock (or just click the "Check Updates" button from the main window).  Are 
you
using one of the default lists, hosted by peerguardian.sourceforge.net?  If so, 
their
blocklist-servers are notoriously unreliable and may have contributed to this 
problem
- if you update to use a different list such as the ones hosted by 
iblocklist.com,
this should help prevent this error occurring in the future.  I have a post up 
on our
Dev Blog explaining how to do this, if you're interested:
(http://devblog.peerblock.com/2009/08/updating-to-iblocklist-lists.html).

Other than that, once we fix Issue #72 you shouldn't have any problems - I'd
recommending "starring" that bug so you get updates on its progress.  Until 
then I'd
keep an eye on things the at least the first couple of times you start/update
PeerBlock, just to make sure a different list-server is in fact working better 
for you.

Original comment by peerbloc...@gmail.com on 28 Aug 2009 at 1:31

[GoogleCodeExporter]

Thank you for the speedy response and very clear troubleshooting instructions. 
It
worked like a charm. 

Original comment by j_rot...@yahoo.com on 30 Aug 2009 at 12:26

[GoogleCodeExporter]

Great, glad to hear it!  For now I'll dupe this bug to Issue #72, we can always
re-open it or add another one if it turns out that fixing that one (once we get
there) doesn't actually fix this one after all.

Original comment by peerbloc...@gmail.com on 30 Aug 2009 at 12:32

• Changed state: Duplicate