Corrupted database

Yes, sometimes it happens... Please report any bugs here
Post Reply
G3ZSS
Log4OM Beta Team
Posts: 147
Joined: 21 Jan 2013, 15:32

Corrupted database

Post by G3ZSS » 06 Feb 2013, 09:50

Ever since upgrading to the latest version, I have twice had a database corruption failure. Luckily I can build a new database by importing the backup ADIF file, but I am very concerned by these database failures. Attached is my log file. Peter G3ZSS
73 Peter G3ZSS

User avatar
IW3HMH
Site Admin
Posts: 2378
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: Corrupted database

Post by IW3HMH » 06 Feb 2013, 10:02

Hi Peter, i've deleted your log attachment after downloading it. Please don't attach on the forum because it can contains some of your personal informations.
This is really a strange behaviour, i never experienced this before. I'm doing a full search on the error reported.

Where is this file saved? The file is saved in a google drive folder or similar?
73
Daniele Pistollato - IW3HMH

G3ZSS
Log4OM Beta Team
Posts: 147
Joined: 21 Jan 2013, 15:32

Re: Corrupted database

Post by G3ZSS » 06 Feb 2013, 10:27

Thanks Lele. The file is saved in a folder on my PC, with automatic replication on my Network Server. I did check the log file first to make sure it did not contain any passwords! If it helps, I can email you directly a copy of the SQLite file. 73 Peter
73 Peter G3ZSS

User avatar
IW3HMH
Site Admin
Posts: 2378
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: Corrupted database

Post by IW3HMH » 06 Feb 2013, 13:50

I think probably the issue is related to something that locks the file before it's closed by Log4OM (software will open database on demand and closes it every time). It's possible for you to save the logfile in another folder AND set backup files on your network replicated folder?

I need to understand if this issue is related to something your O.S. is doing on the file preventing Log4OM writing on it.

I'm about to change the logfile deletion policy to keep errors in some way between subsequent program starts. This could help too...

Let me know if it's possible to do this for some days and if the issue happens again.

Thanks in advance
Daniele
Daniele Pistollato - IW3HMH

K7PT
Old Man
Posts: 726
Joined: 21 Jan 2013, 13:54

Re: Corrupted database

Post by K7PT » 06 Feb 2013, 14:22

I had a user that also wound up with a corrupted log. Not sure if was something he did or if the program did something to corrupt it.

I had to help him reinstall his logbook and didn't think to alert anyone.

I note this just as a possibility as now another user has had a similar issue.
K7PT-Chuck "#1 Top of the Honor Roll"

Post Reply