Error setting up duetcontrolserver during upgrade to fw 3.2

chrishamm

It sounds like the apt update was interrupted. Run sudo dpkg --configure -a and check if that resolves it. Note that you will need a different update approach if you are on the unstable feed; unfortunately apt doesn't respect semver when it comes to beta/rc suffixes. I'll check again if I can generate a new dsf package to fix this.

jay_s_uk

@chrishamm we've had the same issue reported by a couple of LPC/STM users when moving from one beta to another.
I'll add that command to our wiki for reference

Klaas B

@chrishamm After sudo dpkg --configure -a I was able to upgrade to fw 3.2 without problems.

Only now the DCS server is not starting, do you have any idea why?

pi@duet3:~ $ sudo systemctl start duetcontrolserver
Job for duetcontrolserver.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status duetcontrolserver.service" and "journalctl -xe" for details.

pi@duet3:~ $ systemctl status duetcontrolserver.service
● duetcontrolserver.service - Duet Control Server
Loaded: loaded (/lib/systemd/system/duetcontrolserver.service; enabled; vendor preset: enabled)
Active: activating (start) since Thu 2021-01-07 17:48:27 CET; 1s ago
Main PID: 2434 (DuetControlServ)
Tasks: 9 (limit: 2063)
CGroup: /system.slice/duetcontrolserver.service
└─2434 /opt/dsf/bin/DuetControlServer

Jan 07 17:48:27 duet3 systemd[1]: Starting Duet Control Server...
Jan 07 17:48:27 duet3 DuetControlServer[2434]: Duet Control Server v3.2.0
Jan 07 17:48:27 duet3 DuetControlServer[2434]: Written by Christian Hammacher for Duet3D
Jan 07 17:48:27 duet3 DuetControlServer[2434]: Licensed under the terms of the GNU Public License Version 3
pi@duet3:~ $

Klaas B

@jay_s_uk I have tried a beta version before so it can be related. I will try a clean stable install and see if I get my board working on fw 3.2

Klaas B

@chrishamm After a new fresh SD card install and upgrade to fw 3.2 and another board update with Bossa I have the same result that the DCS server is not starting.

When i downgrade then to fw 3.1.1 then everything works. So it seems to be a bug in 3.2

chrishamm

@Klaas-B Your log is truncated. Please post the output of journalctl -u duetcontrolserver -f instead.

Klaas B

@chrishamm the log keeps looping so i copied a part of it.

This is from my existing install my fresh install was not able to upgrade to 3.2 after i downgraded it to 3.1.1 even not after the sudo dpkg --configure -a command.

pi@duet3:~ $ journalctl -u duetcontrolserver -f
-- Logs begin at Fri 2021-01-08 11:18:45 CET. --
Jan 08 11:21:57 duet3 DuetControlServer[2342]: Licensed under the terms of the GNU Public License Version 3
Jan 08 11:21:58 duet3 DuetControlServer[2342]: [info] Settings loaded
Jan 08 11:21:59 duet3 DuetControlServer[2342]: [info] Environment initialized
Jan 08 11:22:00 duet3 DuetControlServer[2342]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
Jan 08 11:22:00 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Jan 08 11:22:00 duet3 systemd[1]: Failed to start Duet Control Server.
Jan 08 11:22:00 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Jan 08 11:22:00 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 5.
Jan 08 11:22:00 duet3 systemd[1]: Stopped Duet Control Server.
Jan 08 11:22:00 duet3 systemd[1]: Starting Duet Control Server...
Jan 08 11:22:01 duet3 DuetControlServer[2362]: Duet Control Server v3.2.0
Jan 08 11:22:01 duet3 DuetControlServer[2362]: Written by Christian Hammacher for Duet3D
Jan 08 11:22:01 duet3 DuetControlServer[2362]: Licensed under the terms of the GNU Public License Version 3
Jan 08 11:22:02 duet3 DuetControlServer[2362]: [info] Settings loaded
Jan 08 11:22:03 duet3 DuetControlServer[2362]: [info] Environment initialized
Jan 08 11:22:03 duet3 DuetControlServer[2362]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
Jan 08 11:22:03 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Jan 08 11:22:03 duet3 systemd[1]: Failed to start Duet Control Server.
Jan 08 11:22:04 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Jan 08 11:22:04 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 6.
Jan 08 11:22:04 duet3 systemd[1]: Stopped Duet Control Server.
Jan 08 11:22:04 duet3 systemd[1]: Starting Duet Control Server...
Jan 08 11:22:04 duet3 DuetControlServer[2385]: Duet Control Server v3.2.0
Jan 08 11:22:04 duet3 DuetControlServer[2385]: Written by Christian Hammacher for Duet3D
Jan 08 11:22:04 duet3 DuetControlServer[2385]: Licensed under the terms of the GNU Public License Version 3
Jan 08 11:22:06 duet3 DuetControlServer[2385]: [info] Settings loaded
Jan 08 11:22:06 duet3 DuetControlServer[2385]: [info] Environment initialized
^C
pi@duet3:~ $

chrishamm

@Klaas-B Remove the SD card from your Duet if there is one in it.

Klaas B

@chrishamm I have removed the SD card from my Duet and now it is working. Did not now that the card should not be in there. So the SD card in the duet has no use?

But problem solved, thanks for your help!

chrishamm

@Klaas-B Glad to hear that solved it! The SD card can be used either in the Duet or the Pi but if a Pi is attached no SD card must be present in the Duet.