Topics

DVSwitch Dashboard - DMR Master Information


g8ptn@...
 

Hi,
A minor observation on the DVSwitch Dashboard.

I have noticed that the “DMR Master” information keeps disappearing. Everything is still working as expected and DVSwitch is connected to the DMR server.

Switching between servers in the “dvs” control panel restores the dialog information.

 

 

PS. Keep up the great work on DVSwitch. Even using the software vocoder, for DMR the audio on both transmit and receive is excellent.

Regards,

Dave (G8PTN)



Version information below.


Software:
dvswitch.sh version 1.6.0
Analog_Bridge version 1.6.0
MMDVM_Bridge version 20201129_V1.6.2 git #89f8998
P25Gateway version 20200824
NXDNGateway version 20200824
YSFGateway version 20200908

 

Hardware:
Raspberry Pi 3 Model B


Steve N4IRS
 

Make sure you have done a update / upgrade. and retest.

On 12/9/20 7:31 AM, g8ptn@... wrote:

Hi,
A minor observation on the DVSwitch Dashboard.

I have noticed that the “DMR Master” information keeps disappearing. Everything is still working as expected and DVSwitch is connected to the DMR server.

Switching between servers in the “dvs” control panel restores the dialog information.

 

 

PS. Keep up the great work on DVSwitch. Even using the software vocoder, for DMR the audio on both transmit and receive is excellent.

Regards,

Dave (G8PTN)



Version information below.


Software:
dvswitch.sh version 1.6.0
Analog_Bridge version 1.6.0
MMDVM_Bridge version 20201129_V1.6.2 git #89f8998
P25Gateway version 20200824
NXDNGateway version 20200824
YSFGateway version 20200908

 

Hardware:
Raspberry Pi 3 Model B



g8ptn@...
 

Hi Steve,

I have done the update/upgrade and it seems fine now.

Many thanks.

Dave


Chris K6CV
 

Hi Steve, I'm a newbie here, and seem to have a issue with lighttpd, below is what I see, and of course no dashboard web page found.
Not sure what all this means, but it looks like my webproxy service is in a damaged and not running state.
:
root@raspberrypi:/var# ps ax | grep lighttpd
17717 pts/0    S+     0:00 grep lighttpd
root@raspberrypi:/var#

root@raspberrypi:/var/log/mmdvm# systemctl restart webproxy
Failed to restart webproxy.service: Unit webproxy.service not found.
root@raspberrypi:/var/log/mmdvm# ps ax | grep lighttpd
11431 pts/0    S+     0:00 grep lighttpd

root@raspberrypi:/var/log/mmdvm# systemctl status lighttpd
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-12-10 11:06:31 PST; 1h 8min ago
  Process: 773 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
  Process: 778 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
 Main PID: 778 (code=exited, status=255/EXCEPTION)
 
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Dec 10 11:06:31 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Dec 10 11:06:31 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
root@raspberrypi:/var/log/mmdvm#

73's
DE K6CV Chris.


Steve N4IRS
 

Did you edit /etc/lighttpd/lighttpd.conf?
show me the result of: systemctl status webproxy
show me the result of: ls /lib/systemd/system/web*

Steve N4IRS


On 12/10/2020 3:53 PM, Chris K6CV wrote:
Hi Steve, I'm a newbie here, and seem to have a issue with lighttpd, below is what I see, and of course no dashboard web page found.
Not sure what all this means, but it looks like my webproxy service is in a damaged and not running state.
:
root@raspberrypi:/var# ps ax | grep lighttpd
17717 pts/0    S+     0:00 grep lighttpd
root@raspberrypi:/var#

root@raspberrypi:/var/log/mmdvm# systemctl restart webproxy
Failed to restart webproxy.service: Unit webproxy.service not found.
root@raspberrypi:/var/log/mmdvm# ps ax | grep lighttpd
11431 pts/0    S+     0:00 grep lighttpd

root@raspberrypi:/var/log/mmdvm# systemctl status lighttpd
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-12-10 11:06:31 PST; 1h 8min ago
  Process: 773 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
  Process: 778 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)
 Main PID: 778 (code=exited, status=255/EXCEPTION)
 
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Dec 10 11:06:31 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Dec 10 11:06:31 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Dec 10 11:06:31 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
root@raspberrypi:/var/log/mmdvm#

73's
DE K6CV Chris.


g8ptn@...
 

Hi Steve,

Unfortunately, when I opened the browser today 11th Dec, the “DMR Master” information had disappeared again. I wonder if it is happening on a 24-hour basis.


Changing the Default DMR Server in the “dvs” control panel restores the information as before.


Dave 


SP2ONG Waldek
 

Dave,

The dashboard is searching in MMDVM_Bridge log file with current data

grep -a 'DMR, Logged\|DMR, Closing DMR\|DMR, Opening DMR\|DMR, Connection' /var/log/mmdvm/MMDVM_Bridge-2020-12-11.log

and if the result is empty the dashboard looking to MMDVM_Bridge log file with yesterday

grep -a 'DMR, Logged\|DMR, Closing DMR\|DMR, Opening DMR\|DMR, Connection' /var/log/mmdvm/MMDVM_Bridge-2020-12-10.log

As so result this command is used to create the status of DMR Server.

If your system works 24H and you have connected to DMR Serve for more than 2 days without changing DMR server at current the dashboard can not has the possibility get info about the connected DMR server

if see that info about the status DMR Server is empty try to check log file with the above command where file name MMDVM_Bridge log file must be with yesterday

Waldek



SP2ONG Waldek
 

My dvswitch server is working 24H and I use a simple method to recovery info about status connected servers / links

I put in /etc/cron.d/ file with contain:

MAILTO=""
#
0 2 * * * root systemctl restart mmdvm_bridge
0 2 * * * root systemctl restart ysfgateway
0 2 * * * root systemctl restart nxdngateway
0 2 * * * root systemctl restart p25gateway
#

after creating the file you must restart crontab

/etc/init.d/cron restart

which restart services during the night for example 2:00
In MMDV_Bridge.ini in [DMR Network] I put my base DMR server (IP address, port , password) and
in NXDNGateway.ini and P25gateway.ini YSFgateway.ini  I have defined in Startup=  
reflectors which I want always connected after a restart of services


g8ptn@...
 

Hi Waldek,

Next time I see the missing information I will check the log files with the grep command you have provided and add the workaround.

Thank you very much for the prompt and detailed response.


Dave