Re: PlymouthD error when running RMSCHANSTAT
Hi Jim,toggle quoted messageShow quoted text
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
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.
Jim Kinter Jr. via Groups.Io <firstname.lastname@example.org> writes: