Log4OM

Sometimes...not all the time...hamlib fails to start up.
Was able to catch this with CAT debug turning on quickly startup -- since we don't save the debug settings across restarts -- could we get these saved please?

Here's the debug showing Log4OM trying to connect to rigctl with only about a 10ms wait. If connection is refused there should be a reattempt for up to 10 seconds (perhaps a 1 second retry timeout) as some rigs can take a long time to start up.

2024-04-12 15:58:11.8751 INFO: [dje_z9GQNBR4Q_ejd] : [HAMLIB] DAEMON STARTED: C:\Users\cfogr\AppData\Roaming\Log4OM2\hamlib\rigctld.exe --model=4 --rig-file=127.0.0.1:12345 -vvvv -Z --vfo
2024-04-12 15:58:11.9623 ERROR: [HamlibEngine][dje_z8XB636PXDTFMEH3QMEJNC4FEFPUQ_ejd] : [EXCEPTION] No connection could be made because the target machine actively refused it 127.0.0.1:4532 System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:4532

Hello,

next time this issue occurs, can you please :
- open a terminal (WIN+R and type "cmd")
- run the following : netstat -an | find "4532"

Port 4532 may be listed in LISTENING state. What can you see in your case ?

rigctld is still running -- but it is Log4OM expecting an immediate (i.e. 10ms) response that is the problem.
There needs to a be a longer retry.

To restate this -- it seems Log4OM is only waiting 10ms for rigctld to offer the TCP port.
That is too short as things can take longer before the tcp port is available.
I'd recommend a retry for 2 seconds to cover the future.

Mike W9MDB

This seems to be fixed in 2.32.1.5 but is not mentioned in the change log.