Date   
Re: NWDR14 image release announcement #beta #support

Dave Christensen
 

Thanks for the reply Basil.  I am a real Newbie to DRAWS and Linux but I muddled through the install until I went to setup ARDOP from the web and then later discovered there was a script to do that.  So I am starting over again to do it using the supplied scripts.  Under the getting started web page = "https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Image-getting-started"  there are 5 steps listed and the first three steps have similar and different instructions for creating the SD card and running the configure scripts.  I suspect this is from improving the images since January.  Being a IT person I understand that the Docs come last but I think they should be updated for the current images as they improve and simplify things.  One thing maybe to note would be the inclusion of a note that the default editor for the V14 image is JED.  I have never seen this editor before (Newbie status) and could not save the image when I was installing PAT.  I changed it with the sudo update-alternatives --config editor command to nano and then I was back in familiar territory, although knowing it is JED I can deal with that also now.

What I want to get to is one DRAWS port for VHF packet and the second for HF apps (understanding that ax25 will have to be stopped to switch between them (I think).  I will probably order a second draws for a "Go Kit" when the cases get into the distribution channel.  This one will be a Pi4 based system.  I wish I could help more but my skills in this area only allow to comment how I can break things..

Thanks again to the team.  I have known John Hayes for over 30 years and he is a good friend.

Moderation?

August Johnson
 
Edited

I see that I'm now subject to moderation on my posts. Why is this? Is it because I'm again asking where my early adopter aluminum case is?

August KG7BZ

Re: Kenwood 707, 2m #draws

Douglas KI7LIK
 

Thank you.  draws manager is setup and I put the settings in for the 500 mv setting for the kenwood tm 707.  I am still having the issue with input device and rig control errors.

Re: Kenwood 707, 2m #draws

 


On Thu, Nov 7, 2019, 19:00 Douglas KI7LIK <KI7LIK.AZ@...> wrote:
Under the input device settings, which one should i use?  I can't seem to get the correct one.  Also, how would I adjust the alsa settings manual for the draws?

Re: Kenwood 707, 2m #draws

Douglas KI7LIK
 

Under the input device settings, which one should i use?  I can't seem to get the correct one.  Also, how would I adjust the alsa settings manual for the draws?

Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

I now have a script, chk_gateway.sh, that I would like to see the console output
of.

# To get the script
cd
cd n7nix
git pull

# To run the script
cd rmsgw
sudo su
./chk_gateway.sh

Copy the console output to an email to me.
Thanks.
/Basil n7nix

Basil Gunn <@basil860> writes:

Please read my previous email & do everything that I asked.
/Basil

Craig McVeay <cmcveay@...> writes:

I ran the scripts that you sent and here's what I have.

Here's the output of the ls -sal /usr/local/etc/rmsgw

total 196
4 drwxr-xr-x 4 rmsgw rmsgw 4096 Nov 6 04:11 .
4 drwxr-xr-x 4 root root 4096 Nov 6 04:12 ..
4 -rw-r--r-- 1 rmsgw rmsgw 599 Sep 19 11:04 acihelp
4 -rwxr-xr-x 1 rmsgw rmsgw 2329 Sep 19 11:04 admin-update.sh
4 -rw-r--r-- 1 rmsgw rmsgw 48 Nov 6 04:11 banner
4 -rw-r--r-- 1 rmsgw rmsgw 810 Nov 6 04:11 channels.xml
4 -rw-r--r-- 1 rmsgw rmsgw 2812 Sep 19 11:04 channels.xsd
4 -rw-r--r-- 1 rmsgw rmsgw 154 Nov 6 04:11 gateway.conf
4 -rw-r--r-- 1 rmsgw rmsgw 160 Sep 19 11:04 gateway.conf-dist
12 -rwxr-xr-x 1 rmsgw rmsgw 9191 Sep 19 11:04 getchannel.py
12 -rwxr-xr-x 1 rmsgw rmsgw 9990 Sep 19 11:04 getsysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 6862 Sep 19 11:04 getversionlist.py
4 -rw-r--r-- 1 rmsgw rmsgw 383 Sep 19 11:04 gwhelp
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 hooks
4 -rw-r--r-- 1 rmsgw rmsgw 234 Sep 19 11:04 hosts
12 -rwxr-xr-x 1 rmsgw rmsgw 10929 Sep 19 11:04 mksysop.py
44 -rwxr-xr-x 1 rmsgw rmsgw 42660 Sep 19 11:04 rmsgwchantest
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 stat
4 -rw-rw---- 1 rmsgw rmsgw 539 Sep 19 11:04 sysop-template.xml
4 -rwxr-xr-x 1 rmsgw rmsgw 3182 Sep 19 11:04 testwlapi.sh
12 -rwxr-xr-x 1 rmsgw rmsgw 9795 Sep 19 11:04 updatechannel.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7840 Sep 19 11:04 updatesysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7832 Sep 19 11:04 updateversion.py
4 -rw-rw-r-- 1 rmsgw rmsgw 352 Sep 19 11:04 .version_info
12 -rwxr-xr-x 1 rmsgw rmsgw 8395 Sep 19 11:04 versionlist.sh
4 -rw-rw---- 1 rmsgw rmsgw 864 Sep 19 11:04 winlinkservice.xml


Here's the output of sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10
status for interface ax0 unavailable



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Nov 6, 2019 at 2:00 PM Basil Gunn <@basil860> wrote:


You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus
new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Yes on the gateway request, I've had a gateway running (RMS Packet on a
Windows machine) for a little over a year. If I have that running on the
windows box while I'm setting this up on the DRAWS, could that be a part of
the problem? They are using different radios and antennas so no conflict
there.

I checked and rechecked the entries in the files as you recommended and
they were correct. Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm
getting good at it now). The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last
line still suggests something is wrong. I've verified and double checked
the PW and other information entered and it is correct. Here are the results
:
Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI
2.5.1 Sep 19 2019 (DM26ad)
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0
(145050000 Hz, mode 0)
Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25
udr0 N0CSM-10 reports unavailable
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN
-- not updated
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1
down, 0 updated, 0 errors
Nov 6 04:17:03 draws rmsgw_aci[1580]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1

Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

Please read my previous email & do everything that I asked.
/Basil

Craig McVeay <cmcveay@...> writes:

I ran the scripts that you sent and here's what I have.

Here's the output of the ls -sal /usr/local/etc/rmsgw

total 196
4 drwxr-xr-x 4 rmsgw rmsgw 4096 Nov 6 04:11 .
4 drwxr-xr-x 4 root root 4096 Nov 6 04:12 ..
4 -rw-r--r-- 1 rmsgw rmsgw 599 Sep 19 11:04 acihelp
4 -rwxr-xr-x 1 rmsgw rmsgw 2329 Sep 19 11:04 admin-update.sh
4 -rw-r--r-- 1 rmsgw rmsgw 48 Nov 6 04:11 banner
4 -rw-r--r-- 1 rmsgw rmsgw 810 Nov 6 04:11 channels.xml
4 -rw-r--r-- 1 rmsgw rmsgw 2812 Sep 19 11:04 channels.xsd
4 -rw-r--r-- 1 rmsgw rmsgw 154 Nov 6 04:11 gateway.conf
4 -rw-r--r-- 1 rmsgw rmsgw 160 Sep 19 11:04 gateway.conf-dist
12 -rwxr-xr-x 1 rmsgw rmsgw 9191 Sep 19 11:04 getchannel.py
12 -rwxr-xr-x 1 rmsgw rmsgw 9990 Sep 19 11:04 getsysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 6862 Sep 19 11:04 getversionlist.py
4 -rw-r--r-- 1 rmsgw rmsgw 383 Sep 19 11:04 gwhelp
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 hooks
4 -rw-r--r-- 1 rmsgw rmsgw 234 Sep 19 11:04 hosts
12 -rwxr-xr-x 1 rmsgw rmsgw 10929 Sep 19 11:04 mksysop.py
44 -rwxr-xr-x 1 rmsgw rmsgw 42660 Sep 19 11:04 rmsgwchantest
4 drwxr-xr-x 2 rmsgw rmsgw 4096 Sep 19 11:04 stat
4 -rw-rw---- 1 rmsgw rmsgw 539 Sep 19 11:04 sysop-template.xml
4 -rwxr-xr-x 1 rmsgw rmsgw 3182 Sep 19 11:04 testwlapi.sh
12 -rwxr-xr-x 1 rmsgw rmsgw 9795 Sep 19 11:04 updatechannel.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7840 Sep 19 11:04 updatesysop.py
8 -rwxr-xr-x 1 rmsgw rmsgw 7832 Sep 19 11:04 updateversion.py
4 -rw-rw-r-- 1 rmsgw rmsgw 352 Sep 19 11:04 .version_info
12 -rwxr-xr-x 1 rmsgw rmsgw 8395 Sep 19 11:04 versionlist.sh
4 -rw-rw---- 1 rmsgw rmsgw 864 Sep 19 11:04 winlinkservice.xml


Here's the output of sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10
status for interface ax0 unavailable



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Nov 6, 2019 at 2:00 PM Basil Gunn <@basil860> wrote:


You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus
new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Yes on the gateway request, I've had a gateway running (RMS Packet on a
Windows machine) for a little over a year. If I have that running on the
windows box while I'm setting this up on the DRAWS, could that be a part of
the problem? They are using different radios and antennas so no conflict
there.

I checked and rechecked the entries in the files as you recommended and
they were correct. Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm
getting good at it now). The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last
line still suggests something is wrong. I've verified and double checked
the PW and other information entered and it is correct. Here are the results
:
Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI
2.5.1 Sep 19 2019 (DM26ad)
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0
(145050000 Hz, mode 0)
Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25
udr0 N0CSM-10 reports unavailable
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN
-- not updated
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1
down, 0 updated, 0 errors
Nov 6 04:17:03 draws rmsgw_aci[1580]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1

Thanks,
Craig




Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

 
I ran the scripts that you sent and here's what I have.

Here's the output of the ls -sal /usr/local/etc/rmsgw

total 196
 4 drwxr-xr-x 4 rmsgw rmsgw  4096 Nov  6 04:11 .
 4 drwxr-xr-x 4 root  root   4096 Nov  6 04:12 ..
 4 -rw-r--r-- 1 rmsgw rmsgw   599 Sep 19 11:04 acihelp
 4 -rwxr-xr-x 1 rmsgw rmsgw  2329 Sep 19 11:04 admin-update.sh
 4 -rw-r--r-- 1 rmsgw rmsgw    48 Nov  6 04:11 banner
 4 -rw-r--r-- 1 rmsgw rmsgw   810 Nov  6 04:11 channels.xml
 4 -rw-r--r-- 1 rmsgw rmsgw  2812 Sep 19 11:04 channels.xsd
 4 -rw-r--r-- 1 rmsgw rmsgw   154 Nov  6 04:11 gateway.conf
 4 -rw-r--r-- 1 rmsgw rmsgw   160 Sep 19 11:04 gateway.conf-dist
12 -rwxr-xr-x 1 rmsgw rmsgw  9191 Sep 19 11:04 getchannel.py
12 -rwxr-xr-x 1 rmsgw rmsgw  9990 Sep 19 11:04 getsysop.py
 8 -rwxr-xr-x 1 rmsgw rmsgw  6862 Sep 19 11:04 getversionlist.py
 4 -rw-r--r-- 1 rmsgw rmsgw   383 Sep 19 11:04 gwhelp
 4 drwxr-xr-x 2 rmsgw rmsgw  4096 Sep 19 11:04 hooks
 4 -rw-r--r-- 1 rmsgw rmsgw   234 Sep 19 11:04 hosts
12 -rwxr-xr-x 1 rmsgw rmsgw 10929 Sep 19 11:04 mksysop.py
44 -rwxr-xr-x 1 rmsgw rmsgw 42660 Sep 19 11:04 rmsgwchantest
 4 drwxr-xr-x 2 rmsgw rmsgw  4096 Sep 19 11:04 stat
 4 -rw-rw---- 1 rmsgw rmsgw   539 Sep 19 11:04 sysop-template.xml
 4 -rwxr-xr-x 1 rmsgw rmsgw  3182 Sep 19 11:04 testwlapi.sh
12 -rwxr-xr-x 1 rmsgw rmsgw  9795 Sep 19 11:04 updatechannel.py
 8 -rwxr-xr-x 1 rmsgw rmsgw  7840 Sep 19 11:04 updatesysop.py
 8 -rwxr-xr-x 1 rmsgw rmsgw  7832 Sep 19 11:04 updateversion.py
 4 -rw-rw-r-- 1 rmsgw rmsgw   352 Sep 19 11:04 .version_info
12 -rwxr-xr-x 1 rmsgw rmsgw  8395 Sep 19 11:04 versionlist.sh
 4 -rw-rw---- 1 rmsgw rmsgw   864 Sep 19 11:04 winlinkservice.xml


Here's the output of sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10
status for interface ax0 unavailable



Virus-free. www.avg.com


On Wed, Nov 6, 2019 at 2:00 PM Basil Gunn <basil@...> wrote:

You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

> Basil,
> Yes on the gateway request, I've had a gateway running (RMS Packet on a Windows machine) for a little over a year. If I have that running on the windows box while I'm setting this up on the DRAWS, could that be a part of the problem? They are using different radios and antennas so no conflict there.
>
> I checked and rechecked the entries in the files as you recommended and they were correct. Rebooted the Pi and checked things again with no change.
>
> I made a new image and started the entire config process over (I'm getting good at it now). The results changed just a little.
>
> AX.25 status shows all running and enabled.
>
> tail -f /var/log/rms.debug results are a little different but the last line still suggests something is wrong. I've verified and double checked the PW and other information entered and it is correct. Here are the results
> :
> Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
> Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
> Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 6 04:17:03 draws rmsgw_aci[1580]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
>
> Thanks,
> Craig
>
>




Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

You may have a file permissions problem in the /usr/local/etc/rmsgw
directory. Verify by sending me the console output of:

ls -sal /usr/local/etc/rmsgw

You can solve the problem by running a new script.
# First fix your local git repo

cd
sudo su
chown -R pi:pi n7nix

# Now get the new script

exit
cd
cd n7nix
git pull

# Now run a script that should fix your problem.

cd rmsgw
sudo su
./grouptest.sh

# Verify that the permissions on files in the /usr/local/etc/rmsgw
directory are correct.

ls -sal /usr/local/etc/rmsgw

# And finally test with rmschanstat

sudo -u rmsgw rmschanstat ax25 udr0 N0CSM-10

Please send me all the console output from all of the above commands plus new
entries in file: /var/log/rms.debug

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Yes on the gateway request, I've had a gateway running (RMS Packet on a Windows machine) for a little over a year. If I have that running on the windows box while I'm setting this up on the DRAWS, could that be a part of the problem? They are using different radios and antennas so no conflict there.

I checked and rechecked the entries in the files as you recommended and they were correct. Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm getting good at it now). The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last line still suggests something is wrong. I've verified and double checked the PW and other information entered and it is correct. Here are the results
:
Nov 6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov 6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 6 04:17:03 draws rmsgw_aci[1580]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

Thanks,
Craig

Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

Basil,
  Yes on the gateway request, I've had a gateway running (RMS Packet on a Windows machine) for a little over a year.  If I have that running on the windows box while I'm setting this up on the DRAWS, could that be a part of the problem?  They are using different radios and antennas so no conflict there.

I checked and rechecked the entries in the files as you recommended and they were correct.  Rebooted the Pi and checked things again with no change.

I made a new image and started the entire config process over (I'm getting good at it now).  The results changed just a little.

AX.25 status shows all running and enabled.

tail -f /var/log/rms.debug results are a little different but the last line still suggests something is wrong.  I've verified and double checked the PW and other information entered and it is correct.  Here are the results
:
Nov  6 04:17:02 draws rmsgw_aci[1580]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov  6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov  6 04:17:02 draws rmsgw_aci[1580]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov  6 04:17:02 draws rmsgw_aci[1580]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  6 04:17:02 draws rmsgw_aci[1580]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  6 04:17:03 draws rmsgw_aci[1580]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

Thanks,
Craig

Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

Your ax.25 status looks good and is running properly. You have something
incorrect in your RMS Gateway config. Have you made an authorization
request for an RMS Gateway previously?
https://winlink.org/content/join_gateway_sysop_team_sysop_guidelines

Look at the last line (with port name udr0) in file /etc/ax25/axports
The call sign with SSID (N0CSM-10) you use there must match the entries
in these 2 files:

--> /etc/rmsgw/channels.xml
Line containing <callsign>
This line must have a call sign with SSID ie. N0CSM-10

Also make sure there is a line like this:
<channel name="udr0" type="ax25" active="yes">

The following entry must also match the call sign in /etc/ax25/axports
--> /etc/rmsgw/gateway.conf
Line containing GWCALL=

/Basil

results of tail -f /var/log/rms.debug Nov 5 16:13:35 draws rmsgw_aci[1493]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 5 16:13:35 draws rmsgw_aci[1493]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 5 16:13:37 draws rmsgw_aci[1493]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov 5 16:17:01 draws rmsgw_aci[2457]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov 5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov 5 16:17:01 draws rmsgw_aci[2457]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 5 16:17:01 draws rmsgw_aci[2457]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 5 16:17:02 draws rmsgw_aci[2457]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

Re: Kenwood 707, 2m #draws

Douglas KI7LIK
 

I get much less errors, now I get the following:

1:  Error in Sound Input
       Requested Input audio format is not supported on device.
2:  Rig Control Error
       Hamlib error:  IO error while testing getting current VFO

Please point me in the direction that i need to go now.

Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

Progress is being made.  I started with a fresh copy of the latest image.  I went through the getting started, learned a few things along the way and this is what I am getting now.  I think this is much closer but, still scratching my head a bit.


results of AX.25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: RUNNING and ENABLED
Status for ax25d.service: RUNNING and ENABLED
AX.25 device: ax0 successfully configured with ip: 192.168.1.245
AX.25 device: ax1 successfully configured with ip: 192.168.1.246

Here are the results of ifconfig
ax0: flags=67<UP,BROADCAST,RUNNING>  mtu 255
        inet 192.168.1.245  netmask 255.255.255.255  broadcast 192.168.1.255
        ax25 N0CSM-10  txqueuelen 10  (AMPR AX.25)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ax1: flags=67<UP,BROADCAST,RUNNING>  mtu 255
        inet 192.168.1.246  netmask 255.255.255.255  broadcast 192.168.1.255
        ax25 N0CSM-10  txqueuelen 10  (AMPR AX.25)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5  bytes 20 (20.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.61  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::48a0:e6e2:f867:4eed  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:88:93:0f  txqueuelen 1000  (Ethernet)
        RX packets 573  bytes 70183 (68.5 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 138  bytes 19353 (18.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.59  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::85c7:f539:b08a:58a6  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:dd:c6:5a  txqueuelen 1000  (Ethernet)
        RX packets 172  bytes 28669 (27.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 27  bytes 4402 (4.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



results of tail -f /var/log/rms.debug
Nov  5 16:13:35 draws rmsgw_aci[1493]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  5 16:13:35 draws rmsgw_aci[1493]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  5 16:13:37 draws rmsgw_aci[1493]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov  5 16:17:01 draws rmsgw_aci[2457]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Sep 19 2019 (DM26ad)
Nov  5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov  5 16:17:01 draws rmsgw_aci[2457]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov  5 16:17:01 draws rmsgw_aci[2457]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  5 16:17:01 draws rmsgw_aci[2457]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  5 16:17:02 draws rmsgw_aci[2457]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

It looks like you didn't follow the instructions from the 'Getting
Started Guide' here:
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

You need to follow those instructions specifically:

cd
cd n7nix/config
sudo su
./app_config.sh core

This configures AX.25, Direwolf, systemd and a few other things for you.
Please read the 'Getting Started Guide'

/Basil

Craig McVeay <cmcveay@...> writes:

Basil,
Thank you for the quick reply.

*results of AX.25-status*
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured

It looks like I have to configure the ports so I'll be looking for the
instructions on that part. If it helps, I'll be running an Alinco DR-135T
on one side and an IC-7200 on the other.


*Here are the results of ifconfig*
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:88:93:0f txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.59 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::85c7:f539:b08a:58a6 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:dd:c6:5a txqueuelen 1000 (Ethernet)
RX packets 821 bytes 146045 (142.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 445 bytes 83615 (81.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

73,
Craig

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Nov 4, 2019 at 11:19 AM Basil Gunn <@basil860> wrote:


Did you start AX.25?
cd
cd bin
sudo su
./ax25-start

As user pi or whatever your default user name is please post the console
output of:

ax25-status
and
ifconfig

/Basil

Craig McVeay <cmcveay@...> writes:

Working on getting WINLINK RMS application running on my DRAWS. The
image is up and running and I suspect I am nearly there but, I am a noob to
Linux so I'm stuck. I went through the setup and configuration from N7NIX
and here's where I am now.

Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered
through the HAT, connected to the internet via WiFi.

When I run "tail -f /var/log/rms.debug", I get the following:

Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat
ax25 udr0 N0CSM-10 reports unavailable
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is
DOWN -- not updated
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1
active, 1 down, 0 updated, 0 errors
Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway
ACI 2.5.1 Nov 4 2019 (DM26sf)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0
(145050000 Hz, mode 0)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat
ax25 udr0 N0CSM-10 reports unavailable
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is
DOWN -- not updated
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1
active, 1 down, 0 updated, 0 errors
Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script
/usr/local/etc/rmsgw/updateversion.py failed, status 1

I've tried two cables on each port with the same results. I'm obviously
missing something but I'm not sure what.

Thank you,
Craig
N0CSM


Re: Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

Basil,
  Thank you for the quick reply.

results of AX.25-status
Status for direwolf.service: RUNNING and ENABLED
Status for ax25dev.service: RUNNING and ENABLED
Status for ax25dev.path: RUNNING and ENABLED
Status for ax25-mheardd.service: NOT RUNNING and ENABLED
Status for ax25d.service: NOT RUNNING and ENABLED
AX.25 device: ax0 not configured
AX.25 device: ax1 not configured

It looks like I have to configure the ports so I'll be looking for the instructions on that part.  If it helps, I'll be running an Alinco DR-135T on one side and an IC-7200 on the other.


Here are the results of ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:88:93:0f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.59  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::85c7:f539:b08a:58a6  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:dd:c6:5a  txqueuelen 1000  (Ethernet)
        RX packets 821  bytes 146045 (142.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 445  bytes 83615 (81.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

73,
Craig

Virus-free. www.avg.com


On Mon, Nov 4, 2019 at 11:19 AM Basil Gunn <basil@...> wrote:

Did you start AX.25?
cd
cd bin
sudo su
./ax25-start

As user pi or whatever your default user name is please post the console
output of:

ax25-status
and
ifconfig

/Basil

Craig McVeay <cmcveay@...> writes:

> Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.
>
> Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.
>
> When I run "tail -f /var/log/rms.debug", I get the following:
>
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf)
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
>
> I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.
>
> Thank you,
> Craig
> N0CSM



Re: Help setting up RMS Gateway? #rms #draws

Basil Gunn
 

Did you start AX.25?
cd
cd bin
sudo su
./ax25-start

As user pi or whatever your default user name is please post the console
output of:

ax25-status
and
ifconfig

/Basil

Craig McVeay <cmcveay@...> writes:

Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.

Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.

When I run "tail -f /var/log/rms.debug", I get the following:

Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.

Thank you,
Craig
N0CSM

Re: NWDR14 image release announcement #beta #support

Basil Gunn
 

direwolf is a daemon & is controlled by systemd as is the preferred
method for controlling daemons that usually start from boot.

The scripts to start/stop/status direwolf & the ax.25 interface are:

cd
cd bin
sudo su
./ax25-status
./ax25-start
./ax25-stop

You can also look at the direwolf daemon status like this:

systemctl status direwolf

The icon in the RPi menus for direwolf comes from the standard direwolf
install and should be deleted.

If you have done a core configuration as described in the 'Getting
Started Guide' then the direwolf binary is in directory /usr/local/bin and
the configuration file is in /etc
ie.
/usr/local/bin/direwolf
/etc/direwolf.conf

/Basil


Dave Christensen <dkc2030@...> writes:

I installed NWDR14. I have not spent much time with DRAWS and in fact have no radios hooked up right now (working on that). So this project has been "benchware" for me. I did bring up FLDigi and it looked familiar to my PC version.

When I clicked on Other>Direwolf I get a message "Failed to change to directory "/root" (Permission denied)" I looked at the shortcut properties and see that the working directory is /root. Is this a problem or can it be fixed?

Thanks and 73
Dave - KD7UM

Help setting up RMS Gateway? #rms #draws

Craig McVeay
 

Working on getting WINLINK RMS application running on my DRAWS.  The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck.  I went through the setup and configuration from N7NIX and here's where I am now.

Setup:  DRAWS HAT on RPi 3B+, 32GB Micro SD running headless.  Powered through the HAT, connected to the internet via WiFi.

When I run "tail -f /var/log/rms.debug", I get the following:

Nov  4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov  4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov  4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov  4 2019 (DM26sf)
Nov  4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov  4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov  4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov  4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov  4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1

I've tried two cables on each port with the same results.  I'm obviously missing something but I'm not sure what.

Thank you,
Craig
N0CSM

Re: NWDR14 image release announcement #beta #support

Dave Christensen
 

I installed NWDR14.  I have not spent much time with DRAWS and in fact have no radios hooked up right now (working on that).  So this project has been "benchware" for me.  I did bring up FLDigi and it looked familiar to my PC version.

When I clicked on Other>Direwolf  I get a message "Failed to change to directory "/root" (Permission denied)"   I looked at the shortcut properties and see that the working directory is /root.  Is this a problem or can it be fixed?  

Thanks and 73
Dave - KD7UM

Re: PlymouthD error when running RMSCHANSTAT

Jim Kinter Jr.
 

Thanks again Basil!

Im not quite ready to upgrade everything.
Im currently running Stretch, and dont foresee the available time to install the new version just yet.

But....
You did aim me at the right place for that error.

apt-get purge plymouth*
(I only SSH into this pi, so no need for plymouth)

and a reboot nets :

root@k5ktf-10:~# sudo -u rmsgw rmschanstat ax25 0 K5KTF-10
channel 0 with callsign K5KTF-10 on interface ax0 up

and

sudo -u rmsgw /usr/local/bin/rmsgw_aci
channel 0 with callsign K5KTF-10 on interface ax0 up

and

Nov  3 22:29:29 localhost rmsgw_aci[508]: K5KTF-10 - Linux RMS Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
Nov  3 22:29:29 localhost rmsgw_aci[508]: Channel: K5KTF-10 on 0 (145730000 Hz, mode 0)
Nov  3 22:29:40 localhost updatechannel.py[528]: Posting channel record updates for K5KTF-10...
Nov  3 22:29:41 localhost rmsgw_aci[508]: Channel Stats: 1 read, 1 active, 0 down, 1 updated, 0 errors
Nov  3 22:29:52 localhost updateversion.py[533]: Version update for K5KTF-10 to version 2.5.0 successful.
Nov  3 22:32:53 localhost rmsgw_aci[568]: K5KTF-10 - Linux RMS Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
Nov  3 22:32:53 localhost rmsgw_aci[568]: Channel: K5KTF-10 on 0 (145730000 Hz, mode 0)
Nov  3 22:32:53 localhost rmsgw_aci[568]: Channel Stats: 1 read, 1 active, 0 down, 0 updated, 0 errors

With plymouth* gone, its working now without any complaints.
And it may have been, but throwing those errors falsely?
Dunno, but looks good for now.

Ill remember the upgrades are ready and waiting for when I have some time.

Thanks again!
Jim



At 10:56 AM 11/3/2019, Basil Gunn wrote:

Hi Jim,

We probably should have been posting our conversations over on the Linux
RMS Gateway forum on yahoo groups since this has not much to do with the
udrc. But let's keep going here as I think I know what your problem is.

The plymouthd daemon is the app which provides the graphical "splash"
screen when booting. It is the owner of the console device. I always run
my Linux RMS Gateways headless (without plymouth) so I have never seen
this error before.

The thing that jumps out at me is that you are not using the latest
version of Linux RMS Gateway. During the last transition of Linux
Debian/Ubuntu from Jessie to Buster there were a lot of changes that
broke the RMS Gateway python scripts ie. ifconfig output changed. Those
problems have been fixed in the latest 2.5.1 release of Linux RMS
Gateway which lives here: https://github.com/nwdigitalradio/rmsgw

The other thing that could be wrong are file permissions used by those
scripts. If you have ever run rmschanstat or rmsgw_aci as a user other
than rmsgw it creates files that have incompatible owner:group
permissions. Normally the program rmsgw_aci is run from a crontab owned
by user rmsgw. When testing I recommend running those programs shown
below.  rmsgw_aci is a C program that calls the python script
rmschanstat. If rmschanstat fails, rmsgw_aci will also fail.

sudo -u rmsgw rmschanstat ax25 0 K5KTF-10
sudo -u rmsgw rmsgw_aci

Also check the directory & file permissions for /etc/rmsgw/stat. It
should look similar to the following. Note that user:group is rmsgw:rmsgw

ls -al /etc/rmsgw/stat
total 8
drwxr-sr-x 2 rmsgw rmsgw 4096 Aug 19 20:25 .
drwxr-sr-x 4 rmsgw rmsgw 4096 Aug  5 16:52 ..
-rw-r--r-- 1 rmsgw rmsgw    0 Nov  3 07:19 .channels.udr0
-rw-r--r-- 1 rmsgw rmsgw    0 Nov  1 13:42 cms.winlink.org
-rw-r--r-- 1 rmsgw rmsgw    0 Nov  3 07:19 .version.N7NIX-10


Those HAMS setting up a Linux RMS Gateway using NW Digital Radio RPi
image won't see the problem you are describing because the latest
version of the gateway has been installed on that image. Of course that
doesn't help you much since you are using a TNC-Pi which should work
fine after installing the latest Linux RMS Gateway.

Let me know if this fixes your problem.

/Basil n7nix

Jim Kinter Jr. via Groups.Io <jim@...> writes:

> Thanks Basil.
> Thats what I thought at first (AX not running), but everything I see
> says it is (as "0", not udrX...its a pi/tnc-pi ).
>
> If I use PAT web GUI on this same system (remotely), I can connect to
> other local  RMS servers just fine, so that tells me the pi,
> TNC-Pi,  network, radio, cabling, AX25, etc are all  OK..
> Right?
> So must be something specific to the RMS config? Or the plymouthd error?
>
>
> root@k5ktf-10:~# ax25-status
> -bash: ax25-status: command not found
>
> root@k5ktf-10:~# netstat --ax25
> Active AX.25 sockets
> Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
> *          K5KTF-0    ax0     LISTENING    000/000  0       0
> *          K5KTF-10   ax0     LISTENING    000/000  0       0
>
>
> root@k5ktf-10:~# ifconfig
> ax0: flags=67<UP,BROADCAST,RUNNING>  mtu 256
>          inet 44.128.1.10  netmask 255.0.0.0  broadcast 44.255.255.255
>          ax25 K5KTF-10  txqueuelen 10  (AMPR AX.25)
>          RX packets 1214  bytes 64695 (63.1 KiB)
>          RX errors 0  dropped 0  overruns 0  frame 0
>          TX packets 301  bytes 13346 (13.0 KiB)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> root@k5ktf-10:~# ps -ef |grep ax
> root       410     1  0 Nov01 ?        00:00:13 /usr/bin/axlisten -artc
> root       414     1  0 Nov01 ?        00:00:00 /usr/sbin/ax25d -l
> root      4231  4212  0 07:20 pts/1    00:00:00 grep ax
>
>
> tail /var/log/messages
> Nov  3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10 on 0
> (145730000 Hz, mode 0)
> Nov  3 06:36:01 localhost rmsgw_aci[4112]: /usr/local/bin/rmschanstat
> ax25 0 K5KTF-10 reports unavailable
> Nov  3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10 on 0 is
> DOWN -- not updated
> Nov  3 06:36:01 localhost rmsgw_aci[4112]: Channel Stats: 1 read, 1
> active, 1 down, 0 updated, 0 errors
> Nov  3 07:00:11 localhost updatechannel.py[4149]: Posting channel
> record updates for K5KTF-10...
> Nov  3 07:06:01 localhost rmsgw_aci[4163]: K5KTF-10 - Linux RMS
> Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
> Nov  3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10 on 0
> (145730000 Hz, mode 0)
> Nov  3 07:06:01 localhost rmsgw_aci[4163]: /usr/local/bin/rmschanstat
> ax25 0 K5KTF-10 reports unavailable
> Nov  3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10 on 0 is
> DOWN -- not updated
> Nov  3 07:06:01 localhost rmsgw_aci[4163]: Channel Stats: 1 read, 1
> active, 1 down, 0 updated, 0 errors
>
> root@k5ktf-10:~# sudo -u rmsgw rmschanstat ax25 0 K5KTF-10
> interface with @sbin/plymouthd unavailable
>
> root@k5ktf-10:~# ps -ef |grep plymouth
> root       130     1  0 07:54 ?        00:00:00 @sbin/plymouthd
> --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
> root       644   597  0 09:24 pts/1    00:00:00 grep plymouth
>
> root@k5ktf-10:~# cat /etc/ax25/axports
> #Port    Call           Baud    PacLen  Window  Description
> 0        K5KTF-10       19200   256     7       Radio - 145.730 MHz
>
> root@k5ktf-10:~# cat /etc/ax25/ax25d.conf
> # /etc/ax25/ax25d.conf
> [K5KTF-10 via 0]
> K5KTF-10  * * * * * * L
> K5KTF  * * * * * * L
> default * * * * * * -    rmsgw /usr/local/bin/rmsgw rmsgw -P 0 %U
> # /etc/ax25/ax25d.conf (End)
>
>
> root@k5ktf-10:~# cat /etc/rmsgw/channels.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <rmschannels xmlns="http://www.namespace.org"
>    xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
>    xsi:schemaLocation=" file:///etc/rmsgw/channels.xsd">
>    <channel name="0" type="ax25" active="yes">
>      <basecall>K5KTF</basecall>
>      <callsign>K5KTF-10</callsign>
>      <password>...Im_not_dumb...</password>
>      <gridsquare>EM10bm</gridsquare>
>      <frequency>145730000</frequency>
>      <mode>0</mode>
>      <autoonly>0</autoonly>
>      <baud>1200</baud>
>      <power>50</power>
>      <height>10</height>
>      <gain>0</gain>
>      <direction>0</direction>
>      <hours>24/7</hours>
>      <groupreference>1</groupreference>
>      <servicecode>PUBLIC</servicecode>
>      <statuschecker>
>        /usr/local/bin/rmschanstat $type $name $callsign
>      </statuschecker>
>    </channel>
> </rmschannels>
>
>
> root@k5ktf-10:~# mheard
> Callsign  Port Packets   Last Heard
> W5TQ-4     0         2   Sun Nov  3 09:36:00
> KE5RS-10   0         1   Sun Nov  3 09:35:09
> W5OEM-12   0         1   Sun Nov  3 09:34:29
>
> For some reason Travis County ARES has W5TQ-4 and W5OEM-12 APRS units
> at fixed locations beaconing on 145.73...smh
> KE5RS-10 is another RMS stn on freq that I can work via PAT (system
> it out in workshop, so I cant change freq remotely)
>
> 2019/11/03 09:53:10 Connecting to KE5RS-10 (ax25)...
> 2019/11/03 09:53:11 Connected to KE5RS-10 (AX.25)
> KE5RS -LEAKA- KANode (Since 1996)
> Connected to KE5RS-10 Winlink 2000 RMS
> [WL2K-5.0-B2FWIHJM$]
> ;PQ: 92941613
> CMS via KE5RS >
>  >FF
> FQ
> 2019/11/03 09:53:24 Disconnected.
>
>
> What da heck am I missing?
> (good thing my hair grows back fast else I would be bald by now...)
>
> 73
> Jim
>
>
> At 09:15 AM 11/2/2019, Basil Gunn wrote:
>
>>Jim,
>>
>>An AX.25 interface is most likely not running
>>
>>Look at this document
>> https://github.com/nwdigitalradio/n7nix/blob/master/rmsgw/README.md#testing-the-rms-gateway
>>
>>run ax25-status to confirm it's not running
>>also run these & look for ax0 or ax1
>>
>>netstat --ax25
>>ifconfig
>>
>>then do this
>>
>>cd
>>cd bin
>>sudo su
>>./ax25-start
>>
>>Also you should always run rmschanstat &  rmsgw_aci as user rmsgw like
>>this:
>>
>>sudo -u rmsgw rmschanstat ax25 udr0 K5KTF-10
>>sudo -u rmsgw rmsgw_aci
>>
>>I now see your gateway k5ktf-10 appearing on the Winlink RMSChannels
>>page this morning which I didn't see last night so I assume you are up &
>>running.
>>
>>/Basil
>>
>>Jim Kinter Jr. via Groups.Io <jim@...> writes:
>>
>> > I received a text from one of our locals that my RMS stn hangs
>> when he tries to connect to it.
>> >
>> > When I go to the logs, I get
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: K5KTF-10 - Linux RMS
>> Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0
>> (145730000 Hz, mode 0)
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]:
>> /usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0
>> is DOWN -- not updated
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel Stats: 1 read,
>> 1 active, 1 down, 0 updated, 0 errors
>> >
>> > When I Google the errors, I found a post to test with
>> rmschanstat. When I do that, I get
>> >
>> > root@k5ktf-10:/etc/rmsgw# rmschanstat ax25 0 K5KTF-10
>> > interface with @sbin/plymouthd unavailable
>> >
>> > If I look at WL2K web site/map, I (K5KTF-10) show up fine there.
>> >
>> > I can also use PAT on this Pi to connect to other VHF stations
>> just fine (without using the -10 suffix going out).
>> >
>> > Im at a loss of where to look.
>> >
>> > Thanks
>> > Jim
>> > K5KTF
>> >
>> >
>>
>>
>>
>
>


73
Jim Kinter, Jr. K5KTF
Cedar Park TX
Webmaster
        www.Broadband-Hamnet.org
        www.CTDXCC.org
        www.AustinSummerfest.org
Williamson County ARES #1545
        2010/11/15/16/17/18 Board Member/AEC Special Operations
Travis County ARES
        Member
ARRL
        Field Instructor/Field Examiner/VE Liaison
W5YI VE # 34031E
NWS Skywarn Spotter
Lone Star Spotter Network Member

-. --- / .... .- -... .-.. .- / -.-. .--