Master maintenance loop started


Jürgen Clemenz
 

Hello
I always get this message from HBlink:
Master maintenance loop started

My Log

root@v293571:/home/dh9yap/HBlink# ./hblink.py
DEBUG 2018-08-06 18:02:06,083 Logging system started, anything from here on gets logged
INFO 2018-08-06 18:02:06,083 Registration ACL file found, importing entries. This will take about 1.5 seconds per 1 million IDs
INFO 2018-08-06 18:02:06,084 Registration ACL loaded: action "DENY" for 1 registration IDs
INFO 2018-08-06 18:02:06,084 HBlink TCP reporting server configured
DEBUG 2018-08-06 18:02:06,084 Periodic reporting loop started
INFO 2018-08-06 18:02:06,085 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2018-08-06 18:02:06,085 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:06,085 MASTER instance created: MASTER-1, <__main__.HBSYSTEM instance at 0x7ff46a9aa3f8>
DEBUG 2018-08-06 18:02:11,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:16,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:21,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:26,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:31,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:36,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:41,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:46,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:51,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:56,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:01,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:06,088 Periodic reporting loop started
DEBUG 2018-08-06 18:03:06,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:11,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:16,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:21,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:26,090 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:31,087 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:36,090 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:41,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:46,090 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:51,089 (MASTER-1) Master maintenance loop started

I would be happy if I got an answer

Juergen DH9YAP


Steve N4IRS
 

In hblink.cfg
Change:
LOG_LEVEL: DEBUG
To:
LOG_LEVEL: INFO

restart.

73, Steve N4IRS


On 8/6/2018 12:14 PM, Jürgen Clemenz wrote:
Hello
I always get this message from HBlink:
Master maintenance loop started

My Log

root@v293571:/home/dh9yap/HBlink# ./hblink.py
DEBUG 2018-08-06 18:02:06,083 Logging system started, anything from here on gets logged
INFO 2018-08-06 18:02:06,083 Registration ACL file found, importing entries. This will take about 1.5 seconds per 1 million IDs
INFO 2018-08-06 18:02:06,084 Registration ACL loaded: action "DENY" for 1 registration IDs
INFO 2018-08-06 18:02:06,084 HBlink TCP reporting server configured
DEBUG 2018-08-06 18:02:06,084 Periodic reporting loop started
INFO 2018-08-06 18:02:06,085 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2018-08-06 18:02:06,085 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:06,085 MASTER instance created: MASTER-1, <__main__.HBSYSTEM instance at 0x7ff46a9aa3f8>
DEBUG 2018-08-06 18:02:11,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:16,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:21,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:26,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:31,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:36,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:41,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:46,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:51,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:02:56,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:01,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:06,088 Periodic reporting loop started
DEBUG 2018-08-06 18:03:06,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:11,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:16,089 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:21,088 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:26,090 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:31,087 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:36,090 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:41,086 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:46,090 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-06 18:03:51,089 (MASTER-1) Master maintenance loop started

I would be happy if I got an answer

Juergen DH9YAP


Jürgen Clemenz
 

On Mon, Aug 6, 2018 at 09:17 AM, Steve N4IRS wrote:
LOG_LEVEL: INFO
Thank you for your prompt reply.
After the change the master is running.

I get with Pi-Star but no connection!
Log from Pi Star:

: 2018-08-09 14:36:21.598 MMDVMHost-20180802_Pi-Star exited on receipt of SIGTERM
I: 2018-08-09 14:36:28.061 This software is for use on amateur radio networks only,
I: 2018-08-09 14:36:28.061 it is to be used for educational purposes only. Its use on
I: 2018-08-09 14:36:28.061 commercial networks is strictly prohibited.
I: 2018-08-09 14:36:28.062 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2018-08-09 14:36:28.062 MMDVMHost-20180802_Pi-Star is starting
M: 2018-08-09 14:36:28.062 Built 22:50:25 Aug  2 2018 (GitID #69f1a21)
I: 2018-08-09 14:36:28.062 General Parameters
I: 2018-08-09 14:36:28.062     Callsign: DH9YAP
I: 2018-08-09 14:36:28.062     Id: 263441224
I: 2018-08-09 14:36:28.062     Duplex: no
I: 2018-08-09 14:36:28.062     Timeout: 240s
I: 2018-08-09 14:36:28.062     D-Star: disabled
I: 2018-08-09 14:36:28.062     DMR: enabled
I: 2018-08-09 14:36:28.062     YSF: disabled
I: 2018-08-09 14:36:28.063     P25: disabled
I: 2018-08-09 14:36:28.063     NXDN: disabled
I: 2018-08-09 14:36:28.063     POCSAG: disabled
I: 2018-08-09 14:36:28.063 Modem Parameters
I: 2018-08-09 14:36:28.063     Port: /dev/ttyAMA0
I: 2018-08-09 14:36:28.063     Protocol: uart
I: 2018-08-09 14:36:28.063     RX Invert: no
I: 2018-08-09 14:36:28.063     TX Invert: yes
I: 2018-08-09 14:36:28.063     PTT Invert: no
I: 2018-08-09 14:36:28.063     TX Delay: 100ms
I: 2018-08-09 14:36:28.063     RX Offset: 0Hz
I: 2018-08-09 14:36:28.063     TX Offset: 0Hz
I: 2018-08-09 14:36:28.063     RX DC Offset: 0
I: 2018-08-09 14:36:28.063     TX DC Offset: 0
I: 2018-08-09 14:36:28.063     RF Level: 100.0%
I: 2018-08-09 14:36:28.063     DMR Delay: 0 (0.0ms)
I: 2018-08-09 14:36:28.063     RX Level: 50.0%
I: 2018-08-09 14:36:28.063     CW Id TX Level: 50.0%
I: 2018-08-09 14:36:28.063     D-Star TX Level: 50.0%
I: 2018-08-09 14:36:28.064     DMR TX Level: 50.0%
I: 2018-08-09 14:36:28.064     YSF TX Level: 50.0%
I: 2018-08-09 14:36:28.064     P25 TX Level: 50.0%
I: 2018-08-09 14:36:28.064     NXDN TX Level: 50.0%
I: 2018-08-09 14:36:28.064     POCSAG TX Level: 50.0%
I: 2018-08-09 14:36:28.064     RX Frequency: 433612500Hz (433612500Hz)
I: 2018-08-09 14:36:28.064     TX Frequency: 433612500Hz (433612500Hz)
M: 2018-08-09 14:36:28.065 Opening the MMDVM
I: 2018-08-09 14:36:30.080 MMDVM protocol version: 1, description: MMDVM_HS_Dual_Hat-v1.4.6 20180720 14.7456MHz dual ADF7021 FW by CA6JAU GitID #10c725c
I: 2018-08-09 14:36:30.103 Display Parameters
I: 2018-08-09 14:36:30.103     Type: None
W: 2018-08-09 14:36:30.103 No valid display found, disabling
I: 2018-08-09 14:36:30.103 DMR Network Parameters
I: 2018-08-09 14:36:30.104     Address: 213.202.228.66
I: 2018-08-09 14:36:30.104     Port: 54000
I: 2018-08-09 14:36:30.104     Local: random
I: 2018-08-09 14:36:30.104     Jitter: 360ms
I: 2018-08-09 14:36:30.104     Slot 1: enabled
I: 2018-08-09 14:36:30.104     Slot 2: enabled
I: 2018-08-09 14:36:30.104     Mode Hang: 20s
I: 2018-08-09 14:36:30.104 Info Parameters
I: 2018-08-09 14:36:30.104     Callsign: DH9YAP
I: 2018-08-09 14:36:30.104     RX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     TX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     Power: 1W
I: 2018-08-09 14:36:30.104     Latitude: 51.588268deg N
I: 2018-08-09 14:36:30.104     Longitude: 7.145595deg E
I: 2018-08-09 14:36:30.104     Height: 0m
I: 2018-08-09 14:36:30.104     Location: "Herten, JO31NO"
I: 2018-08-09 14:36:30.104     Description: "Germany"
I: 2018-08-09 14:36:30.104     URL: "http://www.funknetz.nrw"
M: 2018-08-09 14:36:30.104 DMR, Opening DMR Network
I: 2018-08-09 14:36:30.105 RSSI
I: 2018-08-09 14:36:30.105     Mapping File: /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 Loaded 14 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 DMR Id Lookups
I: 2018-08-09 14:36:30.107     File: /usr/local/etc/DMRIds.dat
I: 2018-08-09 14:36:30.107     Reload: 24 hours
I: 2018-08-09 14:36:32.132 Loaded 104513 Ids to the DMR callsign lookup table
I: 2018-08-09 14:36:32.132 DMR RF Parameters
I: 2018-08-09 14:36:32.132     Id: 263441224
I: 2018-08-09 14:36:32.132     Color Code: 1
I: 2018-08-09 14:36:32.132     Self Only: yes
I: 2018-08-09 14:36:32.132     Embedded LC Only: no
I: 2018-08-09 14:36:32.132     Dump Talker Alias Data: yes
I: 2018-08-09 14:36:32.132     Prefixes: 0
I: 2018-08-09 14:36:32.132     Call Hang: 3s
I: 2018-08-09 14:36:32.132     TX Hang: 4s
I: 2018-08-09 14:36:32.132     Mode Hang: 20s
M: 2018-08-09 14:36:32.133 MMDVMHost-20180802_Pi-Star is running
I: 2018-08-09 14:36:32.138 Started the DMR Id lookup reload thread
E: 2018-08-09 14:36:42.149 Error returned from sendto, err: 1
E: 2018-08-09 14:36:42.149 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:42.150 DMR, Opening DMR Network
E: 2018-08-09 14:36:52.176 Error returned from sendto, err: 1
E: 2018-08-09 14:36:52.177 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:52.177 DMR, Opening DMR Network
E: 2018-08-09 14:37:02.210 Error returned from sendto, err: 1
E: 2018-08-09 14:37:02.211 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:02.211 DMR, Opening DMR Network
E: 2018-08-09 14:37:12.229 Error returned from sendto, err: 1
E: 2018-08-09 14:37:12.229 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:12.229 DMR, Opening DMR Network
M: 2018-08-09 14:37:15.639 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
M: 2018-08-09 14:37:17.677 DMR Slot 2, RF voice transmission lost, 0.7 seconds, BER: 13.2%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:22.258 Error returned from sendto, err: 1
E: 2018-08-09 14:37:22.258 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:22.258 DMR, Opening DMR Network
M: 2018-08-09 14:37:32.175 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
E: 2018-08-09 14:37:32.277 Error returned from sendto, err: 1
E: 2018-08-09 14:37:32.277 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:32.277 DMR, Opening DMR Network
M: 2018-08-09 14:37:37.811 DMR Slot 2, RF voice transmission lost, 5.5 seconds, BER: 5.9%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:42.294 Error returned from sendto, err: 1
E: 2018-08-09 14:37:42.294 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:42.295 DMR, Opening DMR Network
E: 2018-08-09 14:37:52.319 Error returned from sendto, err: 1
E: 2018-08-09 14:37:52.320 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:52.320 DMR, Opening DMR Network
E: 2018-08-09 14:38:02.349 Error returned from sendto, err: 1
E: 2018-08-09 14:38:02.349 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:02.349 DMR, Opening DMR Network
E: 2018-08-09 14:38:12.366 Error returned from sendto, err: 1
E: 2018-08-09 14:38:12.366 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:12.367 DMR, Opening DMR Network
E: 2018-08-09 14:38:22.397 Error returned from sendto, err: 1
E: 2018-08-09 14:38:22.397 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:22.397 DMR, Opening DMR Network


Steve N4IRS
 

Are you saying that after the log change, Pi-Star can no longer connect?

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Jürgen Clemenz <j.clemenz@...>
Sent: Thursday, August 9, 2018 10:48:18 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Master maintenance loop started
 
On Mon, Aug 6, 2018 at 09:17 AM, Steve N4IRS wrote:
LOG_LEVEL: INFO
Thank you for your prompt reply.
After the change the master is running.

I get with Pi-Star but no connection!
Log from Pi Star:

: 2018-08-09 14:36:21.598 MMDVMHost-20180802_Pi-Star exited on receipt of SIGTERM
I: 2018-08-09 14:36:28.061 This software is for use on amateur radio networks only,
I: 2018-08-09 14:36:28.061 it is to be used for educational purposes only. Its use on
I: 2018-08-09 14:36:28.061 commercial networks is strictly prohibited.
I: 2018-08-09 14:36:28.062 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2018-08-09 14:36:28.062 MMDVMHost-20180802_Pi-Star is starting
M: 2018-08-09 14:36:28.062 Built 22:50:25 Aug  2 2018 (GitID #69f1a21)
I: 2018-08-09 14:36:28.062 General Parameters
I: 2018-08-09 14:36:28.062     Callsign: DH9YAP
I: 2018-08-09 14:36:28.062     Id: 263441224
I: 2018-08-09 14:36:28.062     Duplex: no
I: 2018-08-09 14:36:28.062     Timeout: 240s
I: 2018-08-09 14:36:28.062     D-Star: disabled
I: 2018-08-09 14:36:28.062     DMR: enabled
I: 2018-08-09 14:36:28.062     YSF: disabled
I: 2018-08-09 14:36:28.063     P25: disabled
I: 2018-08-09 14:36:28.063     NXDN: disabled
I: 2018-08-09 14:36:28.063     POCSAG: disabled
I: 2018-08-09 14:36:28.063 Modem Parameters
I: 2018-08-09 14:36:28.063     Port: /dev/ttyAMA0
I: 2018-08-09 14:36:28.063     Protocol: uart
I: 2018-08-09 14:36:28.063     RX Invert: no
I: 2018-08-09 14:36:28.063     TX Invert: yes
I: 2018-08-09 14:36:28.063     PTT Invert: no
I: 2018-08-09 14:36:28.063     TX Delay: 100ms
I: 2018-08-09 14:36:28.063     RX Offset: 0Hz
I: 2018-08-09 14:36:28.063     TX Offset: 0Hz
I: 2018-08-09 14:36:28.063     RX DC Offset: 0
I: 2018-08-09 14:36:28.063     TX DC Offset: 0
I: 2018-08-09 14:36:28.063     RF Level: 100.0%
I: 2018-08-09 14:36:28.063     DMR Delay: 0 (0.0ms)
I: 2018-08-09 14:36:28.063     RX Level: 50.0%
I: 2018-08-09 14:36:28.063     CW Id TX Level: 50.0%
I: 2018-08-09 14:36:28.063     D-Star TX Level: 50.0%
I: 2018-08-09 14:36:28.064     DMR TX Level: 50.0%
I: 2018-08-09 14:36:28.064     YSF TX Level: 50.0%
I: 2018-08-09 14:36:28.064     P25 TX Level: 50.0%
I: 2018-08-09 14:36:28.064     NXDN TX Level: 50.0%
I: 2018-08-09 14:36:28.064     POCSAG TX Level: 50.0%
I: 2018-08-09 14:36:28.064     RX Frequency: 433612500Hz (433612500Hz)
I: 2018-08-09 14:36:28.064     TX Frequency: 433612500Hz (433612500Hz)
M: 2018-08-09 14:36:28.065 Opening the MMDVM
I: 2018-08-09 14:36:30.080 MMDVM protocol version: 1, description: MMDVM_HS_Dual_Hat-v1.4.6 20180720 14.7456MHz dual ADF7021 FW by CA6JAU GitID #10c725c
I: 2018-08-09 14:36:30.103 Display Parameters
I: 2018-08-09 14:36:30.103     Type: None
W: 2018-08-09 14:36:30.103 No valid display found, disabling
I: 2018-08-09 14:36:30.103 DMR Network Parameters
I: 2018-08-09 14:36:30.104     Address: 213.202.228.66
I: 2018-08-09 14:36:30.104     Port: 54000
I: 2018-08-09 14:36:30.104     Local: random
I: 2018-08-09 14:36:30.104     Jitter: 360ms
I: 2018-08-09 14:36:30.104     Slot 1: enabled
I: 2018-08-09 14:36:30.104     Slot 2: enabled
I: 2018-08-09 14:36:30.104     Mode Hang: 20s
I: 2018-08-09 14:36:30.104 Info Parameters
I: 2018-08-09 14:36:30.104     Callsign: DH9YAP
I: 2018-08-09 14:36:30.104     RX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     TX Frequency: 433612500Hz
I: 2018-08-09 14:36:30.104     Power: 1W
I: 2018-08-09 14:36:30.104     Latitude: 51.588268deg N
I: 2018-08-09 14:36:30.104     Longitude: 7.145595deg E
I: 2018-08-09 14:36:30.104     Height: 0m
I: 2018-08-09 14:36:30.104     Location: "Herten, JO31NO"
I: 2018-08-09 14:36:30.104     Description: "Germany"
I: 2018-08-09 14:36:30.104     URL: "http://www.funknetz.nrw"
M: 2018-08-09 14:36:30.104 DMR, Opening DMR Network
I: 2018-08-09 14:36:30.105 RSSI
I: 2018-08-09 14:36:30.105     Mapping File: /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 Loaded 14 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2018-08-09 14:36:30.107 DMR Id Lookups
I: 2018-08-09 14:36:30.107     File: /usr/local/etc/DMRIds.dat
I: 2018-08-09 14:36:30.107     Reload: 24 hours
I: 2018-08-09 14:36:32.132 Loaded 104513 Ids to the DMR callsign lookup table
I: 2018-08-09 14:36:32.132 DMR RF Parameters
I: 2018-08-09 14:36:32.132     Id: 263441224
I: 2018-08-09 14:36:32.132     Color Code: 1
I: 2018-08-09 14:36:32.132     Self Only: yes
I: 2018-08-09 14:36:32.132     Embedded LC Only: no
I: 2018-08-09 14:36:32.132     Dump Talker Alias Data: yes
I: 2018-08-09 14:36:32.132     Prefixes: 0
I: 2018-08-09 14:36:32.132     Call Hang: 3s
I: 2018-08-09 14:36:32.132     TX Hang: 4s
I: 2018-08-09 14:36:32.132     Mode Hang: 20s
M: 2018-08-09 14:36:32.133 MMDVMHost-20180802_Pi-Star is running
I: 2018-08-09 14:36:32.138 Started the DMR Id lookup reload thread
E: 2018-08-09 14:36:42.149 Error returned from sendto, err: 1
E: 2018-08-09 14:36:42.149 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:42.150 DMR, Opening DMR Network
E: 2018-08-09 14:36:52.176 Error returned from sendto, err: 1
E: 2018-08-09 14:36:52.177 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:36:52.177 DMR, Opening DMR Network
E: 2018-08-09 14:37:02.210 Error returned from sendto, err: 1
E: 2018-08-09 14:37:02.211 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:02.211 DMR, Opening DMR Network
E: 2018-08-09 14:37:12.229 Error returned from sendto, err: 1
E: 2018-08-09 14:37:12.229 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:12.229 DMR, Opening DMR Network
M: 2018-08-09 14:37:15.639 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
M: 2018-08-09 14:37:17.677 DMR Slot 2, RF voice transmission lost, 0.7 seconds, BER: 13.2%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:22.258 Error returned from sendto, err: 1
E: 2018-08-09 14:37:22.258 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:22.258 DMR, Opening DMR Network
M: 2018-08-09 14:37:32.175 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
E: 2018-08-09 14:37:32.277 Error returned from sendto, err: 1
E: 2018-08-09 14:37:32.277 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:32.277 DMR, Opening DMR Network
M: 2018-08-09 14:37:37.811 DMR Slot 2, RF voice transmission lost, 5.5 seconds, BER: 5.9%, RSSI: -47/-47/-47 dBm
E: 2018-08-09 14:37:42.294 Error returned from sendto, err: 1
E: 2018-08-09 14:37:42.294 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:42.295 DMR, Opening DMR Network
E: 2018-08-09 14:37:52.319 Error returned from sendto, err: 1
E: 2018-08-09 14:37:52.320 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:37:52.320 DMR, Opening DMR Network
E: 2018-08-09 14:38:02.349 Error returned from sendto, err: 1
E: 2018-08-09 14:38:02.349 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:02.349 DMR, Opening DMR Network
E: 2018-08-09 14:38:12.366 Error returned from sendto, err: 1
E: 2018-08-09 14:38:12.366 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:12.367 DMR, Opening DMR Network
E: 2018-08-09 14:38:22.397 Error returned from sendto, err: 1
E: 2018-08-09 14:38:22.397 DMR, Socket has failed when writing data to the master, retrying connection
M: 2018-08-09 14:38:22.397 DMR, Opening DMR Network


Jürgen Clemenz
 

Pi star could not get in touch before. I thought it was due to debug message.
I have now taken another port that is open on my Ubuntu server.
It does not work !

73 de Jürgen :-)


Jürgen Clemenz
 

Maybe I understand something wrong.
I have here 2 raspberry pi Zero with one MMDVM duplex board (hotspot).
Would like the two private networks.
Later, there are more hotspots to come and they should all be connected.
73 Jürgen


Jürgen Clemenz
 

Maybe you can try to connect my master.
Address: 213.202.228.66
Port 5400
Password: funknetz.nrw


Jürgen Clemenz
 

here you have to doh then see the incoming connection !?
INFO 2018-08-09 19: 03: 11,401 Registration ACL file found, importing entries. This will take about 1.5 seconds per 1 million IDs
INFO 2018-08-09 19: 03: 11,402 Registration ACL loaded: action "DENY" for 2 registration IDs
INFO 2018-08-09 19: 03: 11,402 HBlink TCP reporting server configured
INFO 2018-08-09 19: 03: 11,403 HBlink 'HBlink.py' (c) 2016 N0MJS & the KOUSY Group - SYSTEM STARTING ...


Jürgen Clemenz
 

the /tmp/hblink.log
is empty.


Jürgen Clemenz
 

When starting hblink, the port 5400 is not opened.
Other applications such as Svxlink's Svxlink open doe ports.


Steve N4IRS
 

While hblink is running show us the result of netstat -unap

On 8/9/2018 2:31 PM, Jürgen Clemenz wrote:
When starting hblink, the port 5400 is not opened.
Other applications such as Svxlink's Svxlink open doe ports.



Jürgen Clemenz
 

On Thu, Aug 9, 2018 at 11:32 AM, Steve N4IRS wrote:
While hblink is running show us the result of netstat -unap
root@v293571:/home/dh9yap/HBlink# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
udp    50688      0 0.0.0.0:33462           0.0.0.0:*                           162/svxlink
udp    18432      0 0.0.0.0:33569           0.0.0.0:*                           165/svxlink
udp    47616      0 0.0.0.0:34179           0.0.0.0:*                           165/svxlink
udp    17664      0 0.0.0.0:34313           0.0.0.0:*                           170/svxlink
udp    35328      0 0.0.0.0:39745           0.0.0.0:*                           168/svxlink
udp    35328      0 0.0.0.0:40734           0.0.0.0:*                           166/svxlink
udp    50688      0 0.0.0.0:41970           0.0.0.0:*                           166/svxlink
udp    35328      0 0.0.0.0:46506           0.0.0.0:*                           162/svxlink
udp    50688      0 0.0.0.0:56694           0.0.0.0:*                           168/svxlink
udp    36864      0 0.0.0.0:56829           0.0.0.0:*                           169/svxlink
udp    15360      0 0.0.0.0:57484           0.0.0.0:*                           169/svxlink
udp    51456      0 0.0.0.0:5300            0.0.0.0:*                           150/svxreflector
udp    19200      0 0.0.0.0:5310            0.0.0.0:*                           156/svxreflector
udp    40704      0 0.0.0.0:5320            0.0.0.0:*                           146/svxreflector
udp    19200      0 0.0.0.0:5330            0.0.0.0:*                           153/svxreflector
udp    40704      0 0.0.0.0:5340            0.0.0.0:*                           149/svxreflector
udp    13824      0 0.0.0.0:5350            0.0.0.0:*                           151/svxreflector
udp    36864      0 0.0.0.0:5360            0.0.0.0:*                           147/svxreflector
udp    36864      0 0.0.0.0:5370            0.0.0.0:*                           144/svxreflector
udp        0      0 0.0.0.0:5380            0.0.0.0:*                           145/svxreflector
udp        0      0 0.0.0.0:5400            0.0.0.0:*                           171/python
root@v293571:/home/dh9yap/HBlink#
 


Jürgen Clemenz
 


Portscan


Jürgen Clemenz
 

and that when we start hblink.py
appropriate


Albert Lawson
 

Pi-Star has an inbound and outbound firewall configured by default that could be affecting it's ability to connect.  Have you looked at those settings by chance...???

 

73's

 

Albert/WB7AWL

 


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Jürgen Clemenz <j.clemenz@...>
Sent: Thursday, August 9, 2018 10:30 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Master maintenance loop started
 
Maybe you can try to connect my master.
Address: 213.202.228.66
Port 5400
Password: funknetz.nrw


Steve N4IRS
 

So,
HBlink is listening on port 5400. See Albert's message about the Pi-Star firewall. I suggest you test on port 62031 since it is not firewalled.

Steve n4IRS

On 08/09/2018 06:17 PM, Jürgen Clemenz wrote:
On Thu, Aug 9, 2018 at 11:32 AM, Steve N4IRS wrote:
While hblink is running show us the result of netstat -unap
root@v293571:/home/dh9yap/HBlink# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
udp    50688      0 0.0.0.0:33462           0.0.0.0:*                           162/svxlink
udp    18432      0 0.0.0.0:33569           0.0.0.0:*                           165/svxlink
udp    47616      0 0.0.0.0:34179           0.0.0.0:*                           165/svxlink
udp    17664      0 0.0.0.0:34313           0.0.0.0:*                           170/svxlink
udp    35328      0 0.0.0.0:39745           0.0.0.0:*                           168/svxlink
udp    35328      0 0.0.0.0:40734           0.0.0.0:*                           166/svxlink
udp    50688      0 0.0.0.0:41970           0.0.0.0:*                           166/svxlink
udp    35328      0 0.0.0.0:46506           0.0.0.0:*                           162/svxlink
udp    50688      0 0.0.0.0:56694           0.0.0.0:*                           168/svxlink
udp    36864      0 0.0.0.0:56829           0.0.0.0:*                           169/svxlink
udp    15360      0 0.0.0.0:57484           0.0.0.0:*                           169/svxlink
udp    51456      0 0.0.0.0:5300            0.0.0.0:*                           150/svxreflector
udp    19200      0 0.0.0.0:5310            0.0.0.0:*                           156/svxreflector
udp    40704      0 0.0.0.0:5320            0.0.0.0:*                           146/svxreflector
udp    19200      0 0.0.0.0:5330            0.0.0.0:*                           153/svxreflector
udp    40704      0 0.0.0.0:5340            0.0.0.0:*                           149/svxreflector
udp    13824      0 0.0.0.0:5350            0.0.0.0:*                           151/svxreflector
udp    36864      0 0.0.0.0:5360            0.0.0.0:*                           147/svxreflector
udp    36864      0 0.0.0.0:5370            0.0.0.0:*                           144/svxreflector
udp        0      0 0.0.0.0:5380            0.0.0.0:*                           145/svxreflector
udp        0      0 0.0.0.0:5400            0.0.0.0:*                           171/python
root@v293571:/home/dh9yap/HBlink#
 


Jürgen Clemenz
 

On Thu, Aug 9, 2018 at 03:46 PM, Steve N4IRS wrote:
62031
Hello
it seems to work :-)
Here is the log from the pi-star:
I have the port 62031 registered.
Is the timeout from the master correct or does it still have to change a setting in the hblink.cfg?

73 Juergen

Starting logging, please wait...
M: 2018-08-10 11:16:33.121 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
M: 2018-08-10 11:16:35.822 DMR Slot 2, received RF end of voice transmission, 2.5 seconds, BER: 0.3%, RSSI: -47/-47/-47 dBm
E: 2018-08-10 11:16:54.780 DMR, Connection to the master has timed out, retrying connection
M: 2018-08-10 11:16:54.781 DMR, Closing DMR Network
M: 2018-08-10 11:16:54.781 DMR, Opening DMR Network
M: 2018-08-10 11:17:11.560 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
M: 2018-08-10 11:17:16.780 DMR Slot 2, received RF end of voice transmission, 5.0 seconds, BER: 0.5%, RSSI: -47/-47/-47 dBm
E: 2018-08-10 11:18:04.908 DMR, Connection to the master has timed out, retrying connection
M: 2018-08-10 11:18:04.908 DMR, Closing DMR Network
M: 2018-08-10 11:18:04.909 DMR, Opening DMR Network
M: 2018-08-10 11:19:14.841 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
E: 2018-08-10 11:19:15.026 DMR, Connection to the master has timed out, retrying connection
M: 2018-08-10 11:19:15.027 DMR, Closing DMR Network
M: 2018-08-10 11:19:15.027 DMR, Opening DMR Network
M: 2018-08-10 11:19:21.863 DMR Slot 2, received RF end of voice transmission, 6.8 seconds, BER: 0.4%, RSSI: -47/-47/-47 dBm
M: 2018-08-10 11:19:34.584 DMR Slot 2, received RF voice header from DH9YAP to TG ALL
M: 2018-08-10 11:19:40.524 DMR Slot 2, received RF end of voice transmission, 5.8 seconds, BER: 0.5%, RSSI: -47/-47/-47 dBm
E: 2018-08-10 11:20:25.165 DMR, Connection to the master has timed out, retrying connection
M: 2018-08-10 11:20:25.165 DMR, Closing DMR Network
M: 2018-08-10 11:20:25.165 DMR, Opening DMR Network