Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
connection to jAlert lost
28-08-2020, 11:33 AM,
#1
connection to jAlert lost
I'm using Swisslog with connection trough JAlert to WSJT-X.

Since a view weeks (and SwissLog versions) after a while SwissLog do not read any further incoming information.
I tried to find out, when this situation is happened - but I have no clue.
In this situation there is no error message. I found out, that it is enough only to end SwissLog and start again.
Think it is not an issue of JAlaert.

Maybe special configuration here: I have activated all real-time online logging features.
But also there it is not activated suppressing of error messages during online logging.

Have also not found out if I could activate a kind of tracing, if messages of JAlert not 'transferred' of my Windows-10 System, or If the messages are still send to SwissLog and ignored there.

Just happened before. Have manually entered the missed QSO and watched, if new statements of JAlert accepted without restart of SwissLog - but it wasn't the case. I had to restart SwissLog.

73 Roland, DK4RH
vy 73 - DK4RH, Roland
Reply
28-08-2020, 11:51 AM,
#2
RE: connection to jAlert lost
Hi Roland,

It's very important to add exceptions to Swisslog and JT Alert in your antivirus, firewall and antimalware software. They tend to look out excessively the UDP activity blocking communication. Use default 2334 port for broadcasting in JT Alert as explained in the Swislsog help Digital Modes interfaces > Setup > WSJT-X UDP settings -- Special note for JT Alert users.Make sure you are not using port 2334 in other programs.

I suggest to disable error message during online logging. During link to WSJT-X it may interfere your operation which could be annoying and may block the logging procedure if more Log QSO request are coming.

Best 73


Take a look to Grid Tracker.
Jordi, EA3GCV
Current developer of Swisslog
Reply
28-08-2020, 12:59 PM,
#3
RE: connection to jAlert lost
Hi Jordi,

thanks for the info. Have checked, Port-2334 is used and only active on JT Alert & Swisslog.
Firewall both applications, but only for privat. Have activated also public for SwissLog. (even what makes my wonder - online-log was working before. Think those is public).

Maybe I find more...

73 Roland, DK4RH
vy 73 - DK4RH, Roland
Reply
30-08-2020, 07:45 PM, (This post was last modified: 30-08-2020, 09:22 PM by dk4rh.)
#4
RE: connection to jAlert lost
I have activated wireshark in parallel. Whit this trace it is clear, that only one application is sending on port 2334.
What I can also see there, if an application (SwissLog) is open and is receiving this information.

Just before the hanging situation was happened again. With the wireshark trace I could see, that udp-2334 data still transfered to Swisslog. But there was no reaction. Only after stopping and starting Swisslog again it was running.
Sorry, seems there is an issue in Swisslog.

Maybe the details are helpful. Hope I can attach the files to this statement...

In Word-Document what can be seen in Swisslog, what was happened in WSJT-X and the wireshark trace.

Problem is, that the QSO(s)  are not logged and it is a little bit hard to do those afterwards. Currently I am checking the reaction of SwissLog for each QSO which should be logged - So I have only to enter those one.

Hope those all is helpful to find the issue

73 Roland, DK4RH

Additional info. After recap of missing QSOs I found out, that 3 are missed. So it must be happened a little bit before.
Just jet (UTC 18:44) same issue came up. See 200830b-SwissLogHangig.JPG
Here I changed to try answer a call (to CP9JPG) to another(EA2DXY), than SP9JP begun to answer. Later on I changed my answer to SP9JP.
Seems also in the first hanging it was an equal situation.


Attached Files Thumbnail(s)
   

.docx   200830-Swissconnection-hanging.docx (Size: 272,34 KB / Downloads: 4)
.zip   200830-Swissconnection-hanging.zip (Size: 1,33 MB / Downloads: 1)
vy 73 - DK4RH, Roland
Reply
31-08-2020, 12:06 AM, (This post was last modified: 31-08-2020, 08:10 AM by EA3GCV.)
#5
RE: connection to jAlert lost
Hi Roland,

Once you are sure you have exceptions added to Swisslog, WSJT-X and JT Alert in your antivirus and firewall, run ALL these programs as administrator. This is the best way to ensure a good communication among all programs. 

Take care about Wireshark... in order to monitor localhost activity (127.0.0.1) you have to install NPCap. I have experienced some problems resulting in no communication between some applications. After uninstalingl NPCap all worked well. If issue remains after running all programs as administrator, try uninstalling NPCap and test. I also have wireshark but I only install NPCap if I need to monitor specific traces but afterwards I uninstall it for the above reason.

I use JTDX daily and many users with no error reports at all. I have also many users using JT Alert with no error reports as well. Swisslog only receives data in the selected UDP port. It doesn't matter whether it receives data directly from WSJT-X or by the forwading UDP port of JT Alert. I added an option in UDP settings of Swisslog to broadcast data to other software (such Grid tracker). Maybe you can try to change the setup to WSJT-X > Swisslog > JT Alert. Although I think JT Alert needs to send data back to WSJT-X so this configuration won't work 100%.

However and according to my experience I guess NPCap could cause all these issues (if you still have them after running as administrator). I turned crazy until I found out this! I didn't get communication between PstRotator and Swisslog and after uninstalling NPCap all worked well again.

If still in trouble after trying all this, please send me screenshots of all your WSJT-X, JT-Alert and Swisslog UPD settings. Maybe we should arrange a Teamviewer session.

Best 73
Jordi, EA3GCV
Current developer of Swisslog
Reply
31-08-2020, 12:26 PM,
#6
RE: connection to jAlert lost
Hi Jordi,

as first step I try with uninstalling NCap. If possible, I will not have to run applications with administrator rights.

Before I uninstall NCap, I had again this situation. Watching more in details, what is happened in SwissLog got for me the awareness, that in those hanging situation SwissLog is searching for the CallSign. In a normal situation SwissLog show not found (Rufzeichen nicht gefunden) or Callsign found in HAMQTH (Rufzeichen gefunden in HAMQTH).
Even during searching for the CallSign RST-S and RST-R present 599. After finding or not finding it change to 0.
In the hanging status it stay on 599.
Have taken a look in the created pics before, there it was the same.
But I am not able to reproduce. Have enter those callsign manual in WSJT-X and let search Swisslog - those worked.

Those symptom seems for my that it is not an issue of the IP-Connection.
But I still check, and will run in administrator mode if it is still happened.

73 Roland, DK4RH


Attached Files Thumbnail(s)
   
vy 73 - DK4RH, Roland
Reply
01-09-2020, 11:24 PM,
#7
RE: connection to jAlert lost
Was just happened again (with de-installed Ncap, but not admin-rights).
Will change tomorrow by using admin-rights.

Situation was again where SwissLog check the internet-database (HAMQTH) and stay with 599.
Could it be, that there is no timeout programmed for internet database?
Maybe special here at my site: I must have sporadic lost of data of my DSL-Line. Maybe an answer of HAMQTH do not reach my computer / Swisslog.

Makes my wonder, that it is always the same step of hanging point...

As written I will go and test with admin-rights.

73 Roland, DK4RH


Attached Files Thumbnail(s)
   
vy 73 - DK4RH, Roland
Reply
02-09-2020, 02:28 AM,
#8
RE: connection to jAlert lost
Hello Roland,

If you have don't have a stable DSL connection probably this is the source of the issue. You can change the read timeout from Callbook databases in Options / CD-Callbook / Internet databases > Timeout (seconds). By default is 5 seconds. Try to set a lower value and let me know if this works for you.

Best 73
Jordi, EA3GCV
Current developer of Swisslog
Reply
05-09-2020, 12:57 AM,
#9
RE: connection to jAlert lost
Hi Jordi,

sorry, seems not to work. Have reduced up to 1 second. Situation is quite seldom, has taken a while.

Additional findings:
- In this situation, in the window of SwissLog to enter a new QSO the TAB-Key is not working
- If I close the QSO window, open again still TAB is not working. SwissLog even do not search for the CallSign if I enter a CallSign and go to another field with mouse
- When I close the Swisslog in those situation, a beep is coming up like an error - but without an error popup.

Have again activated a trace with filter to IP-Adress of hamqth.com. The session is encrypted, but the sequence of sent and received packets are the same like a good request. Seems there is nothing missed.
Have than installed ncap again, traced on both interfaces (loopback and network) with filter 'ip.addr == 94.23.250.107 || udp.port == 2334'  . I am not a specialist in analysis, but even comparing normal situation and hanging situation cant find an issue.

73 Roland, DK4RH
vy 73 - DK4RH, Roland
Reply
05-09-2020, 12:49 PM,
#10
RE: connection to jAlert lost
Hello Roland,

This case is really strange... Have tried to run Swislsog, WSJT-X and JT Alert as administrator? You don't have to worry to give administrator rights to a known software like these ones.

If you still have the same issues running all as admin, please disable HAMQTH reading and try. we have to found out whch is causing this but the TAB key not working is very strange.

Please I know I insist a lot but make sure you have added exceptions to WSJT-X, JT Alert and Swisslog in your antivirus, firewall and all other antispyware software.

I would need to do a remote session with you via Teamviewer to check carefully what may happen but this is a very strange issue.

Best 73
Jordi, EA3GCV
Current developer of Swisslog
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)