Log4OM

Terry, I have noticed for some time now that when running FT8 with JT Alert, that random QSOs time out and do not log in Log4OM. I did some research using the realtime log in debug mode and found that at times there is an error that the database is locked. Here is an portion of the log that shows the error:

******
11:02:06.318 Info: [#=z945M4hGabQFYUtArQg==] : ############### ADD QSO Callsign: JA4JKO Date: 6/26/2021 11:01:15 AM Band: 30m Mode: FT8
11:02:06.365 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Performing QSO search on callsign JA4JKO
11:02:06.395 Debug: * [Countries][SearchCallsign][645 ms] : Performing Search Callsign on call JA4JKO on date 6/26/2021 11:02:06 AM
11:02:06.44 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Clublog CQ ZONE found for JA4JKO as 25
11:02:06.473 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Searching primary engine QRZCOM
11:02:06.507 Info: * [#=z8XKWcegbqEviGReBcg==][35767 ms] : [QRZCOM] Search start on JA4JKO (originally JA4JKO)
11:02:06.536 Info: [#=z8XKWcegbqEviGReBcg==] : [QRZCOM] JA4JKO FOUND IN CACHE!
11:02:06.568 Info: [#=z8XKWcegbqEviGReBcg==] : [QRZCOM] Search completed
11:02:06.598 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Searching clublog exceptions
11:02:06.632 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : LOTW user identified
11:02:06.677 Debug: * [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext][311 ms] : QSO search on callsign JA4JKO completed
11:02:36.913 Info: [#=zm4H5hujoMdCN7osYk1oIh7Q=] : ##### REMOTE CONTROL UDP MESSAGE RECEIVED ##### :
<CALLSIGN>BX6ABC
on UDP port 2241 from 127.0.0.1:53892
#####
11:02:36.944 Debug: [#=zm4H5hujoMdCN7osYk1oIh7Q=][MoveNext] : Remote control callsign lookup: BX6ABC
11:02:37.018 Debug: [#=zm4H5hujoMdCN7osYk1oIh7Q=][MoveNext] : Error ConnectionReset An existing connection was forcibly closed by the remote host on UDP port 2241
11:02:37.026 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Performing QSO search on callsign BX6ABC
11:02:37.228 Error: [DbSqlite][#=zfdWC$sQ0qm$G] : [SQLITE] InsertUpdateDatabase Command error
[EXCEPTION] database is locked
database is locked
11:02:37.275 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call BX6ABC on date 6/26/2021 11:02:37 AM
11:02:37.277 Error: [DbSqlite][SaveQso] : SQLITE SaveQSO exception while saving QSO with QsoId 20210626110205669
[EXCEPTION] database is locked
database is locked
11:02:37.336 Info: [#=zjQ1JHH5JlzejigvMx9KDtE3v5Wch] : {8375106d-8d0d-494a-9469-368ac59fd8b7} Process completed
11:02:37.348 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Clublog CQ ZONE found for BX6ABC as 24
11:02:37.41 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Searching primary engine QRZCOM
11:02:37.443 Info: * [#=z8XKWcegbqEviGReBcg==][30874 ms] : [QRZCOM] Search start on BX6ABC (originally BX6ABC)
11:02:37.473 Info: [#=z8XKWcegbqEviGReBcg==] : [QRZCOM] BX6ABC FOUND IN CACHE!
11:02:37.506 Info: [#=z8XKWcegbqEviGReBcg==] : [QRZCOM] Search completed
11:02:37.535 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : Searching clublog exceptions
11:02:37.569 Debug: [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext] : LOTW user identified
11:02:37.599 Debug: * [#=zN8xtisin1EZOSvuqTrRGJaw7tEtz][MoveNext][572 ms] : QSO search on callsign BX6ABC completed
*********
In this case, the callsign that failed to log was the JA4JKO. I had to go back and log it manually.

Any thoughts on what might cause this? Not a huge deal, but curious. I love Log4OM!

Thanks
Brad, N4PYI

Terry,

I failed to mention that I am running V2.

Thanks
N4PYI

I have asked Lele to check this

N4PYI wrote: 26 Jun 2021, 11:27 Terry,

I failed to mention that I am running V2.

Thanks
N4PYI

which release of V2 please

Terry,

Release 2.13.0.0.

I think I may have found what was happening. I had set my clublog to log QSOs automatically. I disabled that, and just finished running about 20 or so QSOs on FT8 and never saw the "database locked" error. And, Log4OM and JT Alert seem to be playing much more consistently than before.

Thanks
Brad, N4PYI

Please update to 2.14.1.0 and you will find it's probably fine, 2.13 is too old

Terry,

I saw the update this morning and installed it. I have turned my Clublog auto upload back on and will let you know how it goes. So far, so good.

Thanks

Brad, N4PYI

That issue is not related to Log4OM version.
It seems something goes wrong in the dialog between Sqlite drivers and their own database file.
That may result in a "locked" database that means there is something else trying to get exclusive access to the database at the same time.
When that happens there is usually a .lock file in the same folder of the database file itself. Try removing (DON'T DELETE) this file from the folder and check if that fix, if not, make an ADIF backup and create a new database loading data from the ADIF

Daniele,

The file does not stay locked continuously if that is what you are meaning. I did run more tests after the updae and so far, I have not seen the file locked error.

Brad, N4PYI