Logging issue: WSJT > JTalertX > Log4OM

Need help? - Post here and we will find a solution for you.
Locked
hb9cat
Advanced Class
Posts: 39
Joined: 12 May 2014, 05:57

Logging issue: WSJT > JTalertX > Log4OM

Post by hb9cat »

Hello,

I've been logging FT8 through JTalertX to Log4OM for a while now and it worked just fine.

All of a sudden it does not work anymore; I did have a power failure in between.

Log4OM relevant log:
2019-08-10 06:48:32.2935 INFO: #=qprM9VsL7G_ODbcBnVbKa51zhlSYtdNhcTB0aO5wr7E0=: Incoming TCP QSO <CALL:6>SP9TTV<DXCC:3>269<COUNTRY:6>Poland<QSO_DATE:8>20190810<QSO_DATE_OFF:8>20190810<TIME_ON:6>064800<TIME_OFF:6>064800<FREQ:8>7.075196<FREQ_RX:8>7.075196<BAND:3>40m<BAND_RX:3>40m<MODE:3>FT8<RST_SENT:3>-21<RST_RCVD:3>-11<GRIDSQUARE:4>JO90<DISTANCE:3>837<TX_PWR:3>500<LAT:11>N050 30.000<LON:11>E019 00.000<CQZ:2>15<ITUZ:2>28<PFX:3>SP9<CONT:2>EU<MY_GRIDSQUARE:6>JN46PN<MY_CQ_ZONE:1>0<MY_ITU_ZONE:1>0<STATION_CALLSIGN:6>HB9CAT<QSO_COMPLETE:1>Y <EOR>

2019-08-10 06:48:32.5845 ERROR: *** TCPClientManager: Socket error during Read: [SocketException] Connessione in corso interrotta forzatamente dall'host remoto

So the QSO gets in via UDP from JTalertX to Log4OM but it's not logged; and the TCPClientManager shuts down.

Normal logging (type in qso in Log4OM) is working, so the database should be OK (MySQL)

Any hint ?

Marco HB9CAT
User avatar
NN7D
Log4OM Alpha Team
Posts: 816
Joined: 19 Feb 2014, 19:44

Re: Logging issue: WSJT > JTalertX > Log4OM

Post by NN7D »

Hi Marco,

I would suggest normal stuff like restarting computer, then trying again. Also, make sure the two unlabeled LED indicators at the bottom of the main UI window to the left of the Cluster LED are green. Make sure Communicator is running. Open Communicator and make sure the TCP Connection to Log4OM LED is green. Then minimize Communicator - don't close it.

BTW, we are about to release version 1.39 of Log4OM. It will have a facility to receive UDP adif log QSO messages direct from WSJTx, so you don't have to rely on JTAlert.

Let us know your results, good or not-so-good.

73,
Doug - W7DRM
Doug - NN7D
Gig Harbor, WA, USA
hb9cat
Advanced Class
Posts: 39
Joined: 12 May 2014, 05:57

Re: Logging issue: WSJT > JTalertX > Log4OM

Post by hb9cat »

Doug,

thanks for your feedback, I did go through the obvious restarts/reinstalls prior to sending a message to the forum.
I also did install v1.39 and enable ADIF UDP logging (turned off other methods)

The result is essentially the same: Log4OM does receive the QSO but it's not logged and a Socket exception is generated closing also the port 8081 connection.

So the problem is not related to JTalertX, it's a LOG4OM issue; any further ideas ?

Marco HB9CAT

Log:
2019-08-30 16:35:16.4280 INFO: #=qnb4cOIBeC30hWg3jtJKYnBjQLnzAJ$js0VfNyU7HKXY=: UDPSERVICE received message:<call:6>BH3SCC <gridsquare:4>OM67 <mode:3>FT8 <rst_sent:3>-11 <rst_rcvd:3>-18 <qso_date:8>20190830 <time_on:6>163513 <qso_date_off:8>20190830 <time_off:6>163513 <band:3>40m <freq:8>7.075196 <station_callsign:6>HB9CAT <my_gridsquare:6>JN46PN <tx_pwr:3>500 <eor> on UDP port 2333 (ADIF/INCOMING)
2019-08-30 16:35:16.4500 INFO: #=qiV_55X23gMSkxyDHm2CMcQ821_iC3$mYHwdzQjo0sso=: Incoming QSO from ADIF UDP <call:6>BH3SCC <gridsquare:4>OM67 <mode:3>FT8 <rst_sent:3>-11 <rst_rcvd:3>-18 <qso_date:8>20190830 <time_on:6>163513 <qso_date_off:8>20190830 <time_off:6>163513 <band:3>40m <freq:8>7.075196 <station_callsign:6>HB9CAT <my_gridsquare:6>JN46PN <tx_pwr:3>500 <eor>
2019-08-30 16:35:16.6620 ERROR: *** TCPClientManager: Socket error during Read: [SocketException] Connessione in corso interrotta forzatamente dall'host remoto
User avatar
G4POP
Log4OM Alpha Team
Posts: 10753
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Logging issue: WSJT > JTalertX > Log4OM

Post by G4POP »

hb9cat wrote: 30 Aug 2019, 16:48 Doug,

thanks for your feedback, I did go through the obvious restarts/reinstalls prior to sending a message to the forum.
I also did install v1.39 and enable ADIF UDP logging (turned off other methods)

The result is essentially the same: Log4OM does receive the QSO but it's not logged and a Socket exception is generated closing also the port 8081 connection.

So the problem is not related to JTalertX, it's a LOG4OM issue; any further ideas ?

Marco HB9CAT

Log:
2019-08-30 16:35:16.4280 INFO: #=qnb4cOIBeC30hWg3jtJKYnBjQLnzAJ$js0VfNyU7HKXY=: UDPSERVICE received message:<call:6>BH3SCC <gridsquare:4>OM67 <mode:3>FT8 <rst_sent:3>-11 <rst_rcvd:3>-18 <qso_date:8>20190830 <time_on:6>163513 <qso_date_off:8>20190830 <time_off:6>163513 <band:3>40m <freq:8>7.075196 <station_callsign:6>HB9CAT <my_gridsquare:6>JN46PN <tx_pwr:3>500 <eor> on UDP port 2333 (ADIF/INCOMING)
2019-08-30 16:35:16.4500 INFO: #=qiV_55X23gMSkxyDHm2CMcQ821_iC3$mYHwdzQjo0sso=: Incoming QSO from ADIF UDP <call:6>BH3SCC <gridsquare:4>OM67 <mode:3>FT8 <rst_sent:3>-11 <rst_rcvd:3>-18 <qso_date:8>20190830 <time_on:6>163513 <qso_date_off:8>20190830 <time_off:6>163513 <band:3>40m <freq:8>7.075196 <station_callsign:6>HB9CAT <my_gridsquare:6>JN46PN <tx_pwr:3>500 <eor>
2019-08-30 16:35:16.6620 ERROR: *** TCPClientManager: Socket error during Read: [SocketException] Connessione in corso interrotta forzatamente dall'host remoto
I think your confusing the TCP 8080/8081 connection between Log4om and the communicator communicator listens to log4om on one and writes to log4om on the other!

The connection between JTalert or WSJT is a UDP connection and log4om is just a listener that's why JTALERT/WSJT use a UDP port with the same port number eg. 2249 because only one port is required when a service is sending to a service that is listening without expecting data to be sent back. Bit like an up line and down line on a railwzy.

Sometimes these issues are caused because all three programs were not installed to run as an administrator (page 1 of our quick start guide or page 9 of our user msnual)

Alternatively the UDP port is used by another service, try a different port number in JTALERT/WSJT/communicator then restart all programs.

Only other advice is that some of the older releases of JTALER/WSJT sometimes sent corrupt data which caused dissconections, make sure you use the very latest releases
73 Terry G4POP
hb9cat
Advanced Class
Posts: 39
Joined: 12 May 2014, 05:57

Re: Logging issue: WSJT > JTalertX > Log4OM

Post by hb9cat »

Hello,

I'm not mixing up TCP and UDP: I am only using UDP to send the QSO from WSJT-X
Check my log extract:
- Log4Om receives the ADIF QSO via UDP ("ADIF/INCOMING")
- Log4Om does not log it
- Log4Om kills the TCP 8081 connection for some reason; I am not actively using that connection, but the "TCP connection to Log4Om" Green Led in Log4Om communicator service status turns red.

Again. all I want is to log a QSO via UDP adif, the TCP stuff is some collateral damage

I'm running the latest release of Log4Om and of WSJT-X; just to be safe I created a new blank local Log4Om log to test this

Marco HB9CAT
User avatar
G4POP
Log4OM Alpha Team
Posts: 10753
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Logging issue: WSJT > JTalertX > Log4OM

Post by G4POP »

Again. all I want is to log a QSO via UDP adif, the TCP stuff is some collateral damage
The process is wsjt sends the data via UDP to the communicator

The communicator the forwards that data by TCP to the main log4om program, if it fails the QSO is not logged!

So same questions remain for what causes the disconnect

Are all programs being run as an administrator - it is not sufficient that YOU are the administrator the program has to be run so.

If that is being done then please forward a support request to us by EMAIL do not post the log file here it contains your private information
73 Terry G4POP
hb9cat
Advanced Class
Posts: 39
Joined: 12 May 2014, 05:57

Re: Logging issue: WSJT > JTalertX > Log4OM

Post by hb9cat »

Thanks Terry,

Log4Om is indeed run as Administrator.

I may have at the least found a workaround; by the logics you're explaining, the communicator "task" received indeed the incoming adif qso and attempts to send it to Log4Om through port TCP 8081. That fails (qso not logged) and the TCP session goes down.
So I now changed on both sides the TCP port to 8082 and restarted it all.

Guess what: it works :-)

What must have happened is that some other program I installed is using TCP 8081; I will investigate to find out which program, for the time being I'm happy with the workaround.

Thanks Terry, always very responsive, and looking at the problem with 2 sets of eyes/brains always helps ;-)

Marco HB9CAT
Locked