Section 'ratos_homing' is not a valid config section

Hi, just came back from vacation and fully updated my RatOS Beta2 installation. I am now getting the error above. 'ratos_homing' is referenced in Ratos/homing.cfg. I am using an euclid probe if that's relevant. How can I fix this?
18 Replies
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
blacksmithforlife
blacksmithforlifeā€¢2y ago
fully updated my RatOS Beta2 installation
what do you mean by this?
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
updated all items in the machine tab
blacksmithforlife
blacksmithforlifeā€¢2y ago
is this a fresh install of beta 2?
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
no, I installed it shortly after it was available running perfectly fine since then
blacksmithforlife
blacksmithforlifeā€¢2y ago
so you upgraded from a alpha version or beta 1 version?
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
I did the whole reimage pi and rebuild printer.cfg thing also updated the packages (which means klipper, ratos, configurator etc) quite regulary, so this must be something from the past 5 days does your homing.cfg also have the "ratos_homing" section?
blacksmithforlife
blacksmithforlifeā€¢2y ago
@miklschmidt you recently changed the homing stuff. Maybe an error?
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
I've got to catch some sleep, leaving this to the grown ups for now šŸ™‚
miklschmidt
miklschmidtā€¢2y ago
This seems to happen for a few people, i think if you do a "update all" the configurator might not be online when RatOS tries to register the extension. This would not be an issue in the next release, but i had hoped to make this change backwards compatible (which it would be if you update RatOS first by itself - one of the things highlighted in the documentation). You can fix it like this:
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
seems the configurator isn't running at all: pi@hephestos:~ $ sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh Updating RatOS device symlinks.. ###### Updating whitelisted commands ###### Installing git hooks ###### Registering klippy extension 'ratos_homing_extension' with the RatOS Configurator... curl: (7) Failed to connect to localhost port 3000: Verbindungsaufbau abgelehnt ERROR: Failed to register ratos_homing_extension. Is the RatOS configurator running? pi@hephestos:~ $ service ratos-configurator start pi@hephestos:~ $ ss -tlpn State Recv-Q Send-Q Local Address:Port Peer Address:Port Process LISTEN 0 128 127.0.0.1:8080 0.0.0.0:* users:(("main",pid=1579,fd=7)) LISTEN 0 511 0.0.0.0:80 0.0.0.0:* LISTEN 0 128 0.0.0.0:7125 0.0.0.0:* users:(("python",pid=599,fd=13)) LISTEN 0 128 0.0.0.0:22 0.0.0.0:* LISTEN 0 128 [::]:22 [::]:* pi@hephestos:~ $ service ratos-configurator status ā— ratos-configurator.service - API Server for Klipper Loaded: loaded (/etc/systemd/system/ratos-configurator.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-02-23 01:02:03 CET; 1s ago Process: 2177 ExecStart=yarn start (code=exited, status=1/FAILURE) Main PID: 2177 (code=exited, status=1/FAILURE) CPU: 38ms
miklschmidt
miklschmidtā€¢2y ago
Are you sure this is with the beta 2 image? Try
cd ~/ratos-configurator
pnpm start
cd ~/ratos-configurator
pnpm start
Yeah the service file is wrong this isn't Beta2
2177 ExecStart=yarn start (code=exited, status=1/FAILURE)
it's supposed to be pnpm start
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
I believe it's beta1, although it shows beta2 in the machine tab
No description
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
so reflash?
miklschmidt
miklschmidtā€¢2y ago
Beta1 is royally fucked, hence the beta2 image šŸ˜„ indeed
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
alright, will do tomorrow. thanks! do you have an estimate for the next beta or the stable release? if that's soon, I'll wait a few days
miklschmidt
miklschmidtā€¢2y ago
I'm aiming for a full release on march 3rd. So far there hasn't been any good reason to release a new beta.
metropolitan-bronze
metropolitan-bronzeOPā€¢2y ago
just to confirm: I reflashed with beta2, restored the configuration and the error is gone
Want results from more Discord servers?
Add your server