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?
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.
Nobody with answers?
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.
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!
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.
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) ...
Okay, thanks for providing that. Looks like a one-off.
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.
I tried this twice, once while the repo was set for beta, and once again after switching back to main. Same results.
Thanks. That's an error on my part I need to fix in the postinst logic.
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.
Just tried it. Updated the two ASL3 appliance packages. Success!
Audit passes with no errors reported.
Thank you!