SBC upgrade to 3.4 did not go smooth
-
Yesterday I took the time to upgrade my Duet 3 MB machine from 3.3 to 3.4. Since I am running it in SBC mode (with a Jetson Nano), I upgraded using
apt
. However, due to the order in which the different packages get installed and configured, a dependency arises. At least in my case it did.Here's the therminal output I got:
Setting up duetcontrolserver (3.4.0) ... Configuration file '/opt/dsf/conf/config.json' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** config.json (Y/I/N/O/D/Z) [default=N] ? Y Installing new version of config file /opt/dsf/conf/config.json ... Setting up duetwebserver (3.4.0) ... Configuration file '/opt/dsf/conf/http.json' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** http.json (Y/I/N/O/D/Z) [default=N] ? Y Installing new version of config file /opt/dsf/conf/http.json ... dpkg: error processing package duetwebserver (--configure): installed duetwebserver package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of duetsoftwareframework: duetsoftwareframework depends on duetwebserver (= 3.4.0); however: Package duetwebserver is not configured yet. dpkg: error processing package duetsoftwareframework (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of duetwebcontrol: duetwebcontrol depends on duetsoftwareframework (>= 3.2.0); however: Package duetsoftwareframework is not configured yet. dpkg: error processing package duetwebcontrol (--configure): dependency problems - leaving unconfigured Setting up duettools (3.4.0) ... dpkg: dependency problems prevent configuration of duetpluginservice: duetpluginservice depends on duetsoftwareframework (>= 3.3); however: Package duetsoftwareframework is not configured yet. dpkg: error processing package duetpluginservice (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of reprapfirmware: reprapfirmware depends on duetsoftwareframework (>= 3.2.0); however: Package duetsoftwareframework is not configured yet. dpkg: error processing package reprapfirmware (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already Processing triggers for libc-bin (2.27-3ubuntu1.5) ... Processing triggers for systemd (237-3ubuntu10.53) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for ufw (0.36-0ubuntu0.18.04.2) ... Rules updated for profile 'Nginx HTTP' Rules updated for profile 'Nginx HTTPS' Firewall reloaded Errors were encountered while processing: duetwebserver duetsoftwareframework duetwebcontrol duetpluginservice reprapfirmware E: Sub-process /usr/bin/dpkg returned an error code (1)
-
@nxt-1 It looks like the DuetWebServer package failed to execute the
postinst
script. Can you confirm usingjournalctl
that DWS could be started when the installation occurred? If not, try to disable the service for now and resume the upgrade:sudo systemctl disable duetwebserver sudo apt upgrade duetwebserver duetsoftwareframework duetwebcontrol duetpluginservice reprapfirmware
Perhaps there is something up with your http.json that worked with 3.3 (Kestrel + .NET 5) but not with 3.4 (Kestrel + .NET 6).
-
@chrishamm I can't really provide any more info I am afaid. Even before I posted the original thread, I already fixed the issue with a mixture of --reconfigures and reinstalls. I mainly posted to raise awareness in case more people encountered the issue.