Date   

Re: DVSwitch Dashboard - DMR Master Information

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 


Re: DVSwitch Dashboard - DMR Master Information

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.


Re: DVSwitch Dashboard - DMR Master Information

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.


Re: DVSwitch Dashboard - DMR Master Information

g8ptn@...
 

Hi Steve,

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

Many thanks.

Dave


Re: Using DVSwitch to access DMR+/Phoenix

G4WXN@...
 

Thanks, I'll give it a whirl.

--
Derek

G4WXN


Re: MMDVM to MMDVM connections ?

Gerry Filby
 

Figures ... was curious if the underlying protocol could support peer to peer connections ...

Cheers !
Gerry.


Re: Using DVSwitch to access DMR+/Phoenix

Steve N4IRS
 

sudo /opt/Analog_Bridge/dvswitch.sh tune PASSWORD@...:55555:StartRef=4440;RelinkTime=180;UserLink=1!9

On 12/10/2020 11:16 AM, G4WXN@... wrote:
sudo /opt/Analog_Bridge/dvswitch.sh tune PASSWORD@...:55555:StartRef=4440;RelinkTime=180;UserLink=1
--
Derek

G4WXN


Re: Using DVSwitch to access DMR+/Phoenix

G4WXN@...
 

sudo /opt/Analog_Bridge/dvswitch.sh tune PASSWORD@...:55555:StartRef=4440;RelinkTime=180;UserLink=1
--
Derek

G4WXN


Re: connection Ycs server

luiz_sergio lemos PU1LOY
 

I listen to audio from other stations, but when I transmit nothing appears on the YCS panel.


Re: MMDVM to MMDVM connections ?

Daryl
 

I use my gateway ID as a TG on BM as a place to go so as not to tie up one of the chat TG's.
Works for me and a couple of my locals
Daryl
G0 ANV


Re: connection Ycs server

luiz_sergio lemos PU1LOY
 

191.252.101.21:42000


Re: connection Ycs server

Steve N4IRS
 

What YCS reflector? What is your tune string?

On 12/10/20 6:16 AM, luiz_sergio lemos wrote:
Hi,

Dvswitch ysf mode connects to the YCS server but does not transmit audio. 
Any tips?

PU1LOY Luiz Sérgio


connection Ycs server

luiz_sergio lemos PU1LOY
 

Hi,

Dvswitch ysf mode connects to the YCS server but does not transmit audio. 
Any tips?

PU1LOY Luiz Sérgio


Re: digital transmit overtime

Patrick Perdue
 

I’m adjusting it on the USRP node.
For now, I wrote a cheap shell script that is called only when the USRP node is keying towards ASL, which sleeps for a while, mutes both TLV and USRP. Then another script runs when the node stops transmitting which kills the running time or if it exists, then unmute A_B 10 seconds later. It isn’t perfect, but it does give people a chance to disconnect if things go on for a long time.

Sent from my zippo

On Dec 9, 2020, at 18:57, Steve N4IRS <szingman@msgstor.com> wrote:

Patrick,
Which TOT are you adjusting? Are you adjusting the TOT on the USRP node or the ASL TX? The TOT controls the TX not the RX. Just a thought.

Steve

On 12/9/20 5:55 AM, Patrick Perdue wrote:
Hi Steve:

Thanks. Yeah, I thought it should work the same as any other channel driver, so I changed it to a ridiculously low number (10000), and transmissions over 10 seconds across the bridge still passed after rpt reload, at least from digital to analog. I didn't test in the other direction.











Re: DVSwitch Dashboard Web Port

Joe, WB3IHY
 

Steve,
Webproxy WASN'T running.  That was the netstat output from the WORKING nodes.  Netstat had shown nothing for port 8080 on the non-working one.  That should have been my first clue.  Bu the lack of a generated log file clinched it.

Incidentally, I did look (and had tried) your suggested way of upgrading nodejs.  For some reason, that method completely hosed the existing install on that server.  As a result, I ended up having to remove and completely purge it.

Doing so also removed the DVSwitch installation (but, thankfully, left all the config files intact).  After reinstalling DVSwitch, I ended up back at version 4 of node...which I was then able to successfully update the way I described.

I'm betting that it had something to do with the fact that the server is Ubuntu based (Mint) rather than "pure" Debian (Stretch).  But hey, no big deal.  Just happy it now works.

Thanks again for pointing me in the right direction(s).

73,
Joe


Re: DVSwitch Dashboard Web Port

Steve N4IRS
 

Joe,
Interesting that webproxy was not running when it was showing with netstat.
As far as upgrading nodejs, you might look at: <https://github.com/nodesource/distributions>

curl -sL https://deb.nodesource.com/setup_15.x | sudo -E bash -
sudo apt-get install -y nodejs

I used it to upgrade a install of Stretch.

Glad you have it working.

Steve

On 12/9/20 10:28 PM, Joe, WB3IHY wrote:

Okay...problem (finally) solved.  Turns out that the problem was (probably) not related to changing the dashboard web port.  Documenting my experience so that others may benefit.

Steve, your suggestion to check for webproxy log started me on the trail: THERE WASN'T ONE! Which meant that the service wasn't running at all.

I then tried running the following command manually: sudo /usr/bin/node /opt/Web_Proxy/proxy.js 8080 2222 which generated a SyntaxError: "Unexpected token "Const { Exit }"

Much Googling told me earlier versions of node.js would do that.  Found out that, somehow, I had version (gasp) 4 installed for some reason! My other instances were running 8.10.0, so that had to be the culprit.  Much more Googling told me how to update it to the latest version (15.4.0 as of this writing):

First, install npm: sudo apt-get install npm
Then install n, a node version manager: sudo npm install -g n
Then install the latest version of node: sudo n latest
If the installer changed the path from what's specified in the webproxy service call, change it back with "PATH=$PATH"
Verify that node was truly updated with: node -v
Try running the service manually: sudo /usr/bin/node /opt/Web_Proxy/proxy.js 8080 2222
If you still get the same error, you might have to forcibly copy the newer binary to where the webproxy expects it to be: sudo cp /usr/local/n/versions/node/15.4.0/bin/node /usr/bin/node
Try running the service manually again.  If you get a "cannot find module "ws" " error, then do this: cd /opt/Web_Proxy/ and then install the ws module with sudo npm install ws
Try running the service manually again.  It should now run with no errors.  Control C out of it.  You're almost done.
Finally, start the service properly: sudo systemctl start webproxy.service

Voila: RX Monitor audio AT LAST!



Re: DVSwitch Dashboard Web Port

Joe, WB3IHY
 

Okay...problem (finally) solved.  Turns out that the problem was (probably) not related to changing the dashboard web port.  Documenting my experience so that others may benefit.

Steve, your suggestion to check for webproxy log started me on the trail: THERE WASN'T ONE! Which meant that the service wasn't running at all.

I then tried running the following command manually: sudo /usr/bin/node /opt/Web_Proxy/proxy.js 8080 2222 which generated a SyntaxError: "Unexpected token "Const { Exit }"

Much Googling told me earlier versions of node.js would do that.  Found out that, somehow, I had version (gasp) 4 installed for some reason! My other instances were running 8.10.0, so that had to be the culprit.  Much more Googling told me how to update it to the latest version (15.4.0 as of this writing):

First, install npm: sudo apt-get install npm
Then install n, a node version manager: sudo npm install -g n
Then install the latest version of node: sudo n latest
If the installer changed the path from what's specified in the webproxy service call, change it back with "PATH=$PATH"
Verify that node was truly updated with: node -v
Try running the service manually: sudo /usr/bin/node /opt/Web_Proxy/proxy.js 8080 2222
If you still get the same error, you might have to forcibly copy the newer binary to where the webproxy expects it to be: sudo cp /usr/local/n/versions/node/15.4.0/bin/node /usr/bin/node
Try running the service manually again.  If you get a "cannot find module "ws" " error, then do this: cd /opt/Web_Proxy/ and then install the ws module with sudo npm install ws
Try running the service manually again.  It should now run with no errors.  Control C out of it.  You're almost done.
Finally, start the service properly: sudo systemctl start webproxy.service

Voila: RX Monitor audio AT LAST!


Re: digital transmit overtime

Steve N4IRS
 

Patrick,
Which TOT are you adjusting? Are you adjusting the TOT on the USRP node or the ASL TX? The TOT controls the TX not the RX. Just a thought.

Steve

On 12/9/20 5:55 AM, Patrick Perdue wrote:
Hi Steve:

Thanks. Yeah, I thought it should work the same as any other channel driver, so I changed it to a ridiculously low number (10000), and transmissions over 10 seconds across the bridge still passed after rpt reload, at least from digital to analog. I didn't test in the other direction.






Re: DVSwitch Dashboard Web Port

Steve N4IRS
 

Is lightttpd running?
systemctl status lighttpd and/or
ps ax | grep lighttpd

On 12/9/20 1:06 PM, Joe, WB3IHY wrote:
On the two working DVSwitch installations, netstat -tnap shows the following line:

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      1376/node

Which is, I assume, the RX Monitor doing its thing.

On the one where I switched lighttpd to port 8888, there is nothing listed with port 8080 anywhere.

Is that what you're looking for or do you need me to post the entire output? If the latter, then I'd need to (ahem) redact a few things in it for security reasons, HI HI.



On the one where I switched the lighttpd port, there is nothing with port 8080 listed.


Re: MMDVM to MMDVM connections ?

Steve N4IRS
 

Agreed, why bother? If what you are trying to do is create a private DMR TG, you can use HBlink to create a DMR Master. Insert it where you have internet on your diagram.

On 12/9/20 5:47 PM, Gerry Filby wrote:
Hi Folks,

Is it possible to have a private connection using MMDV/Analog_Bridge ?

Analog HT1 <> AllStar1 <> Analog_Bridge <> MMDVM_Bridge <> [Internet] <> MMDV_Bridge <> Analog_Bridge <> AllStar2 <> HT2

("Why bother ?" - what's the point of going through the digital mode - just go AllStar to AllStar ?)

Or would one have to use a temporary Talk Group ?

Best,
Gerry.
W6WNG

2181 - 2200 of 9882