la5nta / pat

A cross-platform Winlink client written in Go
https://getpat.io
MIT License
488 stars 86 forks source link

Pactor: Exchange failed: unexpected EOF #248

Closed K7LRK closed 3 years ago

K7LRK commented 3 years ago

Pactor seems to be working -- my script uses these commands:

echo Attempting a connection with using pactor pat connect pactor:///

The terminal displays:

Attempting a connection with K7NHV using pactor 2021/04/06 13:13:37 Unable to get frequency from rig network: dial tcp [::1]:4532: connect: connection refused. 2021/04/06 13:13:40 Connecting to K7NHV (pactor)... 2021/04/06 13:13:42 Connected to K7NHV (pactor) 2021/04/06 13:14:27 Exchange failed: unexpected EOF

the test email was created using the web-GUI (had to add .txt to get this interface to accept the attachment)

WBWNQQAXPLIT.b2f.txt

BTW: I wanted to use the pat-users group but can not find a "new message" option. So 2nd issue is the google group site not allowing new messages.

73, Clark K7LRK

harenber commented 3 years ago

The "unexpected EOF" usually means, that the underlying transport layer (PACTOR in this case) has received a disconnect event (bad conds?).

To use Google Groups I suggest to just read the documentation: https://support.google.com/groups/answer/1046523

73s Torsten DL1THM

K7LRK commented 3 years ago

Torsten:

Thank you for your response. I appreciate knowing that the transport layer has received a disconnect.

Unfortunately, this does not help me troubleshoot and correct the problem. What does "bad conds?” Mean?

I believe I have the correct configuration:

+=+=+=+= "pactor": { "path": "/dev/PACTOR", "baudrate": 829440, "rig": "", "custom_init_script": "" }, +=+=+=+=

I am not using rigctl so the command I am using to connect is:

pat connect pactor:///<call sign>

This generates the following:

2021/04/07 10:48:02 Unable to get frequency from rig network: dial tcp [::1]:4532: connect: connection refused. 2021/04/07 10:48:05 Connecting to K7IF (pactor)... 2021/04/07 10:48:07 Connected to K7IF (pactor) 2021/04/07 10:48:51 Exchange failed: unexpected EOF pat: no process found

I do not know what “pat: no process found” means

The eventlog.json file contains:

^%^%^%^%^%^% {"local_addr":"K7LRK","log_time":"2021-04-07T10:48:07.68516945-07:00","network":"pactor","operation":"connect pactor:///K7IF", "remote_addr":"K7IF","success":true,"what":"connect"} {"auxiliary_addresses":[],"end":1617817731,"error":"unexpected EOF","local_addr":"K7LRK","local_locator":"CN88NK", "log_time":"2021-04-07T10:48:51.813932593-07:00","master":false,"mycall":"K7LRK","network":"pactor", "received":null,"remote_addr":"K7IF","remote_fw":null,"remote_sid":"","sent":null,"start":1617817687, "success":false,"targetcall":"K7IF","what":"exchange"} ^%^%^%^%^%^%

I am able to sent and receive emails using telnet.
What else can I do to discover and solve the problem?
Is there some other log file that would be more informative?

73 Clark

P.S. I have read the google groups documentation — it states -=-=-=-=-=-= Start a new conversation Start a group discussion about a topic you’re interested in. Sign in to Google Groups https://groups.google.com/. Click the name of a group. At the top left, click New conversation. Enter your message. Click Post message. -=-=-=-=-=-=

The problem I am having is that the interface does not have a “New conversation” button

martinhpedersen commented 3 years ago

@K7LRK - What Torsten means by "bad conds" is poor radio conditions, aka weak signal and/or a poor signal-to-noise-ratio.

Torsten seems to think that this problem is not with Pat, but rather an issue with your radio/modem. The fact that your connection is terminated after quite some time of inactivity led me to believe the same thing. My advice would be to post a video at the pat-users community forum of what's going on (including audio from your rig). It should provide enough information for people to help you out 🙂

Since we're not seing any evidence suggesting that this is a bug in Pat, I'm closing this issue for now.

K7LRK commented 3 years ago

Yes, I believe this is not a PAT issue.

Thanks for the followup

Clark