Config.g not run automatically. MB6HC 3.5.2 - SBC - Bookworm

jay_s_uk

Phaedrux

Did this only begin after updating to 3.5.2?
What was the last version it was working correctly on?
Have you re-run sudo apt update and sudo apt upgrade?

blt3dp

@Phaedrux
It only started after updating to 3.5.2
Last ver I didn't see any issue with was 3.5.1
I'll run apt update and upgrade now

Edit: no change with apt update and upgrade, didn't look to do anything with any duet packages
Edit again: just downgraded to 3.5.1 and it's all back to normal. Happy to re-up to 3.5.2 if there are troubleshooting/solutions to try.

chrishamm

@blt3dp I would've suspected bad permissions but if it works by running M98 P"config.g" there must be something else going on. Could you have a look at the duetcontrolserver journal? If yes, please connect via SSH or open a terminal, then run sudo journalctl -u duetcontrolserver, press Shift+G, and use the arrow keys to look for the last instance where you started the machine but config.g was not run. That should at least show if config.g was requested from the firmware.

blt3dp

@chrishamm
It looks like quite a few of these

Jun 22 21:14:57 delta systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
Jun 22 21:15:00 delta DuetControlServer[554]: Duet Control Server v3.5.2
Jun 22 21:15:00 delta DuetControlServer[554]: Written by Christian Hammacher for Duet3D
Jun 22 21:15:00 delta DuetControlServer[554]: Licensed under the terms of the GNU Public License Version 3
Jun 22 21:15:02 delta DuetControlServer[554]: [info] Settings loaded
Jun 22 21:15:03 delta DuetControlServer[554]: [info] Environment initialized
Jun 22 21:15:03 delta DuetControlServer[554]: [info] Connection to Duet established
Jun 22 21:15:03 delta DuetControlServer[554]: [info] IPC socket created at /run/dsf/dcs.sock
Jun 22 21:15:03 delta systemd[1]: Started duetcontrolserver.service - Duet Control Server.
Jun 22 21:15:07 delta DuetControlServer[554]: [info] Starting macro file config.g on channel Trigger
Jun 22 21:15:08 delta DuetControlServer[554]: [warn] Trigger: Aborting orphaned macro file config.g
Jun 22 21:15:08 delta DuetControlServer[554]: [error] Trigger: Failed to find corresponding state for code ; Configuration file for Duet 3 (firmware version 3), cancellin>
Jun 22 21:15:08 delta DuetControlServer[554]: [info] Aborted macro file config.g
Jun 22 21:15:08 delta DuetControlServer[554]: [warn] SPI connection has been reset
Jun 22 21:15:17 delta DuetControlServer[554]: [info] Starting macro file dsf-config.g on channel SBC
Jun 22 21:15:17 delta DuetControlServer[554]: [info] SBC: Finished macro file dsf-config.g
Jul 04 19:41:02 delta systemd[1]: Stopping duetcontrolserver.service - Duet Control Server...
Jul 04 19:41:02 delta DuetControlServer[554]: [warn] Received SIGTERM, shutting down...
Jul 04 19:41:02 delta DuetControlServer[554]: [info] Application has shut down
Jul 04 19:41:02 delta systemd[1]: duetcontrolserver.service: Deactivated successfully.
Jul 04 19:41:02 delta systemd[1]: Stopped duetcontrolserver.service - Duet Control Server.
Jul 04 19:41:02 delta systemd[1]: duetcontrolserver.service: Consumed 1min 990ms CPU time.

I think specifically these lines

Jun 22 21:15:07 delta DuetControlServer[554]: [info] Starting macro file config.g on channel Trigger
Jun 22 21:15:08 delta DuetControlServer[554]: [warn] Trigger: Aborting orphaned macro file config.g
Jun 22 21:15:08 delta DuetControlServer[554]: [error] Trigger: Failed to find corresponding state for code ; Configuration file for Duet 3 (firmware version 3), cancellin>
Jun 22 21:15:08 delta DuetControlServer[554]: [info] Aborted macro file config.g

chrishamm

@blt3dp Odd, I tried your config.g on a bench setup here but I couldn't reproduce that problem, it came up as expected. Could you please enable debug logging in /opt/dsf/conf/config.json and send me the journalctl log after that once again? That may help me better identify what's going on.

blt3dp

@chrishamm

Definitely, I just reupdated to 3.5.2, here's journalctl for everything thus far today.

dcs_log.txt

blt3dp

@chrishamm

Actually, we can mark this closed. As a test I ended up imaging a new SD card and manually creating all the config files, transplanting the info into them via the editor in DWC (previously I had followed the bookworm upgrade instructions to sftp backup and restore those files)

Now everything is back to normal.
Thanks for looking into it.

droftarts

@blt3dp Okay, maybe an SD card glitch?

Ian

blt3dp

@droftarts

I actually ended up reimaging the original sd card and doing the same manual recreation of the config files and it's been fine so far. I think more permissions or something when doing the image/sftp backup/restore originally.