v4.2.0 Dashboard Failing

General support for the Pi-Star System
Post Reply
G0FHM
Posts: 57
Joined: Mon May 14, 2018 8:47 pm

v4.2.0 Dashboard Failing

Post by G0FHM »

Hi all,

I'm having issues with the dashboard regularly dropping out since the upgrade to 4.2.0 in as much as when you go to check it, it has frozen at some prior point in time, with the last inbound transmission showing infinity and no subsequent Net/RF data being displayed. I've seen it at odd times before with previous versions and a reboot has fixed it, but it seems to be near constant since the last update.

I've tried with different browsers on different OS's (to rule out cache and cookie issues) but it still happens.

I'm using a rpi 4b v1.5 coupled to a BI7JTA duplex board (V3F4) for what it is worth.

Is there anything else I can try this end?

Thanks,

J
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: v2.4.0 Dashboard Failing

Post by MW0MWZ »

G0FHM wrote: Tue Feb 13, 2024 2:33 pm Hi all,

I'm having issues with the dashboard regularly dropping out since the upgrade to 2.4.0 in as much as when you go to check it, it has frozen at some prior point in time, with the last inbound transmission showing infinity and no subsequent Net/RF data being displayed. I've seen it at odd times before with previous versions and a reboot has fixed it, but it seems to be near constant since the last update.

I've tried with different browsers on different OS's (to rule out cache and cookie issues) but it still happens.

I'm using a rpi 4b v1.5 coupled to a BI7JTA duplex board (V3F4) for what it is worth.

Is there anything else I can try this end?

Thanks,

J
Can you grab the last say 50 lines of /var/log/pi-star/MMDVM*.log and let me have them please.
Andy

73 de MW0MWZ
http://pistar.uk
G0FHM
Posts: 57
Joined: Mon May 14, 2018 8:47 pm

Re: v4.2.0 Dashboard Failing

Post by G0FHM »

Hi Andy,

The dashboard is stuck at 22.27h on 17/02

I can read the MMDVM log for 17/02 in it's entirety, but reading the log dated 18/02 gives an error. Below is the output for the latter half o 2024-02-17 22:26:51.319 YSF, received network data from MW0HMV to DG-ID 0 at FCS235-89
M: 2024-02-17 22:26:51.324 Mode set to System Fusion
M: 2024-02-17 22:26:57.103 YSF, network watchdog has expired, 4.6 seconds, 0% packet loss, BER: 0.0%
M: 2024-02-17 22:27:09.903 YSF, received network data from MW0HMV to DG-ID 0 at FCS235-89
M: 2024-02-17 22:27:19.860 YSF, network watchdog has expired, 8.2 seconds, 0% packet loss, BER: 0.0%
M: 2024-02-17 22:27:38.376 Mode set to Idle
M: 2024-02-17 22:27:43.544 YSF, received network data from MW0HMV to DG-ID 0 at FCS235-89
M: 2024-02-17 22:27:43.549 Mode set to System Fusion
M: 2024-02-17 22:27:56.941 YSF, network watchdog has expired, 12.2 seconds, 0% packet loss, BER: 0.0%
M: 2024-02-17 22:28:15.447 Mode set to Idle
M: 2024-02-17 23:51:37.225 Mode set to Idle
I: 2024-02-17 23:51:37.392 Stopped the DMR Id lookup reload thread
I: 2024-02-17 23:51:37.393 Closing network connections
M: 2024-02-17 23:51:37.393 DMR, Closing DMR Network
M: 2024-02-17 23:51:37.393 Closing YSF network connection
I: 2024-02-17 23:51:37.393 Stopping protocol handlers
I: 2024-02-17 23:51:37.393 MMDVMHost-20240210_PS4 has stopped
M: 2024-02-17 23:51:37.393 Closing the MMDVM
I: 2024-02-17 23:51:37.393 MMDVMHost-20240210_PS4 exited on receipt of SIGTERM
I: 2024-02-17 23:51:37.555 This software is for use on amateur radio networks only,
I: 2024-02-17 23:51:37.555 it is to be used for educational purposes only. Its use on
I: 2024-02-17 23:51:37.555 commercial networks is strictly prohibited.
I: 2024-02-17 23:51:37.555 Copyright(C) 2015-2023 by Jonathan Naylor, G4KLX and others
I: 2024-02-17 23:51:37.555 MMDVMHost-20240210_PS4 is starting
I: 2024-02-17 23:51:37.555 Built 06:27:43 Feb 10 2024 (GitID #218a017)
I: 2024-02-17 23:51:37.555 General Parameters
I: 2024-02-17 23:51:37.555 Callsign: MB6IWN
I: 2024-02-17 23:51:37.555 Id: 2343171
I: 2024-02-17 23:51:37.555 Duplex: no
I: 2024-02-17 23:51:37.555 Timeout: 240s
I: 2024-02-17 23:51:37.555 D-Star: disabled
I: 2024-02-17 23:51:37.555 DMR: enabled
I: 2024-02-17 23:51:37.555 YSF: enabled
I: 2024-02-17 23:51:37.555 P25: disabled
I: 2024-02-17 23:51:37.555 NXDN: disabled
I: 2024-02-17 23:51:37.555 M17: disabled
I: 2024-02-17 23:51:37.555 POCSAG: disabled
I: 2024-02-17 23:51:37.555 FM: disabled
I: 2024-02-17 23:51:37.555 AX.25: disabled
I: 2024-02-17 23:51:37.555 Modem Parameters
I: 2024-02-17 23:51:37.555 Protocol: uart
I: 2024-02-17 23:51:37.555 UART Port: /dev/ttyAMA0
I: 2024-02-17 23:51:37.555 UART Speed: 115200
I: 2024-02-17 23:51:37.555 RX Invert: yes
I: 2024-02-17 23:51:37.555 TX Invert: yes
I: 2024-02-17 23:51:37.555 PTT Invert: no
I: 2024-02-17 23:51:37.555 TX Delay: 100ms
I: 2024-02-17 23:51:37.555 RX Offset: 0Hz
I: 2024-02-17 23:51:37.555 TX Offset: 0Hz
I: 2024-02-17 23:51:37.555 RX DC Offset: 0
I: 2024-02-17 23:51:37.555 TX DC Offset: 0
I: 2024-02-17 23:51:37.555 RF Level: 100.0%
I: 2024-02-17 23:51:37.555 DMR Delay: 0 (0.0ms)
I: 2024-02-17 23:51:37.555 RX Level: 66.0%
I: 2024-02-17 23:51:37.555 CW Id TX Level: 50.0%
I: 2024-02-17 23:51:37.555 D-Star TX Level: 50.0%
I: 2024-02-17 23:51:37.555 DMR TX Level: 40.0%
I: 2024-02-17 23:51:37.555 YSF TX Level: 50.0%
I: 2024-02-17 23:51:37.555 P25 TX Level: 50.0%
I: 2024-02-17 23:51:37.556 NXDN TX Level: 50.0%
I: 2024-02-17 23:51:37.556 M17 TX Level: 50.0%
I: 2024-02-17 23:51:37.556 POCSAG TX Level: 50.0%
I: 2024-02-17 23:51:37.556 FM TX Level: 50.0%
I: 2024-02-17 23:51:37.556 AX.25 TX Level: 50.0%
I: 2024-02-17 23:51:37.556 TX Frequency: 434500000Hz (434500000Hz)
I: 2024-02-17 23:51:37.556 Use COS as Lockout: no
M: 2024-02-17 23:51:37.556 Opening the MMDVM
I: 2024-02-17 23:51:39.567 MMDVM protocol version: 1, description: MMDVM 20201214 (D-Star/DMR/System Fusion/P25/NXDN/POCSAG/FM) 12.0000 MHz GitID #7148cf9
I: 2024-02-17 23:51:39.587 Display Parameters
I: 2024-02-17 23:51:39.587 Type: None
W: 2024-02-17 23:51:39.587 No valid display found, disabling
I: 2024-02-17 23:51:39.587 Opening network connections
I: 2024-02-17 23:51:39.587 DMR Network Parameters
I: 2024-02-17 23:51:39.587 Type: Direct
I: 2024-02-17 23:51:39.587 Remote Address: 185.169.252.213
I: 2024-02-17 23:51:39.587 Remote Port: 55555
I: 2024-02-17 23:51:39.587 Local Address:
I: 2024-02-17 23:51:39.587 Local Port: 0
I: 2024-02-17 23:51:39.587 Jitter: 360ms
I: 2024-02-17 23:51:39.588 Slot 1: disabled
I: 2024-02-17 23:51:39.588 Slot 2: enabled
I: 2024-02-17 23:51:39.588 Mode Hang: 20s
I: 2024-02-17 23:51:39.588 Info Parameters
I: 2024-02-17 23:51:39.588 Callsign: MB6IWN
I: 2024-02-17 23:51:39.588 RX Frequency: 434500000Hz
I: 2024-02-17 23:51:39.588 TX Frequency: 434500000Hz
I: 2024-02-17 23:51:39.588 Power: 5W
I: 2024-02-17 23:51:39.588 Latitude: 52.601002deg N
I: 2024-02-17 23:51:39.588 Longitude: 0.377000deg E
I: 2024-02-17 23:51:39.588 Height: 15m
I: 2024-02-17 23:51:39.588 Location: "Downham Market"
I: 2024-02-17 23:51:39.588 Description: "UK"
I: 2024-02-17 23:51:39.588 URL: "www.g0fhm.co.uk/gb7gs"
M: 2024-02-17 23:51:39.588 DMR, Opening DMR Network
I: 2024-02-17 23:51:39.588 System Fusion Network Parameters
I: 2024-02-17 23:51:39.588 Local Address: 127.0.0.1
I: 2024-02-17 23:51:39.589 Local Port: 3200
I: 2024-02-17 23:51:39.589 Gateway Address: 127.0.0.1
I: 2024-02-17 23:51:39.589 Gateway Port: 4200
I: 2024-02-17 23:51:39.589 Mode Hang: 20s
M: 2024-02-17 23:51:39.589 Opening YSF network connection
I: 2024-02-17 23:51:39.589 Opening UDP port on 3200
I: 2024-02-17 23:51:39.589 RSSI
I: 2024-02-17 23:51:39.589 Mapping File: /usr/local/etc/RSSI.dat
I: 2024-02-17 23:51:39.589 Loaded 10 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2024-02-17 23:51:39.589 DMR Id Lookups
I: 2024-02-17 23:51:39.589 File: /usr/local/etc/DMRIds.dat
I: 2024-02-17 23:51:39.589 Reload: 24 hours
I: 2024-02-17 23:51:39.589 Loading ID lookup table from /usr/local/etc/DMRIds.dat
I: 2024-02-17 23:51:40.885 Loaded 254056 IDs to lookup table - /usr/local/etc/DMRIds.dat
I: 2024-02-17 23:51:40.885 Started the DMR Id lookup reload thread
I: 2024-02-17 23:51:40.885 Starting protocol handlers
I: 2024-02-17 23:51:40.885 DMR RF Parameters
I: 2024-02-17 23:51:40.885 Id: 234317150
I: 2024-02-17 23:51:40.885 Color Code: 3
I: 2024-02-17 23:51:40.885 Self Only: no
I: 2024-02-17 23:51:40.885 Embedded LC Only: no
I: 2024-02-17 23:51:40.885 Dump Talker Alias Data: no
I: 2024-02-17 23:51:40.885 Prefixes: 0
I: 2024-02-17 23:51:40.885 Call Hang: 1s
I: 2024-02-17 23:51:40.885 TX Hang: 1s
I: 2024-02-17 23:51:40.885 Mode Hang: 20s
I: 2024-02-17 23:51:40.885 OVCM: off
I: 2024-02-17 23:51:40.885 DMR Roaming Beacons Type: off
I: 2024-02-17 23:51:40.886 YSF RF Parameters
I: 2024-02-17 23:51:40.886 Low Deviation: no
I: 2024-02-17 23:51:40.886 Remote Gateway: no
I: 2024-02-17 23:51:40.886 TX Hang: 1s
I: 2024-02-17 23:51:40.886 Self Only: no
I: 2024-02-17 23:51:40.886 Mode Hang: 20s
I: 2024-02-17 23:51:40.886 Remote Control Parameters
I: 2024-02-17 23:51:40.886 Address: 127.0.0.1
I: 2024-02-17 23:51:40.886 Port: 7642
I: 2024-02-17 23:51:40.886 Opening UDP port on 7642
M: 2024-02-17 23:51:40.886 Mode set to Idle
I: 2024-02-17 23:51:40.886 MMDVMHost-20240210_PS4 is running
M: 2024-02-17 23:51:50.978 DMR, Logged into the master successfully

That is where the log for 17/02 ends.

If I try to read the log for 18/02, this happens:

[ Bad lock file is ignored: ./.MMDVM-2024-02-18.log.swp ] (at the bottom of the screen in nano)
Screenshot 2024-02-18 at 12-00-38 Pi-Star - Digital Voice Dashboard - SSH.png
Screenshot 2024-02-18 at 12-00-38 Pi-Star - Digital Voice Dashboard - SSH.png (37.48 KiB) Viewed 352 times
Obviously, a reboot cures the problem!

Thanks,

J
M1DNS
Pi-Star Team
Posts: 1394
Joined: Thu Apr 05, 2018 5:30 am

Re: v4.2.0 Dashboard Failing

Post by M1DNS »

Not a huge help, but...

MMDVMHost-20240210_PS4 exited on receipt of SIGTERM

SIGTERM is SIGnal to TERMinate, meaning "something" has told the application to quit.

What that "something" is will be the thing that needs exploring.

Sent via smoke signals using my SM-G935F

Andrew M1DNS.
Pi-star Admin Team.
G0FHM
Posts: 57
Joined: Mon May 14, 2018 8:47 pm

Re: v4.2.0 Dashboard Failing

Post by G0FHM »

I've just upgraded to v4.3.0 (fresh install on 32GB SD) with full updates and FS expanded and have run in to the same problem.

I wonder if it is due to a capacity issue? I've tried to make a backup copy of the mmdvmhost logfile in /var/log/pi-star folder, and get the error that there is no free space (see attached screenshot).

Wonder if the sudden running out of logging capacity is causing the error?

J
pistar.jpg
pistar.jpg (179.94 KiB) Viewed 300 times
G0FHM
Posts: 57
Joined: Mon May 14, 2018 8:47 pm

Re: v4.2.0 Dashboard Failing

Post by G0FHM »

PS,

If you want to dive in via SSH and have a poke around, I can always supply IP and password if you DM me

J
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: v4.2.0 Dashboard Failing

Post by MW0MWZ »

if I have the chance, I'll reach out to you tomorrow so I can have a look at what is going on.
Andy

73 de MW0MWZ
http://pistar.uk
G0FHM
Posts: 57
Joined: Mon May 14, 2018 8:47 pm

Re: v4.2.0 Dashboard Failing

Post by G0FHM »

If you could, that would be good.

I've left it "as is" for the time being, as now the dashboard is showing no DMR or YSF services running, and none of the pi-star logs are accessible. I think the services thing may be related to the paralell port permissions thing that I saw on here in a different thread?


J
GM4CCN
Posts: 1
Joined: Sun Feb 18, 2024 11:40 am

Re: v4.2.0 Dashboard Failing

Post by GM4CCN »

I hope this helps. I have all sorts of things going on after moving to 4.2.0, today I moved to 4.2.1 and all seems to be working fine now.
Post Reply