Re: PlymouthD error when running RMSCHANSTAT


Jim Kinter Jr. <jim@...>
 

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

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

Join udrc@nw-digital-radio.groups.io to automatically receive all group messages.