Log4OM

Log4Om is current version, portable setup
Pc is Windows 11
Cpu i7 9th gen
Memory 16gb
Drive is SSD

My question is why does it take about five minutes after launch of Log4Om to actually connect to the database.
I timed from when I can access the recent qso's.
Database is on SSD drive also.
I am looking at the lower right corner, the Database Connection Status remains red a full five minutes after the log has been started.
I have tried it running Log4Om as admin and as regular user, both instances do the same

Now if I open the settings> Program Configuration, and just save and apply, it will immediately show that it is connected to the database.
However when I do that, none of the connections work then, like the n1mm or wstj udp ports.

If I launch Log4Om, and just wait five minutes it all works.

I have also tried stopping my VPN, my AV, but no difference in behaviour.

TBH it is not the end of the world, just a weird behaviour truly.

If anybody has any ideas as to why this happens, I would love to hear and possibly try it out.

Hi,

Are you using SQLite or MySQL ?
Have you tried launching the log and check where there is a freeze ?

I have SQLite here and connection to Db is instantly made once Log4OM is opened.

Thanks

SQLite is what I use.
It used to connect immediately.
I cannot pinpoint at what point it stopped, because a lot of times I launch log4om and just have it sitting there.
Am wondering if size of log is at issue? just over 208000 q's should not be a problem imho.
Here is the log from about a minute after I launched Log4OM to when it connected to the database

Log:

22:31:41.515 Info: [dje_zQLY5DD8V29D3AD55AAY9Q_ejd] : [HRDLOG] Sending ON AIR message
22:31:41.534 Info: * [dje_z54665LEB2JC6FEJ2BYN72_ejd][60131 ms] : PostDataAsync: Posting data to http://robot.hrdlog.net/OnAir.aspx. upload information:
CALLSIGN=J69DS CODE=D5E5D254A3 APP=LOG4OM2 STATION=J69DS FREQUENCY=14290000 MODE=USB RADIO=ELECRAFT K3
22:32:22.521 Info: [LogWriter] : ### LOG LEVEL CHANGED FROM Info TO Debug
22:32:41.619 Info: [dje_zQLY5DD8V29D3AD55AAY9Q_ejd] : [HRDLOG] Sending ON AIR message
22:32:41.625 Info: [dje_z54665LEB2JC6FEJ2BYN72_ejd] : PostDataAsync: Posting data to http://robot.hrdlog.net/OnAir.aspx. upload information:
CALLSIGN=J69DS CODE=D5E5D254A3 APP=LOG4OM2 STATION=J69DS FREQUENCY=14290000 MODE=USB RADIO=ELECRAFT K3
22:32:41.824 Debug: * [dje_z54665LEB2JC6FEJ2BYN72_ejd][MoveNext][199 ms] : PostDataAsync: Post completed
<?xml version="1.0" ?>
<HrdLog xmlns="http://xml.hrdlog.com">
<OnAir>
<insert>OK</insert></OnAir>
</HrdLog>
22:33:41.746 Info: [dje_zQLY5DD8V29D3AD55AAY9Q_ejd] : [HRDLOG] Sending ON AIR message
22:33:41.752 Info: [dje_z54665LEB2JC6FEJ2BYN72_ejd] : PostDataAsync: Posting data to http://robot.hrdlog.net/OnAir.aspx. upload information:
CALLSIGN=J69DS CODE=XXXXXXXXXXXX APP=LOG4OM2 STATION=J69DS FREQUENCY=14290000 MODE=USB RADIO=ELECRAFT K3
22:33:41.951 Debug: * [dje_z54665LEB2JC6FEJ2BYN72_ejd][MoveNext][199 ms] : PostDataAsync: Post completed
<?xml version="1.0" ?>
<HrdLog xmlns="http://xml.hrdlog.com">
<OnAir>
<insert>OK</insert></OnAir>
</HrdLog>
22:33:41.955 Info: [dje_zSNT23LWQ6TRC96JJ5EJCZ_ejd] : [WEBPAGE] Generating webpage
22:33:41.959 Debug: [FwFile][LoadFile] : Begin load text file C:\Log4OM\config\log4om.htm
22:33:41.963 Debug: [FwFile][LoadFile] : Text file load completed C:\Log4OM\config\log4om.htm
22:33:44.559 Debug: [FwFile][WriteFile] : Begin writing text file D:\temp\log.htm
22:33:44.565 Debug: [FwFile][WriteFile] : Text file write completed D:\temp\log.htm
22:33:44.569 Info: [dje_zHPRGUKHXC62E4FY4VHCUDJBYQACA_ejd] : [FTPUPLOAD] Uploading ftp://ftp.qsl.net:21/logs/log4om.htm
22:33:46.46 Info: [dje_zKMNHX2F5Z47DWFUYP8APQ_ejd] : Worked before list updated
22:33:46.464 Debug: * [dje_zAGYH766ZKBXGEMVPET8YZS7XDFVFUZA4GS_ejd][MoveNext] [WORKED] : End calculating worked callsigns
22:33:46.471 Info: * [dje_zGVN4ADVY7Y24R63SMP29SMFKDSGA_ejd][333253 ms] : Recalculating statistics asynchronous process completed
22:33:57.053 Info: [dje_zHPRGUKHXC62E4FY4VHCUDJBYQACA_ejd] : Upload File terminated, status 226 Transfer complete.
22:33:57.057 Info: [dje_zM7KYKQ4FRZU2EP4543QE48BJY77A_ejd] : [WEBPAGE] Webpage process terminated
22:34:21.828 Debug: [FwFile][WriteFile] : Begin writing text file D:\Log4OM\Log\Log4OM_log_20240729223409.txt
22:34:21.838 Debug: [FwFile][WriteFile] : Text file write completed D:\Log4OM\Log\Log4OM_log_20240729223409.txt
22:34:41.86 Info: [dje_zQLY5DD8V29D3AD55AAY9Q_ejd] : [HRDLOG] Sending ON AIR message
22:34:41.874 Info: [dje_z54665LEB2JC6FEJ2BYN72_ejd] : PostDataAsync: Posting data to http://robot.hrdlog.net/OnAir.aspx. upload information:
CALLSIGN=J69DS CODE=D5E5D254A3 APP=LOG4OM2 STATION=J69DS FREQUENCY=14290000 MODE=USB RADIO=ELECRAFT K3
22:34:42.092 Debug: * [dje_z54665LEB2JC6FEJ2BYN72_ejd][MoveNext][218 ms] : PostDataAsync: Post completed
<?xml version="1.0" ?>
<HrdLog xmlns="http://xml.hrdlog.com">
<OnAir>
<insert>OK</insert></OnAir>
</HrdLog>

All your logfile shows is the section for upload to HRDlog and your web site and considering the number of QSO's in your database its fairly fast.

With the number of QSO's you have I would be using a MySQL database

Also consider just how many checks are being done while doing the various load operations.

Word of advice - Be carefull when posting your log file here it could be risky - I have deleted your HRDlog code for you!

Oops I did not pay attention and missed that code.. appreciated it.

Yeah I have contemplated to go the route of mysql..

actually I think I will spend some time with that and see what difference that makes.

Carefull as last version of MySQL as well as MariaDb does not work with Log4OM, I think Daniele is working on it.

Hi, thank you for the heads up re compatibility.

I also ran a vacuum on the sqlite database.
and at 361Mb the size is small insofar as to what sqlite can handle.
Also did a clean of Application cache

However neither made a difference insofar as time it takes to get a connection to the database.

Main reason I did create this thread was to see if others had the same experience and or found a solution to it.

But it seems not or nobody notices it maybe.

The onliest time it becomes obvious is if I come on in a hurry to work a specific station.. otherwise it is not a big deal

I experienced the same issue and it takes time to connect to the database, my personal experience is not to use MYSQL because it is much slower and will create more problems, my recommendation is to stick to SQLite. I have more than 500k qso and yes it is not super fast but it was acceptable and much faster when I was with MYSQL.

This is my personal opinion

J69DS wrote: 02 Aug 2024, 22:08 Hi, thank you for the heads up re compatibility.

I also ran a vacuum on the sqlite database.
and at 361Mb the size is small insofar as to what sqlite can handle.
Also did a clean of Application cache

However neither made a difference insofar as time it takes to get a connection to the database.

Main reason I did create this thread was to see if others had the same experience and or found a solution to it.

But it seems not or nobody notices it maybe.

The onliest time it becomes obvious is if I come on in a hurry to work a specific station.. otherwise it is not a big deal

Try dissabling other features of Log4OM like VOACAP

Also see performence tab of config