Debugging pi-star for err=111 and verbose log output

General support for the Pi-Star System
Post Reply
w7brs
Posts: 3
Joined: Tue Nov 06, 2018 5:53 am

Debugging pi-star for err=111 and verbose log output

Post by w7brs » Tue Nov 06, 2018 7:09 am

I'm getting this error trying to Link to a reflector through the Pi-Star (ZumSpot RPI Kit) via TH-D74A

This is the error in the log /var/log/pi-star/ircDDBGateway-2018-08-11.log is:

Cannot connect the TCP client socket, err=111

Is there a list of error codes? To which host is the pi-star trying to establish a TCP/IP socket connection? and why?

What log entry is supposed to be emitted when a successful Link to Reflector is attempted?

Also, is there a debug level setting to make the pi-star very verbose in logging? Which stanza of the /etc/mmdvmhost file?

Version info:

ZumSpot:
$ uname -a
Linux pi-star 4.9.35+ #1014 Fri Jun 30 14:34:49 BST 2017 armv6l GNU/Linux

More version info:

pi-star version 1.4.16
dashboard 20181019
zumspot FW 1.3.3

Point me to documents if it would be easier. Thanks.

-jeff
W7BRS

User avatar
KE0FHS
Posts: 312
Joined: Wed Apr 11, 2018 8:40 pm
Location: Colorado, USA
Contact:

Re: Debugging pi-star for err=111 and verbose log output

Post by KE0FHS » Tue Nov 06, 2018 3:48 pm

Error 111 is connection refused.
Does this happen with attempts to connect to any reflector?
On your dashboard page, what is the network status for D-STAR, green or red?

Also, your firmware is quite out of date. Suggest updating. See: https://amateurradionotes.com/pi-star-n ... otflashetc
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
http://pi-star.hamnotes.com

w7brs
Posts: 3
Joined: Tue Nov 06, 2018 5:53 am

Re: Debugging pi-star for err=111 and verbose log output

Post by w7brs » Thu Nov 08, 2018 2:39 am

Occurs when trying to link to any reflector.

Network status of D-STAR is Green.

User avatar
KE0FHS
Posts: 312
Joined: Wed Apr 11, 2018 8:40 pm
Location: Colorado, USA
Contact:

Re: Debugging pi-star for err=111 and verbose log output

Post by KE0FHS » Thu Nov 08, 2018 2:24 pm

Not much info to go on, but again, recommend a firmware update. There have been at least nine firmware releases since 1.3.3. Using Pi-Star, doing a firmware update is trivially easy.

Also, double check your radio setup. You should use D-STAR Repeater (DR) or Duplex mode: set up RPT1, RPT2, and a zero offset (either +/−0.000).
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
http://pi-star.hamnotes.com

w7brs
Posts: 3
Joined: Tue Nov 06, 2018 5:53 am

Re: Debugging pi-star for err=111 and verbose log output

Post by w7brs » Thu Nov 08, 2018 5:32 pm

Upgraded ZumSpot RPI Kit Fw to 1.4.12

Still getting error when trying to Link to a reflector,

M: 2018-08-12 18:53:33: Link command from W7BRS B to REF023 C issued via UR Call by W7BRS
M: 2018-08-12 18:53:34: USER: W7BRS W7BRS B W7BRS G 64.91.104.188
M: 2018-08-12 18:53:35: USER: W7BRS W7BRS B W7BRS G 64.91.104.188
[...]

M: 2018-08-12 18:53:57: USER: W7BRS W7BRS B W7BRS G 64.91.104.188
M: 2018-08-12 18:53:57: USER: W7BRS W7BRS B W7BRS G 64.91.104.188

[...]
M: 2018-08-12 18:55:03: D-Plus link to REF023 C has failed to connect


Is there a flag or debug option in the pi-star software that can cause the software to emit more detail in the log?

I used off-target utilities to sniff the packets to and from the Zum and no traffic occurs other than the

This is the only remarkable traffic that occurs between the pi-star ZumSpot hardware and the broader net:
30 or so records like this:

(the IP addr of the interface is 192.168.0.182)

12 1.755696 192.168.0.182 239.255.255.250 SSDP 174 M-SEARCH * HTTP/1.1

Then periodically these two packets:

41 151.553997 192.168.0.182 192.168.0.255 BROWSER 262 Local Master Announcement PI-STAR, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Master Browser, DFS server
42 151.553999 192.168.0.182 192.168.0.255 BROWSER 250 Domain/Workgroup Announcement WORKGROUP, NT Workstation, Domain Enum

User avatar
KE0FHS
Posts: 312
Joined: Wed Apr 11, 2018 8:40 pm
Location: Colorado, USA
Contact:

Re: Debugging pi-star for err=111 and verbose log output

Post by KE0FHS » Thu Nov 08, 2018 6:04 pm

Just FYI: I had no problem linking to REF023 C just now using a Kenwood TH-D74A with a ZUMspot mounted on a RPi (Pi-Star 3.4.16, Dashboard 20181107, firmware 1.4.12.

Have you tried a DCS or XRF reflector? I've heard that sometimes people can get blocked on DPLUS, which is a proprietary system. I seem to remember that can happen if multiple connections are attempted simultaneously with the same callsign, or something like that.
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
http://pi-star.hamnotes.com

ct1dvm
Posts: 117
Joined: Thu Apr 19, 2018 6:34 am

Re: Debugging pi-star for err=111 and verbose log output

Post by ct1dvm » Fri Nov 09, 2018 6:39 am

w7brs wrote:
Thu Nov 08, 2018 5:32 pm
Upgraded ZumSpot RPI Kit Fw to 1.4.12

Still getting error when trying to Link to a reflector,

M: 2018-08-12 18:53:33: Link command from W7BRS B to REF023 C issued via UR Call by W7BRS
M: 2018-08-12 18:53:34: USER: W7BRS W7BRS B W7BRS G 64.91.104.188
M: 2018-08-12 18:53:35: USER: W7BRS W7BRS B W7BRS G 64.91.104.188
[...]

M: 2018-08-12 18:53:57: USER: W7BRS W7BRS B W7BRS G 64.91.104.188
M: 2018-08-12 18:53:57: USER: W7BRS W7BRS B W7BRS G 64.91.104.188

[...]
M: 2018-08-12 18:55:03: D-Plus link to REF023 C has failed to connect


Is there a flag or debug option in the pi-star software that can cause the software to emit more detail in the log?

I used off-target utilities to sniff the packets to and from the Zum and no traffic occurs other than the

This is the only remarkable traffic that occurs between the pi-star ZumSpot hardware and the broader net:
30 or so records like this:

(the IP addr of the interface is 192.168.0.182)

12 1.755696 192.168.0.182 239.255.255.250 SSDP 174 M-SEARCH * HTTP/1.1

Then periodically these two packets:

41 151.553997 192.168.0.182 192.168.0.255 BROWSER 262 Local Master Announcement PI-STAR, Workstation, Server, Print Queue Server, Xenix Server, NT Workstation, NT Server, Master Browser, DFS server
42 151.553999 192.168.0.182 192.168.0.255 BROWSER 250 Domain/Workgroup Announcement WORKGROUP, NT Workstation, Domain Enum
You are not showing all the relevant verbose, especially the RO or RW dplus access that usually shows in the log ?

You only have one terminal ;

[W7BRS ] [WA7HJR B]

So that looks like what you used above. It is possible REf023 is not synced or has other issue. Does any other dplus reflector link ?

Post Reply