DMR Master Disconnects


John - WB5NFC <wb5nfc@...>
 

I'm making a first run at installing ASL to DMR Bridge on a Rpi 3B+ with the latest ASL image. Install proceedes normally until I run MMDVM_Bridge in the foreground. First logon to the master server is good, but I get disconnected after about a minute. Then the cycle of connects and disconnects continues thereafter. Can someone point me in the right direction for determining the source of this behavior? Thanks in advance! John / WB5NFC

M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] TXPort -> 31100
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] RXPort -> 31103
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Slot -> 2
M: 2019-07-21 21:20:58.069 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-07-21 21:20:58.069 MMDVM_Bridge-20180423 is running
D: 2019-07-21 21:21:08.163 DMR, Sending authorisation
D: 2019-07-21 21:21:08.260 DMR, Sending configuration
M: 2019-07-21 21:21:08.363 DMR, Logged into the master successfully
W: 2019-07-21 21:22:08.475 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:23:08.480 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:23:08.480 DMR, Closing DMR Network
M: 2019-07-21 21:23:08.480 DMR, Opening DMR Network
D: 2019-07-21 21:23:18.587 DMR, Sending authorisation
D: 2019-07-21 21:23:18.685 DMR, Sending configuration
M: 2019-07-21 21:23:18.782 DMR, Logged into the master successfully
W: 2019-07-21 21:24:18.892 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:25:18.894 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:25:18.895 DMR, Closing DMR Network
M: 2019-07-21 21:25:18.895 DMR, Opening DMR Network
D: 2019-07-21 21:25:28.987 DMR, Sending authorisation
D: 2019-07-21 21:25:29.084 DMR, Sending configuration
M: 2019-07-21 21:25:29.181 DMR, Logged into the master successfully


Steve N4IRS
 

John,
As a start, Please show the [DMR] and [DMR Network] stanzas from MMDVM_Bridge.ini

Steve N4IRS

On 7/24/2019 12:28 PM, John - WB5NFC wrote:
I'm making a first run at installing ASL to DMR Bridge on a Rpi 3B+ with the latest ASL image. Install proceedes normally until I run MMDVM_Bridge in the foreground. First logon to the master server is good, but I get disconnected after about a minute. Then the cycle of connects and disconnects continues thereafter. Can someone point me in the right direction for determining the source of this behavior? Thanks in advance! John / WB5NFC

M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] TXPort -> 31100
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] RXPort -> 31103
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Slot -> 2
M: 2019-07-21 21:20:58.069 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-07-21 21:20:58.069 MMDVM_Bridge-20180423 is running
D: 2019-07-21 21:21:08.163 DMR, Sending authorisation
D: 2019-07-21 21:21:08.260 DMR, Sending configuration
M: 2019-07-21 21:21:08.363 DMR, Logged into the master successfully
W: 2019-07-21 21:22:08.475 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:23:08.480 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:23:08.480 DMR, Closing DMR Network
M: 2019-07-21 21:23:08.480 DMR, Opening DMR Network
D: 2019-07-21 21:23:18.587 DMR, Sending authorisation
D: 2019-07-21 21:23:18.685 DMR, Sending configuration
M: 2019-07-21 21:23:18.782 DMR, Logged into the master successfully
W: 2019-07-21 21:24:18.892 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:25:18.894 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:25:18.895 DMR, Closing DMR Network
M: 2019-07-21 21:25:18.895 DMR, Opening DMR Network
D: 2019-07-21 21:25:28.987 DMR, Sending authorisation
D: 2019-07-21 21:25:29.084 DMR, Sending configuration
M: 2019-07-21 21:25:29.181 DMR, Logged into the master successfully


John - WB5NFC <wb5nfc@...>
 

[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0


Mark N2NUO <n2nuo@...>
 

I just looked at the logs on Master 3102 and see your connection and sudden disconnects. I see no reason in the server for the disconnects, earlier in the day I see you have the incorrect password setup, but after that you connected and then soon after, it disconnects.
A little insight from the Master server side.
Mark

On 7/24/19 1:47 PM, John - WB5NFC wrote:
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0


John - WB5NFC <wb5nfc@...>
 

Interesting.... thanks, Mark. I've made no changes in configs today. Didn't even log in until late this morning and that was just to get the info Steve requested. I had saved the Connect / Disconnect messages earlier in the week.


Steve N4IRS
 

John,
Thanks for that. I don't see any issue. Thinking about your description, if you are running MMDVM_Bridge in the foreground, are you sure it's not ALSO running in background?
Before you start MB in the foreground:
ps ax | grep MMDVM

Steve

On 7/24/2019 1:47 PM, John - WB5NFC wrote:
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0


John - WB5NFC <wb5nfc@...>
 

I believe you're right on target, as usual! Time permitting,  educate me a little (or a LOT), please...

I didn't understand what I was seeing with the ps ax | grep MMDVM command.

root@WB5NFC-2186:/opt/MMDVM_Bridge#  ps ax | grep MMDVM
  668 ?        Ss     0:01 /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini
 1265 pts/0    S+     0:00 grep MMDVM

So I ran systemctl status mmdvm_bridge

● mmdvm_bridge.service - MMDVM_Bridge Service
   Loaded: loaded (/lib/systemd/system/mmdvm_bridge.service; enabled; vendor preset: enabled
   Active: active (running) since Wed 2019-07-24 13:51:14 CDT; 34min ago
 Main PID: 661 (MMDVM_Bridge)
   CGroup: /system.slice/mmdvm_bridge.service
           └─661 /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

Which I think... tells me, yes dummy, it's already running and there's your problem.  How I started it at boot and now how I keep it from starting at every boot (while testing) are questions I can't answer.....


Curt Hart <curtg49@...>
 

John,
it's starting at boot because the service is enabled. if you don't want it to start at boot systemctl disable mmdvm_bridge or after you've made changes systemctl restart mmdvm_bridge.
See systemctl --help
Hope this helps,
Curtis - N9INK

On Wednesday, July 24, 2019, 3:14:10 PM CDT, John - WB5NFC <wb5nfc@...> wrote:


I believe you're right on target, as usual! Time permitting,  educate me a little (or a LOT), please...

I didn't understand what I was seeing with the ps ax | grep MMDVM command.

root@WB5NFC-2186:/opt/MMDVM_Bridge#  ps ax | grep MMDVM
  668 ?        Ss     0:01 /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini
 1265 pts/0    S+     0:00 grep MMDVM

So I ran systemctl status mmdvm_bridge

● mmdvm_bridge.service - MMDVM_Bridge Service
   Loaded: loaded (/lib/systemd/system/mmdvm_bridge.service; enabled; vendor preset: enabled
   Active: active (running) since Wed 2019-07-24 13:51:14 CDT; 34min ago
 Main PID: 661 (MMDVM_Bridge)
   CGroup: /system.slice/mmdvm_bridge.service
           └─661 /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini

Which I think... tells me, yes dummy, it's already running and there's your problem.  How I started it at boot and now how I keep it from starting at every boot (while testing) are questions I can't answer.....


John - WB5NFC <wb5nfc@...>
 

Gentleman, thank you for identifying the source of my self-inflicted headache! Now that only one instance is running, there are no login/logout errors.

In trying to remember when or how I got into this twofer mess, I remember seeing the list of useful commands at the end of the setup document and trying them out. I just "assumed" anything started would reset after a boot. That little word sure gets people in trouble... thanks again, guys.


Steve N4IRS
 

John,
As Curt explained the install set up MMDVM_Bridge (and others) to start at boot. There will be times when you need to run in the foreground and all you need to do is make sure you are the only running copy unless you are running a more complex bridge.

systemctl has 6 commands you will want to know off the top of your head and quite a few more that -h or man systemctl will show you.

systemctl start mmdvm_bridge    # Start the mmdvm_bridge service
systemctl status mmdvm_bridge  # check the status of the mmdvm_bridge service. Is it running? is it enabled? any errors?
systemctl stop mmdvm_bridge     # stop the service IF it is running
systemctl restart mmdvm_bridge # restart the service (will also start it if not running) good for re-reading the config files.
systemctl enable mmdvm_bridge # setup the service to start at boot
systemctl disable mmdvm_bridge # stop the service from running at boot.

The 3 big ones for you with a running bridge are stop, start and status. Always check the status before running in the foreground.

Hope this helps,
Steve N4IRS 

On 7/24/19 5:03 PM, John - WB5NFC wrote:
Gentleman, thank you for identifying the source of my self-inflicted headache! Now that only one instance is running, there are no login/logout errors.

In trying to remember when or how I got into this twofer mess, I remember seeing the list of useful commands at the end of the setup document and trying them out. I just "assumed" anything started would reset after a boot. That little word sure gets people in trouble... thanks again, guys.


John - WB5NFC <wb5nfc@...>
 

Helps immensely. Thank you.


On Jul 24, 2019, at 4:44 PM, Steve N4IRS <szingman@...> wrote:

John,
As Curt explained the install set up MMDVM_Bridge (and others) to start at boot. There will be times when you need to run in the foreground and all you need to do is make sure you are the only running copy unless you are running a more complex bridge.

systemctl has 6 commands you will want to know off the top of your head and quite a few more that -h or man systemctl will show you.

systemctl start mmdvm_bridge    # Start the mmdvm_bridge service
systemctl status mmdvm_bridge  # check the status of the mmdvm_bridge service. Is it running? is it enabled? any errors?
systemctl stop mmdvm_bridge     # stop the service IF it is running
systemctl restart mmdvm_bridge # restart the service (will also start it if not running) good for re-reading the config files.
systemctl enable mmdvm_bridge # setup the service to start at boot
systemctl disable mmdvm_bridge # stop the service from running at boot.

The 3 big ones for you with a running bridge are stop, start and status. Always check the status before running in the foreground.

Hope this helps,
Steve N4IRS 

On 7/24/19 5:03 PM, John - WB5NFC wrote:
Gentleman, thank you for identifying the source of my self-inflicted headache! Now that only one instance is running, there are no login/logout errors.

In trying to remember when or how I got into this twofer mess, I remember seeing the list of useful commands at the end of the setup document and trying them out. I just "assumed" anything started would reset after a boot. That little word sure gets people in trouble... thanks again, guys.