Apt update/upgrade broke my node

Hi All,

Got an interesting problem - I ran a "sudo apt update" & "sudo apt upgrade" on my ASL3 Debian 12 node yesterday. Node is configured to be a hub - no radio connected.

After the update/upgrade, my node was registering with Allstarlink, but couldn't make any connections inbound or outbound.

When I attempt an outgoing connection from Asterisk CLI (rpt fun 478326 *351077) I get nothing on the CLI.

When I attempt an inbound connection from one of my other nodes (via CLI), I get the following on my node with the issues:

[2025-07-02 11:35:29.875] WARNING[25899][C-00000005]: app_rpt.c:6324 rpt_exec: Cannot find specified system node 478326
== Spawn extension (radio-secure, 478326, 12) exited non-zero on 'IAX2/103.106.91.93:4568-14334'
-- Hungup 'IAX2/103.106.91.93:4568-14334'

The node is registered okay with "rpt show registrations"

When I look at /var/log/asterisk/messages.log I have the following:

[2025-07-02 11:33:54.210] WARNING[25805] loader.c: Module 'res_adsi' has been loaded but may be removed in a future release.
[2025-07-02 11:33:54.217] WARNING[25829] pbx_config.c: users.conf is deprecated and will be removed in a future version of Asterisk
[2025-07-02 11:33:54.447] NOTICE[25849] app_rpt.c: Domain used for DNS node lookup is: nodes.allstarlink.org
[2025-07-02 11:33:54.447] NOTICE[25849] app_rpt.c: Normal Repeater Init 478326
[2025-07-02 11:33:54.448] WARNING[25854] app_rpt/rpt_bridging.c: app_rpt/rpt_bridging.c:376 (dahdi_conf_add) Unable to set conference mode on DAHDI/pseudo-90638483
[2025-07-02 11:33:54.448] WARNING[25854] app_rpt/rpt_bridging.c: Failed to join DAHDI conf (mode: 7)
[2025-07-02 11:33:54.448] ERROR[25854] app_rpt/rpt_bridging.c: app_rpt.c:2788: Failed to add to conference using chan type 0
[2025-07-02 11:33:54.449] WARNING[25854] app_rpt.c: Disabled broken repeater 478326
[2025-07-02 11:35:29.875] WARNING[25899][C-00000005] app_rpt.c: Cannot find specified system node 478326

Any suggestions would be appreciated.

Regards,

Rob...
VK6LD

Done some more investigating and found the following:

With hub node setup as Duplex=2, (This seems the default when selecting radioless hub) I'm getting the not being able to connect issue & errors and also noticing asterisk restarts are also taking much longer than usual.

I change to type Duplex=0 and full duplex selected, problem goes away.

Interesting to do some more testing, but if anyone else has similar issues, would be good to hear your solutions.

Regards,

Rob...

Keep reading..... yesterday's update broke all duplex=2 nodes (like me!); run apt update/upgrade again and it'll be fixed. The announcement is over in the Announcements section.

Many thanks @kk6rq - I usually skip change logs posts to save some time in life! :laughing:

1 Like

Updated packages were released yesterday afternoon that corrected the issue with duplex=2. Please update to v3.5.4.

1 Like

@WA3WCO Thank you and completed.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.