DMR Master Connection Timeout & Master is closing down

[N9MNU]

For approx a month I've been unable to connect to a BM master. Based on Pi-star dashboard I thought connection was successful. I started watching closely and the DMR Net in Network Status column is red. Yet in the past when I checked it was green. Perhaps it was going red and I didn't see. I've tried difference server 3101, 3102, 3103, & 3108 but the problem continues. I then backed up config and reset to factory defaults and restored the config. Problem continues.

When I look at the BM dashboard/ My Hotspots sometimes the icon is green and clicking "Get IP Address" returns the correct value. Sometimes, most of the time, error 500 is displayed.

Famous last words but to my knowledge nothing has changed on my end. Here is the result of the live logs:

Starting logging, please wait...
M: 2019-11-23 20:18:19.194 DMR Slot 2, received RF voice header from N9MNU to TG 9999
M: 2019-11-23 20:18:22.249 DMR Slot 2, received RF end of voice transmission from N9MNU to TG 9999, 3.2 seconds, BER: 0.2%, RSSI: -47/-47/-47 dBm
M: 2019-11-23 20:18:24.112 DMR, Logged into the master successfully
E: 2019-11-23 20:19:50.821 DMR, Master is closing down
M: 2019-11-23 20:19:50.821 DMR, Closing DMR Network
M: 2019-11-23 20:19:50.822 DMR, Opening DMR Network
E: 2019-11-23 20:21:00.930 DMR, Connection to the master has timed out, retrying connection
M: 2019-11-23 20:21:00.930 DMR, Closing DMR Network
M: 2019-11-23 20:21:00.930 DMR, Opening DMR Network
E: 2019-11-23 20:22:11.051 DMR, Connection to the master has timed out, retrying connection
M: 2019-11-23 20:22:11.052 DMR, Closing DMR Network

Any ideas how to resolve?

[N9MNU]

I'm not sure what the cause of this issue was but the resolution was to format the SD card and install the latest Pi-Star version for the device. I then setup on the correct SSID, performed an update, then set the parameters correctly. All seems to be working now.

[VK7HSE]

Sometimes it's just easier to reformat and start a fresh when unexpected things start to happen.

Naturally it's nice to know what went wrong and how to fix it, but time and sanity play a part in that too!

Sent from my Pixel 4 XL using Tapatalk

[F5VMR]

I disagree that this is the way to resolve this issue. I have just begun to encounter this error with a relatively new install on a micro-repeater. It has been working well until a few moments ago when the DMR Network turned red mid QSO. The log indicates :
from G4NOY to TG 8082, 19.6 seconds, 0% packet loss, BER: 0.0%
M: 2020-02-25 12:51:19.368 DMR Slot 1, received network voice header from GD6XHG to TG 8082
E: 2020-02-25 12:51:21.480 DMR, Master is closing down
M: 2020-02-25 12:51:21.480 DMR, Closing DMR Network
M: 2020-02-25 12:51:21.481 DMR, Opening DMR Network
M: 2020-02-25 12:51:22.977 DMR Slot 1, network watchdog has expired, 3.2 seconds, 33% packet loss, BER: 0.0%
E: 2020-02-25 12:52:31.499 DMR, Connection to the master has timed out, retrying connection
M: 2020-02-25 12:52:31.499 DMR, Closing DMR Network
M: 2020-02-25 12:52:31.499 DMR, Opening DMR Network
E: 2020-02-25 12:53:41.528 DMR, Connection to the master has timed out, retrying connection
M: 2020-02-25 12:53:41.528 DMR, Closing DMR Network
M: 2020-02-25 12:53:41.528 DMR, Opening DMR Network
E: 2020-02-25 12:54:51.544 DMR, Connection to the master has timed out, retrying connection.
It is not a Pi issue as the processor is in good form. Nor is it a Modem issue as the repeater continues to function. I have set BrandMeister and IPSC2-Phoenix-F with the appropriate changes to talk-groups. BrandMeister self-care has fixed groups, as has IPSC2 and for several days has been operating within normal parameters.
Then:
M: 2020-02-25 13:07:30.677 DMR, Closing DMR Network
M: 2020-02-25 13:07:30.677 DMR, Opening DMR Network
M: 2020-02-25 13:08:10.722 DMR, Logged into the master successfully
E: 2020-02-25 13:09:39.480 DMR, Master is closing down
M: 2020-02-25 13:09:39.480 DMR, Closing DMR Network
M: 2020-02-25 13:09:39.480 DMR, Opening DMR Network
staying up for less than a minute.
I'll reset it to DMR Only to see what happens, then I'll reset it back to DMR Network after tests.
Added - (Using Pi 3B with Pi-Star 4.1.0.-RC8.)

[M1DNS]

Couple things I'd do. Try using 3.4 it differs from 4.1 slightly. If it's a 3B and not a 3B+ it should run with 3.4

Contact BM to check there is no issue with ur particular id no. Given you've tried several of their servers it's strange they'd all give the same issue if everything is ok with ur install.

BrandMeister General Support (English)
https://t.me/BRANDMEISTERGENERALSUPPORT



Sent from my SM-G935F using Tapatalk

[F5VMR]

Thanks for a prompt reply Andrew. But the Pi3B is quite capable of running Buster as I use it in the FM repeaters with SVXLink. I reverted to BrandMeister Only and the problem does not occur, so I am guessing that trying to run Two networks simultaneously might be the issue. Despite living in France, I choose the UK networks in Preference for my own repeater at the house, but for the two in service I have selected French Networks. F5ZLR has DMR Network (BM & IPSC2-France 3) on RC8 and has no problems. F5ZLW has RC4 on Stretch and I've no reason to change it at the moment and it's still only on BM. But I'll experiment further to see what occurs.
http://f5zgm.f8kfz.org:19389/

(A side issue that also came to light is that both my RT3 and MD380G get rebooted when certain signals appear on the repeater and not necessarily on the talk group that I am on. Most of the stations that cause the issue are from Region 2 and rarely does it happen with stations in Europe. I have since pared down the fixed talk-groups to stop the problem but not eradicated it as when activating a dynamic group where the stations might pop up recreates the problem still. I've spoken with Jonathan G4KLX, and it could be data that passes through the MMDVM so nothing to do with local conditions at all. So Minimum TG Minimum Networks, and we'll see how it goes.)

Many thanks again.

[F5VMR]

Ok, so that IS odd.
Without DMR Gateway, the repeater has no issue at all - doesn't drop the connection with the BM2341 and is quite happy. Change the setting to DMR Gateway with BM as the only setting and it crashes within a few minutes, dropping the connection.
pi-star@pi-star(ro):pi-star$ tail -f MMDVM-2020-02-25.log
E: 2020-02-25 15:44:57.168 DMR, Master is closing down
M: 2020-02-25 15:44:57.168 DMR, Closing DMR Network
M: 2020-02-25 15:44:57.168 DMR, Opening DMR Network
M: 2020-02-25 15:44:58.655 DMR Slot 1, network watchdog has expired, 7.6 seconds, 14% packet loss, BER: 0.0%
E: 2020-02-25 15:46:07.181 DMR, Connection to the master has timed out, retrying connection
M: 2020-02-25 15:46:07.181 DMR, Closing DMR Network
M: 2020-02-25 15:46:07.181 DMR, Opening DMR Network
E: 2020-02-25 15:47:17.209 DMR, Connection to the master has timed out, retrying connection
M: 2020-02-25 15:47:17.209 DMR, Closing DMR Network
M: 2020-02-25 15:47:17.209 DMR, Opening DMR Network

[F5VMR]

OK, so it worked continuously without issue with BrandMeister without setting it as a Gateway Selection. Within minutes of setting it as the sole entry as a Gateway entry, the server connection to the Master was terminated. I see that when we switch to the Gateway from the Standard settings the the address changes in the MMDVMHost ini to 127.0.0.1 taking the BrandMeister address from the DMR GW file. However could this be the problem? Is there an issue with the IP address redirect? Yes I have reset everything to begin again, and the result is the same.

[M1DNS]

Thanks for a prompt reply Andrew. But the Pi3B is quite capable of running Buster as I use it in the FM repeaters with SVXLink.

Many thanks again.

Yes it should indeed. The idea was 3.4 runs the earlier (although outdated) stretch OS so was trying to limit anything that might be in the new release. Kinda of the echoing the foughts above.


Interesting as you, I too am seeing an issue with 2341 and dmrgateway with a repeater install. Im resident in the UK so use it on one particular install and a couple others connected to Ireland and the Danish servers. I've had 2341 running as a straight connection, without using dmrgateway but changing it does create an error and the connection drops. Ireland and Denmark don't appear to drop for me when using dmrgateway with my simplex installs they don't seem to care if using dmrgateway or not.

Sent from my SM-G935F using Tapatalk

[F5VMR]

OK, so we are on the same page - I thought I was going crazy. I'll switch BM servers and see what happens. I don't think ISPC2 server-F has any particular issues. I've a rather complicated TG redirection routine in place, that I have eliminated as the cause, so in the same CP I can have TGs for BrandMeister as standard, and TGs for IPSC2 overlaid by 8000, so 8235 is 235 and 8080-8084 as 80-84 on slot 1, and 8860 as 860 on slot 2, but it all falls over when the BrandMeister Master throws me out. Doh! - I'll keep my eye on things in case of any updates.
Thanks Again.Chris