Moonraker Warning
[update_manager]: Failed to load extension ratos-configurator: Invalid path for option
install_script in section [update_manager ratos-configurator]: Path /home/pi/ratos-configurator/scripts/setup.sh does not exist14 Replies
ambitious-aqua•13mo ago
When you ssh in, does the file exist according to that path?
no
setup.sh exists in ratos/src/ratos-configurator/scripts Does that mean the update did not execute?
ambitious-aqua•13mo ago
When you go to that scripts folder and type: pwd
What does it show?
It should show the whole path
/home/pi/ratos-configurator/src/scripts is the whole path. I'm not sure how or what created the src path or how to fixi it
Here are all the files in the scr folder
components next.config.mjs pnpm-lock.yaml server
env next-env.d.ts postcss.config.js styles
helpers package.json public tailwind.config.js
hooks pages scripts tsconfig.json
ambitious-aqua•13mo ago
im confused
so /home/pi/ratos-configurator/scripts/ exists?
No. The folder scr exists between ratos-configurator and scripts.
That's not the right path, seems like you checked out a dev branch and not a deployment branch, what exactly did you do to get that warning?
I'm also going to need your RatOS version (you can see that in the mainsail machine tab in the host pane)
v2.02-20-gd131bf25 I update frequently always running RatOS update first. I really would rather not start over but will if you recommend it.
I really would rather not start over but will if you recommend it.Not even close to there yet.
v2.02-20-gd131bf25 I update frequently always running RatOS update first.I was looking for the image version, not the version of the repository. See my screenshot.
Let me make sure i'm understanding you correctly. You did nothing other than update packages through the update manager?
I've had these Moonraker errors for quite some time. Maybe 3 months and several upgrades. I added an Android tablet as a KlipperScreen and had some trouble getting it to run and thought these Moonraker errors could have been the cause. Turns out they were not the problem.
Maybe 3 months and several upgrades.Ah. Well you're getting the error because you changed the branch of the ratos-configurator. I'm trying to find out how/why that happened, because you're not supposed to (it doesn't work, as you know). the fix itself is easy, But to be clear, this doesn't just happen on it's own automatically. It requires user intervention.
Can you give me an example of how I could have changed it? I want to make sure I don't do it again.
Just ran the new updates. No errors. Thanks for your help.
you'd have to ssh into the pi and change the branch
I don't know how that could happen accidentally, that's why i'm asking 😅
np