e-sailing / openplotter-avnav Goto Github PK

There is an issue for AvNav (wellenvogel/avnav#302) that reports problems if AvNav and OpenCPN are running in parallel.
By defining an own /tmp dir for AvNav (PrivateTmp=yes in the systemd configuration for AvNav) this was solved.
So we should add this to the avnav installer.

There was an issue on AvNav wellenvogel/avnav#161.
It turned out that the AvNav config was completely corrupted.
AvNav now has some internal handling to potentially fall back to a factory default config if it's config is corrupted and there is no "last known good" config.
For OpenPlotter this could become an issue if the user changed the AvNav HTTP port as AvNav would fall back to it's default port - and maybe could not start due to port conflicts.
On OP it could make more sense to give the user a chance to reset the AvNav config by hand (for example if AvNav is not starting any more).
By triggering the OP port check at this point the user could be given a warning on conflicts and an option to change the port settings.

After running sudo apt update and upgrade (as well as postinstall) openplotter info complained about conflicting ports in AvNav.
As it turned out, the newly added avnav updater was setup by the installer with port 8080 (same as viewer)

Setting it manually to default 8085 (as documented) fixed the problem.
As no port settings had been modified before, this appears to be a bug in the install/update process

Hi, https://github.com/wellenvogel/avnav (original developer) just did an update so SignalK charts are supported:

https://www.wellenvogel.net/software/avnav/downloads/release/20201105/fr

More info: wellenvogel/avnav#72 (comment)

I used the e-saling / openplotter installation, how can I upgrade so this new features is enabled?

Hi @e-sailing

Work on OP4 is now in full swing. Should we adapt openplotter-avnav?

Regards
free-x

Hello av.

I just installed this avpackage, it`s webserver defaults to port 8080, and this is allready used by the installer for FlightAware from the new SDR-Plugin. We do have an small Port conflict here:

I managed to edit the /home/pi/avnav/data/avnav_server.xml to use port 8082.
Now the avnav service will start without crashing with "port is allready busy".

This little Problem consists: you call port 8080 in openplotterAvnav.py.
Please consider to change one of the Plugins Port.

Great Work.
Holger

Based on image OP2+moitessier I had to reinstall OP2 + AvNav from scratch as my system was messed up.
AvNav installed nicely with no issues to be found

However AvNav alarm sound command (as predefined in AvNav config) lacks correct permissions.
Alarms are played back on client but not on the pi

pi@BOP2010:/usr/lib/avnav/sounds $ /usr/lib/python3/dist-packages/openplotterAvnav/data/sound.sh 90% waypointAlarm.mp3 
bash: /usr/lib/python3/dist-packages/openplotterAvnav/data/sound.sh: Permission denied
pi@BOP2010:/usr/lib/avnav/sounds $ 

manually granting execute permissions to sound.sh fixed the problem

I installed Avnav and after openning the Browser tells me that the Site can't be found. I did reinstall it but the Issue is still there.