# Error when updating ASL3 in Cockpit **URL:** \ **Category:** AllStarLink\ **Created:** [September 3, 2026, 3:59pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968 "2026-09-03T15:59:52Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![KC9IPP](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/a87d85/32.png) [@KC9IPP](https://community.allstarlink.org/u/KC9IPP)\ **Post date:** [September 3, 2026, 3:59pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/1 "2026-09-03T15:59:53Z")
When updating ASL3 in Cockpit, I'm receiving the following error: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." How do I run this? Also, what would have caused this error? ---
**Author:** ![KC9IPP](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/a87d85/32.png) [@KC9IPP](https://community.allstarlink.org/u/KC9IPP)\ **Post date:** [September 3, 2026, 4:10pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/2 "2026-09-03T16:10:22Z")
So I ran 'dpkg --configure -a' and that generates the following: kc9ipp@node628802:~ $ sudo dpkg --configure -a Setting up asl3-appliance (2.2.1-1.deb13) ... apache2\_invoke ssl: already enabled apache2\_invoke default-ssl: already enabled apache2\_invoke headers: already enabled apache2\_invoke nocache: already enabled Synchronizing state of apache2.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable apache2 Then the node disconnects. When I attempt to run the update again, I receive the same error as in my first post. ---
**Author:** ![KC9IPP](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/a87d85/32.png) [@KC9IPP](https://community.allstarlink.org/u/KC9IPP)\ **Post date:** [September 4, 2026, 1:54pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/3 "2026-09-04T13:54:43Z")
Nobody with answers? ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 4, 2026, 3:02pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/4 "2026-09-04T15:02:59Z")
Where did you run the `dpkg` command - through Cockpit's console screen or via SSH? If via cockpit, do you have the same experience if you connect directly with SSH? It looks like you're using beta packages and this might be an issue with the 2.2.1-1 beta package of asl3-appliance. ---
**Author:** ![KC9IPP](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/a87d85/32.png) [@KC9IPP](https://community.allstarlink.org/u/KC9IPP)\ **Post date:** [September 4, 2026, 4:21pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/5 "2026-09-04T16:21:38Z")
I ran the dpkg command via Cockpit. Though I tried via SSH direct and that solved the issue and now I can update in Cockpit. Thank you very much for the help! ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 4, 2026, 4:42pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/6 "2026-09-04T16:42:05Z")
Do you have the output? I would like to know if there's a bug in the package or if this is a one-off. ---
**Author:** ![KC9IPP](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/a87d85/32.png) [@KC9IPP](https://community.allstarlink.org/u/KC9IPP)\ **Post date:** [September 4, 2026, 5:05pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/7 "2026-09-04T17:05:17Z")
Yes, below is the output. kc9ipp@node628802:~ $ sudo dpkg --configure -a [sudo] password for kc9ipp: Setting up asl3-appliance (2.2.1-1.deb13) ... apache2\_invoke ssl: already enabled apache2\_invoke default-ssl: already enabled apache2\_invoke headers: already enabled apache2\_invoke nocache: already enabled Synchronizing state of apache2.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable apache2 Warning: ZONE\_ALREADY\_SET: allstarlink success Warning: ALREADY\_ENABLED: echolink success Warning: ALREADY\_ENABLED: 'echolink' already in 'allstarlink' success Setting up asl3-appliance-pi (2.2.1-1.deb13) ... Removed '/etc/systemd/system/timers.target.wants/fallback-ap.timer'. Connection 'asl-fallback-ap' (4ba72861-28dc-4c04-9b7d-fe1db6eb8a1a) successfully deleted. fallback-ap.service is a disabled or a static unit not running, not starting it. fallback-ap.timer is a disabled or a static unit not running, not starting it. Processing triggers for libc-bin (2.41-12+rpt1+deb13u3) ... Processing triggers for man-db (2.13.1-1) ... Processing triggers for hicolor-icon-theme (0.18-2) ... kc9ipp@node628802:~ $ apache2\_invoke ssl: already enabled apache2\_invoke default-ssl: already enabled apache2\_invoke headers: already enabled apache2\_invoke nocache: already enabled Synchronizing state of apache2.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable apache2 Warning: ZONE\_ALREADY\_SET: allstarlink success Warning: ALREADY\_ENABLED: echolink success Warning: ALREADY\_ENABLED: 'echolink' already in 'allstarlink' success Setting up asl3-appliance-pi (2.2.1-1.deb13) ... Removed '/etc/systemd/system/timers.target.wants/fallback-ap.timer'. Connection 'asl-fallback-ap' (4ba72861-28dc-4c04-9b7d-fe1db6eb8a1a) successfully deleted. fallback-ap.service is a disabled or a static unit not running, not starting it. fallback-ap.timer is a disabled or a static unit not running, not starting it. Processing triggers for libc-bin (2.41-12+rpt1+deb13u3) ... Processing triggers for man-db (2.13.1-1) ... Processing triggers for hicolor-icon-theme (0.18-2) ... ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 4, 2026, 5:43pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/8 "2026-09-04T17:43:31Z")
Okay, thanks for providing that. Looks like a one-off. ---
**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\ **Post date:** [September 4, 2026, 10:48pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/9 "2026-09-04T22:48:14Z")
Having a similar issue. Just built a new node, switched to beta to the latest versions. Then today decided to add the Overview metric packages via cockpit. Received a failure message that it failed to complete. Unfortunately I did not screenshot it. Rebooted, then went to bash prompt to try and correct based on AI recommendations. Here is what happens: root@node616530:/home/w2njr# sudo dpkg --audit The following packages are only half configured, probably due to problems configuring them the first time. The configuration should be retried using dpkg --configure or the configure menu option in dselect: asl3-appliance-pi Appliance customization for Debian-based ASL "appliances" root@node616530:/home/w2njr# sudo dpkg --configure asl3-appliance-pi Setting up asl3-appliance-pi (2.2.1-1.deb13) ... Error: unknown connection 'asl-fallback-ap'. Error: cannot delete unknown connection(s): 'asl-fallback-ap'. dpkg: error processing package asl3-appliance-pi (--configure): installed asl3-appliance-pi package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: asl3-appliance-pi root@node616530:/home/w2njr# Maybe this will shed some light. ---
**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\ **Post date:** [September 4, 2026, 10:49pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/10 "2026-09-04T22:49:18Z")
I tried this twice, once while the repo was set for beta, and once again after switching back to main. Same results. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 4, 2026, 11:47pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/11 "2026-09-04T23:47:50Z")
Thanks. That's an error on my part I need to fix in the `postinst` logic. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 4, 2026, 11:59pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/12 "2026-09-04T23:59:02Z")
This was helpful. I was inappropriately restarting the cockpit.socket service which was tearing down your connection mid-update. Fixed in 2.2.1-2. ---
**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\ **Post date:** [September 5, 2026, 12:30am UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/13 "2026-09-05T00:30:04Z")
Just tried it. Updated the two ASL3 appliance packages. Success! Audit passes with no errors reported. Thank you! ---
**Author:** ![KC9IPP](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/a87d85/32.png) [@KC9IPP](https://community.allstarlink.org/u/KC9IPP)\ **Post date:** [September 5, 2026, 11:37pm UTC](https://community.allstarlink.org/t/error-when-updating-asl3-in-cockpit/24968/14 "2026-09-05T23:37:19Z")
Just an update. Today, I received the same error message and issue as above when trying to update another node. Though as above, I was able to resolve the issue by running dkpg via SSH direct (genersted the same output as above). I have four nodes. I'll check and see if I encounter the issue with the other two nodes.