A bit broken since today's update.

General support for the Pi-Star System
g0hww
Posts: 16
Joined: Tue Jul 10, 2018 8:35 pm

A bit broken since today's update.

Post by g0hww »

Hi,

There seems to be a degree of buggeration in my hotspot with today's updates.
I've not been experiencing it long enough to be able to succinctly describe it but I'll try.

It's a dual mode DSTAR and DMR simplex hotspot on a dual-band DVMEGA on FW HR3.18.

All was working nicely, but since the update, I can connect to D-STAR REF030C and get a bit of traffic. I can get a response from the BM Parrot on DMR, and then something goes SNAFU and everything stops working. The "DMR Net" indicator in the dash goes red. It looks like the MMDVMHost restarts after 6 or so minutes and reconnects to BM UK. During that time, D-STAR calls to Echo will not function. After a reboot, the experience generally seems to be more or less the same.

The hotspot was a fairly recent install of 4.1.4, with daily updates. I did notice that during this upgrade, there was an indication from git that there was a conflict pertaining to upnp service file or similar, but no errors were shown on a reinvocation of the update mechanism.
There's nothing obvious in the dash log, or in dmesg or usual system logs.
Calling up the Brandmeister parrot on the local repeater running Pi-Star 3.4.17 shows no obvious signs of network problems.

I'm not desperate to get this working as I also have a newish OpenSpot3 to play with, so I can put in some effort investigating the brokenness if you need me to dig deeper.

Cheers,

Darren, G0HWW
g0hww
Posts: 16
Joined: Tue Jul 10, 2018 8:35 pm

Re: A bit broken since today's update.

Post by g0hww »

OK, there is some evidence of badness happening in /var/log/syslog. This is not necessarily consistent with any of the scenarios I described above, but then I'm not really sure what the actual problem that I'm reporting is, other than general buggeration.

Code: Select all

pi-star@pi-star(ro):~$ tail -f -n 50 /var/log/syslog 
Jun  4 23:32:55 pi-star systemd[1]: Started Update UTMP about System Runlevel Changes.
Jun  4 23:32:56 pi-star ntpd[911]: Soliciting pool server 162.159.200.123
Jun  4 23:32:56 pi-star ntpd[911]: Soliciting pool server 129.250.35.250
Jun  4 23:32:56 pi-star ntpd[911]: Soliciting pool server 51.155.16.62
Jun  4 23:32:56 pi-star ntpd[911]: Soliciting pool server 178.79.155.116
Jun  4 23:32:57 pi-star ntpd[911]: Soliciting pool server 162.159.200.1
Jun  4 23:32:57 pi-star ntpd[911]: Soliciting pool server 139.162.219.252
Jun  4 23:32:57 pi-star ntpd[911]: Soliciting pool server 80.87.128.222
Jun  4 23:32:57 pi-star kernel: [   26.521528] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Jun  4 23:32:57 pi-star systemd[1]: apt-daily-upgrade.service: Succeeded.
Jun  4 23:32:57 pi-star systemd[1]: Started Daily apt upgrade and clean activities.
Jun  4 23:32:57 pi-star systemd[1]: Startup finished in 3.737s (kernel) + 22.872s (userspace) = 26.609s.
Jun  4 23:32:58 pi-star ntpd[911]: Soliciting pool server 77.68.29.174
Jun  4 23:32:58 pi-star ntpd[911]: Soliciting pool server 81.21.65.169
Jun  4 23:32:59 pi-star ntpd[911]: Soliciting pool server 81.21.65.168
Jun  4 23:32:59 pi-star ntpd[911]: Soliciting pool server 2a00:2381:19c6::100
Jun  4 23:33:00 pi-star systemd[1]: Created slice User Slice of UID 1000.
Jun  4 23:33:00 pi-star systemd[1]: Starting User Runtime Directory /run/user/1000...
Jun  4 23:33:00 pi-star systemd[1]: Started User Runtime Directory /run/user/1000.
Jun  4 23:33:00 pi-star systemd[1]: Starting User Manager for UID 1000...
Jun  4 23:33:00 pi-star systemd[1372]: gpgconf: running /usr/bin/gpg-agent failed (exitcode=2): General error
Jun  4 23:33:00 pi-star systemd[1372]: gpgconf: fatal error (exit status 1)
Jun  4 23:33:00 pi-star systemd[1372]: Reached target Timers.
Jun  4 23:33:00 pi-star systemd[1372]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jun  4 23:33:00 pi-star systemd[1372]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jun  4 23:33:00 pi-star systemd[1372]: Starting D-Bus User Message Bus Socket.
Jun  4 23:33:00 pi-star systemd[1372]: Reached target Paths.
Jun  4 23:33:00 pi-star systemd[1372]: Listening on GnuPG cryptographic agent and passphrase cache.
Jun  4 23:33:00 pi-star systemd[1372]: Listening on GnuPG network certificate management daemon.
Jun  4 23:33:00 pi-star systemd[1372]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jun  4 23:33:00 pi-star systemd[1372]: Listening on D-Bus User Message Bus Socket.
Jun  4 23:33:00 pi-star systemd[1372]: Reached target Sockets.
Jun  4 23:33:00 pi-star systemd[1372]: Reached target Basic System.
Jun  4 23:33:00 pi-star systemd[1372]: Reached target Default.
Jun  4 23:33:00 pi-star systemd[1]: Started User Manager for UID 1000.
Jun  4 23:33:00 pi-star systemd[1372]: Startup finished in 378ms.
Jun  4 23:33:00 pi-star systemd[1]: Started Session 1 of user pi-star.
Jun  4 23:33:01 pi-star cron[406]: (*system*) RELOAD (/etc/crontab)
Jun  4 23:33:12 pi-star ntpd[911]: receive: Unexpected origin timestamp 0xe465289e.1cdcbac3 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe46528a8.3540604f
Jun  4 23:33:12 pi-star ntpd[911]: receive: Unexpected origin timestamp 0xe465289e.1cee6145 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe46528a8.356115a5
Jun  4 23:33:20 pi-star systemd[1]: Starting D-Star Radio Servce...
Jun  4 23:33:20 pi-star systemd[1]: Starting MMDVMHost Radio Servce...
Jun  4 23:33:20 pi-star systemd[1]: dstarrepeater.service: Control process exited, code=exited, status=1/FAILURE
Jun  4 23:33:20 pi-star systemd[1]: dstarrepeater.service: Failed with result 'exit-code'.
Jun  4 23:33:20 pi-star systemd[1]: Failed to start D-Star Radio Servce.
Jun  4 23:33:20 pi-star mmdvmhost.service[1644]: Dropping root permissions in daemon mode is disabled.
Jun  4 23:33:20 pi-star kernel: [   40.148915] uart-pl011 3f201000.serial: no DMA platform data
Jun  4 23:33:20 pi-star mmdvmhost.service[1644]: MMDVMHost started as PID 1678
Jun  4 23:33:20 pi-star systemd[1]: Started MMDVMHost Radio Servce.
Jun  4 23:33:22 pi-star systemd[1]: systemd-fsckd.service: Succeeded.
Jun  4 23:33:28 pi-star systemd[1]: systemd-hostnamed.service: Succeeded.
Jun  4 23:33:47 pi-star systemd[1]: Starting PiStar-Remote Service...
Jun  4 23:33:47 pi-star systemd[1]: Starting PiStar-Watchdog Service Watchdog...
Jun  4 23:33:47 pi-star systemd[1]: pistar-remote.service: Control process exited, code=exited, status=1/FAILURE
Jun  4 23:33:47 pi-star systemd[1]: pistar-remote.service: Failed with result 'exit-code'.
Jun  4 23:33:47 pi-star systemd[1]: Failed to start PiStar-Remote Service.
Jun  4 23:33:47 pi-star pistar-watchdog.service[2824]: pistar-watchdog started as PID 2829
Jun  4 23:33:47 pi-star systemd[1]: Started PiStar-Watchdog Service Watchdog.
Jun  4 23:33:48 pi-star systemd[1]: pistar-upnp.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun  4 23:33:48 pi-star systemd[1]: pistar-upnp.service: Failed with result 'exit-code'.
Jun  4 23:34:25 pi-star systemd[1]: mmdvmhost.service: Main process exited, code=killed, status=11/SEGV
Jun  4 23:34:25 pi-star systemd[1]: mmdvmhost.service: Failed with result 'signal'.
Jun  4 23:34:45 pi-star systemd[1]: Starting Pi-Star HostAPD Service...
Jun  4 23:34:45 pi-star systemd[1]: pistar-ap.service: Failed with result 'protocol'.
Jun  4 23:34:45 pi-star systemd[1]: Failed to start Pi-Star HostAPD Service.
Jun  4 23:35:01 pi-star CRON[6822]: (root) CMD (/usr/local/sbin/pistar-upnp.service start > /dev/null 2>&1 &)
Jun  4 23:35:18 pi-star pistar-watchdog.service[2824]: Warning: Stopping mmdvmhost.service, but it can still be activated by:
Jun  4 23:35:18 pi-star pistar-watchdog.service[2824]:   mmdvmhost.timer
Jun  4 23:35:20 pi-star systemd[1]: Starting MMDVMHost Radio Servce...
Jun  4 23:35:20 pi-star mmdvmhost.service[7873]: Dropping root permissions in daemon mode is disabled.
Jun  4 23:35:20 pi-star mmdvmhost.service[7873]: MMDVMHost started as PID 7882
Jun  4 23:35:20 pi-star systemd[1]: Started MMDVMHost Radio Servce.
Jun  4 23:35:30 pi-star pistar-watchdog.service[2824]: Warning: Stopping dmrgateway.service, but it can still be activated by:
Jun  4 23:35:30 pi-star pistar-watchdog.service[2824]:   dmrgateway.timer
Jun  4 23:35:32 pi-star systemd[1]: Starting DMRGateway Radio Servce...
Jun  4 23:35:32 pi-star systemd[1]: dmrgateway.service: Control process exited, code=exited, status=1/FAILURE
Jun  4 23:35:32 pi-star systemd[1]: dmrgateway.service: Failed with result 'exit-code'.
Jun  4 23:35:32 pi-star systemd[1]: Failed to start DMRGateway Radio Servce.
Jun  4 23:35:32 pi-star pistar-watchdog.service[2824]: Job for dmrgateway.service failed because the control process exited with error code.
Jun  4 23:35:32 pi-star pistar-watchdog.service[2824]: See "systemctl status dmrgateway.service" and "journalctl -xe" for details.
Jun  4 23:35:42 pi-star pistar-watchdog.service[2824]: Warning: Stopping ysfgateway.service, but it can still be activated by:
Jun  4 23:35:42 pi-star pistar-watchdog.service[2824]:   ysfgateway.timer
Jun  4 23:35:44 pi-star systemd[1]: Starting Yaesu System Fusion Servce...
Jun  4 23:35:44 pi-star systemd[1]: ysfgateway.service: Control process exited, code=exited, status=1/FAILURE
Jun  4 23:35:44 pi-star systemd[1]: ysfgateway.service: Failed with result 'exit-code'.
Jun  4 23:35:44 pi-star systemd[1]: Failed to start Yaesu System Fusion Servce.
Jun  4 23:35:44 pi-star pistar-watchdog.service[2824]: Job for ysfgateway.service failed because the control process exited with error code.
Jun  4 23:35:44 pi-star pistar-watchdog.service[2824]: See "systemctl status ysfgateway.service" and "journalctl -xe" for details.
Jun  4 23:35:54 pi-star pistar-watchdog.service[2824]: Warning: Stopping p25gateway.service, but it can still be activated by:
Jun  4 23:35:54 pi-star pistar-watchdog.service[2824]:   p25gateway.timer
Jun  4 23:35:56 pi-star systemd[1]: Starting P25 Servce...
Jun  4 23:35:57 pi-star systemd[1]: p25gateway.service: Control process exited, code=exited, status=1/FAILURE
Jun  4 23:35:57 pi-star systemd[1]: p25gateway.service: Failed with result 'exit-code'.
Jun  4 23:35:57 pi-star systemd[1]: Failed to start P25 Servce.
Jun  4 23:35:57 pi-star pistar-watchdog.service[2824]: Job for p25gateway.service failed because the control process exited with error code.
Jun  4 23:35:57 pi-star pistar-watchdog.service[2824]: See "systemctl status p25gateway.service" and "journalctl -xe" for details.
Jun  4 23:36:07 pi-star pistar-watchdog.service[2824]: Warning: Stopping ysfparrot.service, but it can still be activated by:
Jun  4 23:36:07 pi-star pistar-watchdog.service[2824]:   ysfparrot.timer
Jun  4 23:36:09 pi-star systemd[1]: Starting YSF Parrot...
Jun  4 23:36:09 pi-star systemd[1]: ysfparrot.service: Control process exited, code=exited, status=1/FAILURE
Jun  4 23:36:09 pi-star systemd[1]: ysfparrot.service: Failed with result 'exit-code'.
Jun  4 23:36:09 pi-star systemd[1]: Failed to start YSF Parrot.
Jun  4 23:36:09 pi-star pistar-watchdog.service[2824]: Job for ysfparrot.service failed because the control process exited with error code.
Jun  4 23:36:09 pi-star pistar-watchdog.service[2824]: See "systemctl status ysfparrot.service" and "journalctl -xe" for details.
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 »

The conflict on pistar-upnp.service is to be expected, that file is updated locally by the dashboard, so when i released a patched version - the update process caught that and fixed it.

As for the "badness" in the syslog, some of that is expected, it's down to the way the system will try and start all the daemons, and then work out of they are needed or not.

The most useful logs to look at are the ones in /var/log/pi-star - those are written by the radio related daemons and usually give you the best clue about what is going on.
Andy

73 de MW0MWZ
http://pistar.uk
CT2HRB
Posts: 19
Joined: Thu Apr 26, 2018 8:15 pm

Re: A bit broken since today's update.

Post by CT2HRB »

I can reproduce apparently similar problem as g0hww, new mmdvmhost updated today is crashing (11/SEGV) always 1min after started when DStar mode is enabled. Pi-Star watchdog will then restart it after a while and then crash after 1min again and again as g0hww says...

If I enable just DMR and/or YSF modes apparently no problem, it seems to happen only if DStar mode is enabled (alone or along other modes also enabled). I also have a DVMega (Single Band) hotspot, not sure if the issue is hotspot specific.
CT2HRB
Posts: 19
Joined: Thu Apr 26, 2018 8:15 pm

Re: A bit broken since today's update.

Post by CT2HRB »

I did check it before, unfortunately it's useless as nothing is added on the log when it crashs.
CT2HRB
Posts: 19
Joined: Thu Apr 26, 2018 8:15 pm

Re: A bit broken since today's update.

Post by CT2HRB »

JFYI: I did test to compile mmdvmhost myself from g4klx repo (also GitID #9106fd6), using normal "Makefile" (not any other Makefile.Pi.xxxx, as I have no display), all "stock" except I had to do a very very small change so it doesn't drop privileges from root... I guess Andy does something similar or uses display defines that disable that also (MMDVMHost.cpp, line 216, just added an "&& 0" there to disable that despite no display)... and my compiled mmdvmhost is running fine without the issue!

Anyway my binary is 7MB as old ones on PiStar, I'm not aware at all of the new "automated build system", that produces the new smaller files, that Andy refers on the announcement post.

Just some thoughts:
- is the issue related to any specific changes Andy may have applied for Pi-Star build?
- is it something related with that "automated build system" that I have no idea what it is?
- or something related to code specific to versions with displays support enabled? (as my compiled binary doesn't include these and works fine, as stated above)

Andy, if you have any ideas or need I test something (if you can't reproduce it) just let me know.
Last edited by CT2HRB on Sat Jun 05, 2021 6:51 am, edited 1 time in total.
User avatar
YL3IM
Posts: 39
Joined: Sun Nov 22, 2020 8:38 pm
Location: Riga, Latvia
Contact:

Re: A bit broken since today's update.

Post by YL3IM »

I ran into this error:

Code: Select all

M: 2021-06-05 03:35:05.526 Unknown packet from the MMDVM
M: 2021-06-05 03:35:05.526 0000:  52 50 54 4C 00 25 B0 76                            *RPTL.%.v*
VK2HL
Posts: 2
Joined: Sun Jun 03, 2018 7:39 am

Re: A bit broken since today's update.

Post by VK2HL »

Same here, strange stuff happening on my MMDVM Hotspot which has been running for months and this morning it had crashed. When re-starting it, it announced the connect to the reflector and then stopped before finishing the announcement. I could connect using my radio but it didn't run for long and stopped with the screen not timing out. It is a generic MMDVM single modem with OLED running on a Pi zero. It had been very reliable and I thought maybe the SD card was bad, so, I reflashed with an old image and it worked again but when I do an update, same thing happens. Sorry, can't be more specific. It is a DSTAR only node.
Update: I have a second hotspot in my car also running a DSTAR node but using a DVMEGA modem, and that is now sick as well.
Last edited by VK2HL on Sat Jun 05, 2021 7:45 am, edited 1 time in total.
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 »

YL3IM wrote: Sat Jun 05, 2021 3:36 am I ran into this error:

Code: Select all

M: 2021-06-05 03:35:05.526 Unknown packet from the MMDVM
M: 2021-06-05 03:35:05.526 0000:  52 50 54 4C 00 25 B0 76                            *RPTL.%.v*
I'm seeing the same, (well with my DMRID not yours). RPTL is the hotspot attempting to authenticate with the DMR server. Not sure why DMRGateway is reporting it as an unknown packet though.
-----------------------------
DMR Help: https://help.m0guy.com
Personal web: https://m0guy.com
CT2HRB
Posts: 19
Joined: Thu Apr 26, 2018 8:15 pm

Re: A bit broken since today's update.

Post by CT2HRB »

KE7FNS wrote: Sat Jun 05, 2021 3:01 amThe file size difference is nothing to be concerned about, its just one has debugging symbols and one doesn't.
Well, as I did mention before, I don't know at all what is that "automated build system", I did just mention it after seeing the announcement and got the idea of some possible differences, but maybe misinterpretation at my side... after 'strip' my binary is 650KB, Andy one is 500KB... but for sure differences may be related to other things of his build system as you say... I did compile mine on Pi-Star itself on RPi... let's wait for sure! ;)
Post Reply