aprx.pid

[wa6mhz]

ALMOST have it running, got the files installed with that .DEB file (though I can't find where in the file tree it is hidden.

The hold up now seems to be the aprx.pid file
when I had it almost installed before, it was in the /VAR/RUN directory.  and just contained the number 32

I finally got the file into the directory, but the number 32 is evidently wrong!
now it says APRX PID FILE '/Var/run/aprx.pid ' exists, and PROCESSID 32 INDICATED THERE EXISTS TOO, FURTHER INSTANCES CAN ONLY BE RUN FORGROUND!

what is the value for the aprx.pid file?

While I am at it, what is the trick for entering the lat/lon?  I enter mine EXACTLY as shown in examples and it kicks it out!

[wa6mhz]

from what I see on the NET, this is a very common problem.  But I don't see an answer for why.  Evidently the /var/run/
directory is a protected directory and the program cannot write to it. I was able to place some phoney aprx.pid files in it, but it still didn't work.  I then tried making a new directory that COULD be written to /home/pi/aprx/  But STILL wouldn't wirte to it.
hair tearer!!!

[Nagi Punyamurthula]

Hi Pat

wrt lat/lon question: this is what I have for my setup

myloc lat 4440.62N lon 09328.63W  (I pull my location coords from the http://aprs.fi/ site and helps w/ location ambiguity).

 

you might have already tried doing this. But, if not, try running aprx w/ the –v (verbose), -L (log)  –d (debug) command line params (aprx –v –L –d). This will run aprx as a foreground process and will spit out log and other runtime messages on stdout.  Before you run this, you should kill any previous aprx processes by doing “pkill aprx”.

 

When you run in foreground mode, what do you see in error response to the myloc setting ?

 

Not sure if this helps w/ answering your question – but, I hope it does help lead in fwd direction.

--
You received this message because you are subscribed to the Google Groups "Aprx software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kenneth Finnegan]

The deb installs aprx fully configured to run as a service, so once
you set STARTAPRX=yes, (or whatever that flag is called in the
/etc/default/aprx file) it will automatically start when you turn on
the system, which I suspect is happening since you're seeing it get
such a low PID value.

The pid file then tells you the process ID for the currently running
instance. Since it contains the number 32, that indicates that the
last process ran with the ID number of 32. Since there is still a
process running with that ID, odds are that it is that last instance
of aprx still running.

To stop the running instance of aprx, I will usually either use "sudo
service aprx stop" or "sudo killall aprx" When I'm done making
configuration changes, I will start/restart it by running "sudo
service aprx restart"

Aprx has not been written/maintained with consideration for running it
as any user other than root. I recommend always running aprx from a
root shell (sudo -s).

As for problems with your configuration file, feel free to post it in
its entirety for us to review for you.
--
Kenneth Finnegan
http://blog.thelifeofkenneth.com/