aprsc 2.1.18: Fixed systemd service files for deb packages

39 views
Skip to first unread message

Heikki Hannikainen

unread,
Jun 9, 2024, 2:50:25 AM6/9/24
to ap...@googlegroups.com

aprsc 2.1.18 is now available.

Upgrading on Debian / Ubuntu:

sudo apt-get update && sudo apt-get upgrade
sudo reboot (to run the new kernel if it was updated)

Upgrading on Fedora:

sudo dnf upgrade
sudo reboot (to run the new kernel if it was updated)

FreeBSD:

http://he.fi/aprsc/down/

Changes in 2.1.18:

* Added the missing aprsc-chroot.service file back which went missing in
2.1.17 when I switched to use the standard dh_installsystemd
debianhelper script for packaging the service files.

If you've upgraded to 2.1.17 on Debian or Ubuntu, do upgrade to 2.1.18 -
otherwise aprsc might not start up after a reboot.

- Hessu

Richard Jannes

unread,
Jun 9, 2024, 7:12:22 AM6/9/24
to aprsc
Since upgrade to 2.1.18, my server won't start up. Anyone else with this issue?

● aprsc.service - APRS-IS server
     Loaded: loaded (/lib/systemd/system/aprsc.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Sun 2024-06-09 12:44:54 CEST; 2s ago
       Docs: http://he.fi/aprsc/,
             man:aprsc(8)
    Process: 20409 ExecStart=/opt/aprsc/sbin/aprsc -u aprsc -t /opt/aprsc -e info -o file -r logs -c etc/aprsc.conf (code=exited, status=1/FAILURE)
   Main PID: 20409 (code=exited, status=1/FAILURE)
        CPU: 22ms


73 PD3RFR


Op zondag 9 juni 2024 om 08:50:25 UTC+2 schreef Heikki Hannikainen:

Heikki Hannikainen

unread,
Jun 9, 2024, 7:14:47 AM6/9/24
to aprsc

Hi,

Check the log file, /opt/aprsc/logs/aprsc.log and the config file
/opt/aprsc/etc/aprsc.conf - the end of the log file should say what's
wrong.

There was one report about the config file aprsc.conf getting replaced
with the default one during upgrade. It didn't happen to me, though, when
I upgraded.

If this is indeed happening, please report which version you're upgrading
from, and which distribution & distro version are you using?

It's probably good advice now to take a backup copy of aprsc.conf before
upgrading.
> --
> You received this message because you are subscribed to the Google Groups "aprsc" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to aprsc+un...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/aprsc/393a5ea6-28f2-4352-a1e2-88b62c4cfab7n%40googlegroups.com.
>
>

- Hessu

Richard Jannes

unread,
Jun 12, 2024, 6:31:56 PM6/12/24
to ap...@googlegroups.com
Hi Hessu, 

Thanks for your reply.. This is in the logfile:

2024/06/09 11:17:04.169291 aprsc[46045:7f7e72ec4040] NOTICE: Starting up version 2.1.18-gce57698, instance id fqqib1us ...
2024/06/09 11:17:04.169384 aprsc[46045:7f7e72ec4040] ERROR: No such configuration file directive: magicbadness
2024/06/09 11:17:04.169412 aprsc[46045:7f7e72ec4040] ERROR: Problem in etc/aprsc.conf at line 124: magicbadness
2024/06/09 11:17:04.169426 aprsc[46045:7f7e72ec4040] CRIT: Initial configuration failed.

Magicbadness makes it clear the config was deleted indeed. Luckily it's not hard to set up again.. So it's up and running again. 

FYI; I upgraded from 2.1.15 to 2.1.18.. I missed some steps I guess..

73 Richard PD3RFR 





Op zo 9 jun 2024 om 13:14 schreef Heikki Hannikainen <he...@hes.iki.fi>:
You received this message because you are subscribed to a topic in the Google Groups "aprsc" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/aprsc/nUPDD_jdfVc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to aprsc+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aprsc/695f5a49-3085-3fc6-e582-2312273f5a4a%40hes.iki.fi.

Christian Barthod

unread,
Jun 13, 2024, 12:00:47 PM6/13/24
to ap...@googlegroups.com
When I upgraded  aprsc on my RPI from 2.1.15 to 2.1.18 I did not met the "aprsc.conf default" issue met on my VPS for the samedi upgrade

Le jeu. 13 juin 2024 à 08:09, Christian Barthod <cbar...@gmail.com> a écrit :

I encountered the same problem after upgrading from 2.1.15 to 2.1.18


Christian Barthod

unread,
Jun 13, 2024, 12:00:52 PM6/13/24
to ap...@googlegroups.com

I encountered the same problem after upgrading from 2.1.15 to 2.1.18


Le jeu. 13 juin 2024 à 00:31, Richard Jannes <rmja...@gmail.com> a écrit :
Reply all
Reply to author
Forward
0 new messages