A bit broken since today's update.

General support for the Pi-Star System
User avatar
EA3W
Posts: 5
Joined: Tue Jul 07, 2020 9:24 am
Location: Catalonia ||*||
Contact:

Re: A bit broken since today's update.

Post by EA3W »

DMR + disappeared when I activated the DMRGateway
I had DMRGateway activated with DMR +, TGIF and XLX, now I can only have DMR+ with TG9.
Hope you have a solution soon.

Greetings from Catalunya ||*||
Last edited by EA3W on Sat Jun 05, 2021 10:12 am, edited 1 time in total.
Xavi, EA3W
JN01XL
http://www.ea3w.cat
User avatar
m0guy
Posts: 26
Joined: Mon May 04, 2020 12:57 pm
Contact:

Re: A bit broken since today's update.

Post by m0guy »

KE7FNS wrote: Sat Jun 05, 2021 6:25 am
It was supposed to print out the buffer contents and its length in the log on the same line and since there isn't anything printed, it is probably NULL and shouldn't be. I assume it is a server side issue.
I've found the lines in the MMDVM code which output this error and agree, however I also turned on more logging on one of my DMR servers and it's interesting that I'm seeing no traffic from the pi-star hotspots. There is no attempt to send RPTL out to the server to begin the connection process. So this is something internal to the pi-stars.
-----------------------------
DMR Help: https://help.m0guy.com
Personal web: https://m0guy.com
User avatar
RC3C
Posts: 48
Joined: Tue Mar 05, 2019 12:09 pm
Location: Moscow
Contact:

Re: A bit broken since today's update.

Post by RC3C »

This morning time DMR (I am using DMR Gateway/D-STAR/DMR2YSF) and other modes are not working.
Here is a piece of /var/log/syslog file on my PI-STAR

Code: Select all

root@rc3c-pistar(rw):log# less syslog | more
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/tr/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/tr/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't chmod /var/cache/man/fi/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/fi/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/fi/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/fi/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't chmod /var/cache/man/ru/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/ru/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/ru/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/ru/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't chmod /var/cache/man/gl/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/gl/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/gl/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/gl/32401: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't chmod /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:03 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/fr.ISO8859-1/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/fr.ISO8859-1/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't chmod /var/cache/man/da/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/da/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/da/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/da/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't chmod /var/cache/man/sv/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/sv/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/sv/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/sv/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar systemd[1]: man-db.service: Succeeded.
Jun  5 00:00:04 rc3c-pistar rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="206" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't chmod /var/cache/man/pt/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/pt/CACHEDIR.TAG: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: fopen /var/cache/man/pt/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar mandb[32401]: /usr/bin/mandb: can't remove /var/cache/man/pt/32401: Read-only file system
Jun  5 00:00:04 rc3c-pistar systemd[1]: Started Daily man-db regeneration.
Jun  5 00:00:04 rc3c-pistar rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="206" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Jun  5 00:00:04 rc3c-pistar systemd[1]: logrotate.service: Succeeded.
Jun  5 00:00:04 rc3c-pistar systemd[1]: Started Rotate log files.
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: bits received from HRNG source: 660064
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: bits sent to kernel pool: 602560
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: entropy added to kernel pool: 602560
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS 140-2 successes: 33
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS 140-2 failures: 0
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS 140-2(2001-10-10) Poker: 0
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS 140-2(2001-10-10) Runs: 0
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS 140-2(2001-10-10) Long run: 0
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: HRNG source speed: (min=69.810; avg=334.795; max=727.583)Kibits/s
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: FIPS tests speed: (min=553.074; avg=3226.092; max=6376.510)Kibits/s
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: Lowest ready-buffers level: 2
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: Entropy starvations: 0
Jun  5 00:00:55 rc3c-pistar rngd[258]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Jun  5 00:01:14 rc3c-pistar minissdpd[531]: setsockopt(udp, IP_ADD_MEMBERSHIP)(eth0): Address already in use
Jun  5 00:03:36 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping ysf2dmr.service, but it can still be activated by:
Jun  5 00:03:36 rc3c-pistar pistar-watchdog.service[30418]:   ysf2dmr.timer
Jun  5 00:03:38 rc3c-pistar systemd[1]: Starting Pi-Star YSF2DMR Service...
Jun  5 00:03:38 rc3c-pistar systemd[1]: ysf2dmr.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:03:38 rc3c-pistar systemd[1]: ysf2dmr.service: Failed with result 'exit-code'.
Jun  5 00:03:38 rc3c-pistar systemd[1]: Failed to start Pi-Star YSF2DMR Service.
Jun  5 00:03:38 rc3c-pistar pistar-watchdog.service[30418]: Job for ysf2dmr.service failed because the control process exited with error code.
Jun  5 00:03:38 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status ysf2dmr.service" and "journalctl -xe" for details.
Jun  5 00:03:49 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping ysf2nxdn.service, but it can still be activated by:
Jun  5 00:03:49 rc3c-pistar pistar-watchdog.service[30418]:   ysf2nxdn.timer
Jun  5 00:03:51 rc3c-pistar systemd[1]: Starting Pi-Star YSF2NXDN Service...
Jun  5 00:03:51 rc3c-pistar systemd[1]: ysf2nxdn.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:03:51 rc3c-pistar systemd[1]: ysf2nxdn.service: Failed with result 'exit-code'.
Jun  5 00:03:51 rc3c-pistar systemd[1]: Failed to start Pi-Star YSF2NXDN Service.
Jun  5 00:03:51 rc3c-pistar pistar-watchdog.service[30418]: Job for ysf2nxdn.service failed because the control process exited with error code.
Jun  5 00:03:51 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status ysf2nxdn.service" and "journalctl -xe" for details.
Jun  5 00:04:02 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping ysf2p25.service, but it can still be activated by:
Jun  5 00:04:02 rc3c-pistar pistar-watchdog.service[30418]:   ysf2p25.timer
Jun  5 00:04:04 rc3c-pistar systemd[1]: Starting Pi-Star YSF2P25 Service...
Jun  5 00:04:04 rc3c-pistar systemd[1]: ysf2p25.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:04:04 rc3c-pistar systemd[1]: ysf2p25.service: Failed with result 'exit-code'.
Jun  5 00:04:04 rc3c-pistar systemd[1]: Failed to start Pi-Star YSF2P25 Service.
Jun  5 00:04:04 rc3c-pistar pistar-watchdog.service[30418]: Job for ysf2p25.service failed because the control process exited with error code.
Jun  5 00:04:04 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status ysf2p25.service" and "journalctl -xe" for details.
Jun  5 00:04:15 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping dmr2nxdn.service, but it can still be activated by:
Jun  5 00:04:15 rc3c-pistar pistar-watchdog.service[30418]:   dmr2nxdn.timer
Jun  5 00:04:17 rc3c-pistar systemd[1]: Starting Pi-Star DMR2NXDN Service...
Jun  5 00:04:18 rc3c-pistar systemd[1]: dmr2nxdn.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:04:18 rc3c-pistar systemd[1]: dmr2nxdn.service: Failed with result 'exit-code'.
Jun  5 00:04:18 rc3c-pistar systemd[1]: Failed to start Pi-Star DMR2NXDN Service.
Jun  5 00:04:18 rc3c-pistar pistar-watchdog.service[30418]: Job for dmr2nxdn.service failed because the control process exited with error code.
Jun  5 00:04:18 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status dmr2nxdn.service" and "journalctl -xe" for details.
Jun  5 00:04:28 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping dapnetgateway.service, but it can still be activated by:
Jun  5 00:04:28 rc3c-pistar pistar-watchdog.service[30418]:   dapnetgateway.timer
Jun  5 00:04:30 rc3c-pistar systemd[1]: Starting Pi-Star DAPNet Gateway Service...
Jun  5 00:04:31 rc3c-pistar systemd[1]: dapnetgateway.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:04:31 rc3c-pistar systemd[1]: dapnetgateway.service: Failed with result 'exit-code'.
Jun  5 00:04:31 rc3c-pistar systemd[1]: Failed to start Pi-Star DAPNet Gateway Service.
Jun  5 00:04:31 rc3c-pistar pistar-watchdog.service[30418]: Job for dapnetgateway.service failed because the control process exited with error code.
Jun  5 00:04:31 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status dapnetgateway.service" and "journalctl -xe" for details.
Jun  5 00:05:02 rc3c-pistar CRON[4825]: (root) CMD (/usr/local/sbin/pistar-upnp.service start > /dev/null 2>&1 &)
Jun  5 00:06:14 rc3c-pistar minissdpd[531]: setsockopt(udp, IP_ADD_MEMBERSHIP)(eth0): Address already in use
Jun  5 00:09:00 rc3c-pistar systemd[1]: Starting Clean php session files...
Jun  5 00:09:01 rc3c-pistar CRON[8595]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Jun  5 00:09:02 rc3c-pistar systemd[1]: phpsessionclean.service: Succeeded.
Jun  5 00:09:02 rc3c-pistar systemd[1]: Started Clean php session files.
Jun  5 00:09:43 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping ysf2dmr.service, but it can still be activated by:
Jun  5 00:09:43 rc3c-pistar pistar-watchdog.service[30418]:   ysf2dmr.timer
Jun  5 00:09:46 rc3c-pistar systemd[1]: Starting Pi-Star YSF2DMR Service...
Jun  5 00:09:46 rc3c-pistar systemd[1]: ysf2dmr.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:09:46 rc3c-pistar systemd[1]: ysf2dmr.service: Failed with result 'exit-code'.
Jun  5 00:09:46 rc3c-pistar systemd[1]: Failed to start Pi-Star YSF2DMR Service.
Jun  5 00:09:46 rc3c-pistar pistar-watchdog.service[30418]: Job for ysf2dmr.service failed because the control process exited with error code.
Jun  5 00:09:46 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status ysf2dmr.service" and "journalctl -xe" for details.
Jun  5 00:09:56 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping ysf2nxdn.service, but it can still be activated by:
Jun  5 00:09:56 rc3c-pistar pistar-watchdog.service[30418]:   ysf2nxdn.timer
Jun  5 00:09:59 rc3c-pistar systemd[1]: Starting Pi-Star YSF2NXDN Service...
Jun  5 00:09:59 rc3c-pistar systemd[1]: ysf2nxdn.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:09:59 rc3c-pistar systemd[1]: ysf2nxdn.service: Failed with result 'exit-code'.
Jun  5 00:09:59 rc3c-pistar systemd[1]: Failed to start Pi-Star YSF2NXDN Service.
Jun  5 00:09:59 rc3c-pistar pistar-watchdog.service[30418]: Job for ysf2nxdn.service failed because the control process exited with error code.
Jun  5 00:09:59 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status ysf2nxdn.service" and "journalctl -xe" for details.
Jun  5 00:10:01 rc3c-pistar CRON[9600]: (root) CMD (/usr/local/sbin/pistar-upnp.service start > /dev/null 2>&1 &)
Jun  5 00:10:09 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping ysf2p25.service, but it can still be activated by:
Jun  5 00:10:09 rc3c-pistar pistar-watchdog.service[30418]:   ysf2p25.timer
Jun  5 00:10:11 rc3c-pistar systemd[1]: Starting Pi-Star YSF2P25 Service...
Jun  5 00:10:12 rc3c-pistar systemd[1]: ysf2p25.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:10:12 rc3c-pistar systemd[1]: ysf2p25.service: Failed with result 'exit-code'.
Jun  5 00:10:12 rc3c-pistar systemd[1]: Failed to start Pi-Star YSF2P25 Service.
Jun  5 00:10:12 rc3c-pistar pistar-watchdog.service[30418]: Job for ysf2p25.service failed because the control process exited with error code.
Jun  5 00:10:12 rc3c-pistar pistar-watchdog.service[30418]: See "systemctl status ysf2p25.service" and "journalctl -xe" for details.
Jun  5 00:10:22 rc3c-pistar pistar-watchdog.service[30418]: Warning: Stopping dmr2nxdn.service, but it can still be activated by:
Jun  5 00:10:22 rc3c-pistar pistar-watchdog.service[30418]:   dmr2nxdn.timer
Jun  5 00:10:25 rc3c-pistar systemd[1]: Starting Pi-Star DMR2NXDN Service...
Jun  5 00:10:25 rc3c-pistar systemd[1]: dmr2nxdn.service: Control process exited, code=exited, status=1/FAILURE
Jun  5 00:10:25 rc3c-pistar systemd[1]: dmr2nxdn.service: Failed with result 'exit-code'.
Jun  5 00:10:25 rc3c-pistar systemd[1]: Failed to start Pi-Star DMR2NXDN Service.
Jun  5 00:10:25 rc3c-pistar pistar-watchdog.service[30418]: Job for dmr2nxdn.service failed because the control process exited with error code.
According to messages about, let's wait for any FIX on this issue.
Last edited by RC3C on Sat Jun 05, 2021 7:52 am, edited 1 time in total.
73! Anton aka Tony
EL #2102, EL #53698, DMR #2503041, XLX937-B
Clubs: RC5C, RY3AAL, NMDXC

Image
Image
DO4CZ
Posts: 19
Joined: Mon Dec 07, 2020 1:04 pm

Re: A bit broken since today's update.

Post by DO4CZ »

I have 3 hotspots and I noticed the following...

Hotspot 1 => Mode DMR only => ok
Hotspot 2 => Mode YST and D-Star => neither not work and under "Aktiv Modi" is D-Star and DMR Red
Hotspot 3 => Mode DMR Plus (DMR-Gateway) and D-Star => D-Star ok and DMR Plus not working
73, DE DO4CZ Joerg
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: A bit broken since today's update.

Post by MW0MWZ »

Those of you having issues with the DMRGateway - what DMRGateway version are you using - if its not the one I provide and you run your own version, you may have issues - Jonathan made some changes and the versions of MMDVMHost and DMRGateway need to have the same features in them.

So if you run some other 3rd party version of DMRGateway, please don't complain here.

If you are seeing the issue on the Pi-Star binaries - please let me have the output from:

Code: Select all

MMDVMHost -v
and

Code: Select all

DMRGateway -v

Looking into the DMR+D-Star issue now...
Andy

73 de MW0MWZ
http://pistar.uk
User avatar
m0guy
Posts: 26
Joined: Mon May 04, 2020 12:57 pm
Contact:

Re: A bit broken since today's update.

Post by m0guy »

MW0MWZ wrote: Sat Jun 05, 2021 8:29 am Those of you having issues with the DMRGateway - what DMRGateway version are you using - if its not the one I provide and you run your own version, you may have issues - Jonathan made some changes and the versions of MMDVMHost and DMRGateway need to have the same features in them.

So if you run some other 3rd party version of DMRGateway, please don't complain here.

If you are seeing the issue on the Pi-Star binaries - please let me have the output from:

Code: Select all

MMDVMHost -v
and

Code: Select all

DMRGateway -v

Looking into the DMR+D-Star issue now...

I'm using the stock binaries provided my pi-star, I've never install anything, just run the update/upgrade commands at regular intervals.

pi-star@pi-star-smlx(ro):pi-star$ MMDVMHost -v
MMDVMHost version 20210604_Pi-Star_v4 git #9106fd6
pi-star@pi-star-smlx(ro):pi-star$ DMRGateway -v
DMRGateway version 20210426_Pi-Star_v4 git #03bcdbc
pi-star@pi-star-smlx(ro):pi-star$
-----------------------------
DMR Help: https://help.m0guy.com
Personal web: https://m0guy.com
G4FDL
Posts: 44
Joined: Wed Apr 11, 2018 12:10 pm

Re: A bit broken since today's update.

Post by G4FDL »

root@pi-star(ro):pi-star# MMDVMHost -v
MMDVMHost version 20210604_Pi-Star_v4 git #9106fd6
root@pi-star(ro):pi-star# DMRGateway -v
DMRGateway version 20210426_Pi-Star_v4 git #03bcdbc
root@pi-star(ro):pi-star#

root@pi-star(ro):pi-star# tail DMRGateway-2021-06-05.log
M: 2021-06-05 08:43:58.743 Unknown packet from the MMDVM
M: 2021-06-05 08:43:58.743 0000: 52 50 54 4C 00 23 BD C8 *RPTL.#..*
M: 2021-06-05 08:44:08.748 Unknown packet from the MMDVM
M: 2021-06-05 08:44:08.748 0000: 52 50 54 4C 00 23 BD C8 *RPTL.#..*
DO4CZ
Posts: 19
Joined: Mon Dec 07, 2020 1:04 pm

Re: A bit broken since today's update.

Post by DO4CZ »

Andy, I don't use any modified files, everything is original from your image including your updates!

Until yesterday everything worked perfectly, the problems only appeared after yesterday's update to update.

MMDVMHost -v Output

Code: Select all

MMDVMHost version 20210604_Pi-Star_v4 git #9106fd6
DMRGateway -v Output

Code: Select all

DMRGateway version 20210426_Pi-Star_v4 git #03bcdbc
73, DE DO4CZ Joerg
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: A bit broken since today's update.

Post by MW0MWZ »

G4FDL wrote: Sat Jun 05, 2021 8:45 am root@pi-star(ro):pi-star# MMDVMHost -v
MMDVMHost version 20210604_Pi-Star_v4 git #9106fd6
root@pi-star(ro):pi-star# DMRGateway -v
DMRGateway version 20210426_Pi-Star_v4 git #03bcdbc
root@pi-star(ro):pi-star#

root@pi-star(ro):pi-star# tail DMRGateway-2021-06-05.log
M: 2021-06-05 08:43:58.743 Unknown packet from the MMDVM
M: 2021-06-05 08:43:58.743 0000: 52 50 54 4C 00 23 BD C8 *RPTL.#..*
M: 2021-06-05 08:44:08.748 Unknown packet from the MMDVM
M: 2021-06-05 08:44:08.748 0000: 52 50 54 4C 00 23 BD C8 *RPTL.#..*
Can you check your [DMR Network] section of the /etc/mmdvmhost config please.
There should be a new option called "Type" in there, this should be set to "Gateway" when using DMRGateway - both the config page and the update process should automatically address that for you, but I wonder if yours is missing for some reason.

The top of that section should look something like this:

Code: Select all

[DMR Network]
Type=Gateway
Enable=1
Address=127.0.0.1
Port=62031
Andy

73 de MW0MWZ
http://pistar.uk
G4FDL
Posts: 44
Joined: Wed Apr 11, 2018 12:10 pm

Re: A bit broken since today's update.

Post by G4FDL »

Looks like that's the issue

Code: Select all

[DMR Network]
Enable=1
Address=127.0.0.1
Port=62031
Jitter=600
Password="none"
Slot1=0
Slot2=1
Debug=0
ModeHang=20
Type=Direct
Local=62032
Post Reply