Checking configuration:
Info: rpt.conf has configuration for: 42215
Info: /etc/asterisk/iax.conf contains no registration lines.
Info: /etc/asterisk/rpt_http_registrations.conf contains 1 registration line(s)
Info: Registrations present for configured node(s): 42215
Info: IP from https://conntest-east1.allstarlink.org/ip reports: 136.49.110.62
Info: IP from https://conntest-west1.allstarlink.org/ip reports: 136.49.110.62
Info: IP from https://conntest-west2.allstarlink.org/ip reports: 136.49.110.62
Info: IP from udp://conntest-east1.allstarlink.org:4570 reports: 136.49.110.62
Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: 136.49.110.62
Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: 136.49.110.62
OK: HTTP IP probes have consensus on the same perceived IP
OK: IAX IP probes have consensus on the same perceived IP
Testing node 42215:
OK: Node registration config is well-formed
OK: Node registration type is HTTP
OK: register.allstarlink.org is reachable (via HTTP)
Error: There is no apparent HTTP registration attempt for node 42215
Info: Stopping node checks due to registration failure
Info: as further information will be unreliable
May 04 11:33:43 Skyline systemd[1]: asterisk.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
May 04 11:33:43 Skyline systemd[1]: asterisk.service: Failed with result 'exit-code'.
May 04 11:33:43 Skyline systemd[1]: Failed to start asterisk.service - Asterisk PBX.
May 04 11:33:43 Skyline systemd[1]: asterisk.service: Consumed 1.135s CPU time.
and, more importantly, after the first boot did you wait until initial batch of package updates completed (something that takes a LONG time on Raspberry Pi's) ?
Are you using the template configuration files that shipped with the install image? or were you using modified configuration files? or configuration files restored from another/older node?
This is from a working test server image that I've been using and just updated. As I have done many times before, I changed the owner, group and home directory, as well as the hostname and hosts files. Then /etc/asterisk and /usr/local/sbin files tailored for the new node. This has always worked in the past. Bookworm is certainly stable.
This was based on a working node (41886). Node, port and node-password edits to /etc/asterisk files shouldn't break it, unless I fat fingered an edit. Where to look is the question and why the [Error: There is no apparent HTTP registration attempt for node 42215] after OK: HTTP IP probes have consensus on the same perceived IP.
[2026-05-04 16:51:29.964] Asterisk 22.8.2+asl3-3.8.3-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2026-03-26 15:35:46 UTC
[2026-05-04 16:51:29.993] NOTICE[1042] loader.c: 70 modules will be loaded.
[2026-05-04 16:51:30.036] NOTICE[1042] cdr.c: CDR simple logging enabled.
[2026-05-04 16:51:30.038] NOTICE[1042] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
[2026-05-04 16:51:30.053] NOTICE[1042] indications.c: Default country for indication tones: us
[2026-05-04 16:51:30.053] NOTICE[1042] indications.c: Setting default indication country to 'us'
[2026-05-04 16:51:30.151] NOTICE[1042] chan_dahdi.c: Ignoring any changes to 'userbase' (on reload) at line 28.
[2026-05-04 16:51:30.151] NOTICE[1042] chan_dahdi.c: Ignoring any changes to 'vmsecret' (on reload) at line 36.
[2026-05-04 16:51:30.151] NOTICE[1042] chan_dahdi.c: Ignoring any changes to 'hasiax' (on reload) at line 40.
[2026-05-04 16:51:30.151] NOTICE[1042] chan_dahdi.c: Ignoring any changes to 'hasmanager' (on reload) at line 48.
[2026-05-04 16:51:30.151] WARNING[1042] chan_dahdi.c: Only FXO signalled channels may belong to a call group
[2026-05-04 16:51:30.151] WARNING[1042] chan_dahdi.c: Only FXO signalled channels may belong to a pickup group
[2026-05-04 16:51:30.222] ERROR[1042] loader.c: Failed to resolve dependencies for app_rpt
[2026-05-04 16:51:30.222] ERROR[1042] loader.c: Required module app_rpt declined to load.
[2026-05-04 16:51:30.222] ERROR[1042] asterisk.c: Module initialization failed. ASTERISK EXITING!
Because you are running 3.8.3 you shouldn't have any DAHDI errors. This suggests issues with your /etc/asterisk/modules.conf file. When exec'ing apt upgrade from pre-3.8.3 versions of ASL we have a .postinst script that updates a few of the configuration files with important changes. The updated files include modules.conf and rpt.conf. If you loaded/restored an older modules.conf file after the packages were updated then you are missing those updates.
You might try sudo apt install --reinstall asl3-asterisk-config
It looks like something in modules.conf is wrong. If I load a much older file, asterisk starts but has some complaints about some of the loaded stuff. Here's the log:
[2026-05-04 18:28:34.029] NOTICE[921] loader.c: 70 modules will be loaded.
[2026-05-04 18:28:34.273] NOTICE[921] cdr.c: CDR simple logging enabled.
[2026-05-04 18:28:34.276] NOTICE[921] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
[2026-05-04 18:28:34.295] NOTICE[921] indications.c: Default country for indication tones: us
[2026-05-04 18:28:34.295] NOTICE[921] indications.c: Setting default indication country to 'us'
[2026-05-04 18:28:34.399] NOTICE[921] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[2026-05-04 18:28:34.415] NOTICE[921] chan_dahdi.c: Ignoring any changes to 'userbase' (on reload) at line 28.
[2026-05-04 18:28:34.415] NOTICE[921] chan_dahdi.c: Ignoring any changes to 'vmsecret' (on reload) at line 36.
[2026-05-04 18:28:34.415] NOTICE[921] chan_dahdi.c: Ignoring any changes to 'hasiax' (on reload) at line 40.
[2026-05-04 18:28:34.415] NOTICE[921] chan_dahdi.c: Ignoring any changes to 'hasmanager' (on reload) at line 48.
[2026-05-04 18:28:34.415] WARNING[921] chan_dahdi.c: Only FXO signalled channels may belong to a call group
[2026-05-04 18:28:34.415] WARNING[921] chan_dahdi.c: Only FXO signalled channels may belong to a pickup group
[2026-05-04 18:28:34.589] WARNING[921] loader.c: Some non-required modules failed to load.
[2026-05-04 18:28:34.624] WARNING[921] loader.c: Module 'res_adsi' has been loaded but may be removed in a future release.
[2026-05-04 18:28:34.658] ERROR[921] loader.c: Failed to resolve dependencies for app_rpt
[2026-05-04 18:28:34.658] ERROR[921] loader.c: app_rpt declined to load.
[2026-05-04 18:28:34.659] WARNING[996] pbx_config.c: users.conf is deprecated and will be removed in a future version of Asterisk
------------------------------
some asterisk commands don't work: No such command 'rpt fun 42215 *997' (type 'core show help rpt fun' for other possible commands).
I suspect that with the correct modules.conf, it will work properly. Did an "update" mess up the modules file?
I copied in an older (several months old with [global] removed) modules.conf then ran: sudo apt install --reinstall asl3-asterisk-config . That seems to have worked.
The newer modules.conf (from today's update) breaks it.
Now that it is working, I wonder if another 'update' will break it ?
I'm going to dd image the working image before I try a check for updates. If there's anything on the development end to catch these problems going forward, that would be really good. This is the second time I've been bit by modules.conf.
We try really hard to minimize the need to make any changes to the configuration files. It's just that this last change (3.8.x, no-DAHDI) was a biggie and a bunch of changes were needed. I've tweaked the .postinst upgrade script to take care of the (2) known issues and that will be included in the next set of packages.
And, since you asked if there's anything that can be done to help catch these problems going forward, we'd love to have more folks try out the "beta" packages when they are announced. The sooner we know about an issue the sooner we can get it resolved (and, hopefully, before we promote the packages to production). We'd also welcome a few more to join our beta team
