search

warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

updating list #299

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.opening program
2.updating list 
3.cache error when finished updating

What is the expected output? What do you see instead?
program used same list without finishing the update.

What version of PeerBlock are you using? On what operating system?
64-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 shawnv...@gmail.com on 5 Apr 2010 at 3:12

Attachments:

GoogleCodeExporter commented 9 years ago 
Please check the size of your C:\Program Files\PeerBlock\history.db file.  This 
error
is caused by issues in our database-accessing code, and this file - which 
contains
your History of allowed/blocked IP addresses (as per your settings) - is the 
only one
we're using.  Our current theory is that many of these issues may be caused by a
too-large history.db file, so if you could verify that for us it would be 
greatly
appreciated.

After checking that file's size, if it's actually _not_ excessively large if you
could upload it to e.g. mediafire.com for us to analyze that would be great.  If
you're concerned about security feel free to compress it into an encrypted .zip 
(or
.7z, or whatever) file, and then email the password for it to us at
http://tinymailto.com/peerblock

Exiting PeerBlock, deleting this history.db file, then re-starting PeerBlock 
again
should resolve this problem for you.  If you wouldn't mind waiting to do this 
until
after you look into the aforementioned things though that would be greatly 
appreciated.

Original comment by peerbloc...@gmail.com on 5 Apr 2010 at 3:18

GoogleCodeExporter commented 9 years ago 
it says only 21.3 mb ill still upload it

Original comment by shawnv...@gmail.com on 5 Apr 2010 at 3:35

GoogleCodeExporter commented 9 years ago 
http://www.mediafire.com/?zmjtmitdjmd  sent pw in email also

Original comment by shawnv...@gmail.com on 5 Apr 2010 at 3:46

GoogleCodeExporter commented 9 years ago 
Thank you for uploading the file!  Unfortunately I'm able to load that file up 
in my
own installation of PeerBlock without problem - no errors trying to log to it, 
or
view it, or anything else.

The sqlite3 docs state "This value is returned if the operating system informs 
SQLite
that it is unable to perform some disk I/O operation. This could mean that 
there is
no more space left on the disk.".  Might be worth checking for disk-space, or 
running
through a low-level disk utility to make sure your harddrive isn't going bad.  I
wonder if maybe the file is just too fragmented?  If you haven't yet deleted the
file, running it through a single-file defragmenter like contig
(http://technet.microsoft.com/en-us/sysinternals/bb897428.aspx) with the "-a" 
option
would be interesting to see.  Another interesting experiment would be exiting
PeerBlock then creating a copy of this history.db, deleting the original, and 
then
renaming the copy to be history.db again.

Right now my thinking is that we may need to specifically trap this error and 
then
try deleting/recreating history.db if we hit it . . . but if we can come up 
with some
alternative solutions those might be preferable to losing all your historical 
data.

Original comment by peerbloc...@gmail.com on 5 Apr 2010 at 4:53

GoogleCodeExporter commented 9 years ago

Original comment by nightstalkerz on 27 May 2012 at 2:57