Stop attempting to log to history if hit reoccurring sqlite errors

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Run PeerBlock on a computer with very low disk space
2.This error:

Build Number: 30910210202
File: .\logproc.cpp
Line: 321
Type: class sqlite3x::database_error
Message: database or disk is full

Shows repeatedly
3. It goes away as soon as HDD space is cleared

What is the expected output? What do you see instead?
It's annoying to have to continually close this message (whilst trying to 
clear HDD space), it should show less frequently if possible.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?
XP SP2 x32
PeerBlock r202

Obviously it's not good to run any computer with NO HDD space, but on 
occasion it does happen (in this case on my download box VM), and when it 
does having repeated error messages is quite annoying!

Cheers!

Hoodadilly

Original issue reported on code.google.com by nathan.v...@gmail.com on 5 Nov 2009 at 2:10

Attachments:

• peerblocklog.txt

[GoogleCodeExporter]

I should add; this error showed every 15 seconds untill i managed to clear some 
HDD 
space - 9 times in total

Original comment by nathan.v...@gmail.com on 5 Nov 2009 at 2:11

[GoogleCodeExporter]

I am experiencing the same problem but I've got 7GB of free space on the drive.
That's far from being low.

Original comment by nexd...@gmail.com on 14 Dec 2009 at 1:15

[GoogleCodeExporter]

Yes, if the code we're using to interface to the history database starts 
encountering
problems we'll report that problem time and time again.  What would make more 
sense
would be to disable history logging (at least temporarily), warning the user 
that
this is happening.  This should silence these errors after that.

Original comment by peerbloc...@gmail.com on 20 Jan 2010 at 6:44

• Changed title: Stop attempting to log to history if hit reoccurring sqlite errors
• Changed state: Accepted
• Added labels: Milestone-1.1

[GoogleCodeExporter]

I had the same issue as nexdeci.  Several gigs of free space on the hard drive, 
and 
constant errors stating that the database or disk was full.

My issue is that the log file was almost 4 gigs in size on a FAT32 drive.  
First of 
all, FAT32 can not handle file sizes above 4gigs, secondly, I did not need or 
want 
the log files.

My solution was to close peerblock, delete the history.db file in the peerblock 
progam folder, re-launch peerblock, click on the settings tab and chose the log 
none 
option in the history section.

If you need to monitor your traffic, you should chose to log the traffic you 
need 
(Block, Allow, or both) and select archive and remove every 1 day.

If you are using a FAT32 file system, you can not handle logs over 4 gigs.  
NTFS 
will handle larger logs.   In either case, if you do NOT need to look at them, 
these 
will be a tremendous waste of disk space.

John

Original comment by johncor...@shaw.ca on 12 Mar 2010 at 3:49