# Apt update/upgrade broke my node **URL:** \ **Category:** AllStarLink\ **Created:** [July 2, 2025, 3:52am UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440 "2025-07-02T03:52:53Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![VK6LD](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/7c8e57/32.png) [@VK6LD](https://community.allstarlink.org/u/VK6LD)\ **Post date:** [July 2, 2025, 3:52am UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440/1 "2025-07-02T03:52:53Z")
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](http://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 ---
**Author:** ![VK6LD](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/7c8e57/32.png) [@VK6LD](https://community.allstarlink.org/u/VK6LD)\ **Post date:** [July 2, 2025, 4:54am UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440/2 "2025-07-02T04:54:12Z")
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... ---
**Author:** ![KK6RQ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6rq/32/3511_2.png) [@KK6RQ](https://community.allstarlink.org/u/KK6RQ)\ **Post date:** [July 2, 2025, 5:21am UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440/3 "2025-07-02T05:21:22Z")
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. ---
**Author:** ![VK6LD](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/7c8e57/32.png) [@VK6LD](https://community.allstarlink.org/u/VK6LD)\ **Post date:** [July 2, 2025, 8:38am UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440/4 "2025-07-02T08:38:45Z")
Many thanks @KK6RQ - I usually skip change logs posts to save some time in life! 😆 ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [July 2, 2025, 12:51pm UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440/5 "2025-07-02T12:51:20Z")
Updated packages were released yesterday afternoon that corrected the issue with duplex=2. Please update to [v3.5.4](https://community.allstarlink.org/t/allstarlink-v3-software-updates-release-2025-06-30/23435). ---
**Author:** ![VK6LD](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/7c8e57/32.png) [@VK6LD](https://community.allstarlink.org/u/VK6LD)\ **Post date:** [July 3, 2025, 9:00am UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440/6 "2025-07-03T09:00:07Z")
@WA3WCO Thank you and completed. ---
**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\ **Post date:** [July 6, 2025, 9:00am UTC](https://community.allstarlink.org/t/apt-update-upgrade-broke-my-node/23440/7 "2025-07-06T09:00:11Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.