SV08 unexpected message and Klipper will not restart -- No section: 'Variables'

Sovol SV08
1

First , looks like 2 people with SV06 had the same issue, but i did not see a resolution ?

After a successful ABS print I attempted to send a new ABS print to the SV08 using Orca and Mainsail as usual.
The Slicer was connected and was sending the Gcode to the printer when it issued an error that was nearly a full page.
I shut down and then power on the printer, the Panda screen came up with the above error.
When I reopened Mainsail i get this on the UI.

No section: ‘Variables’

Once the underlying issue is corrected, use the “RESTART”
command to reload the config and restart the host software.
Printer is halted

Tried restarting same error, researched and found advice to check all the bables , so I dropped off the bottom and made sure its was all seating OK. reconnected power, still same message.

Notice a pop up error that says
"
Moonraker reports: DISCONNECTED

Mainsail
Moonraker
Klipper
Moonraker can’t connect to Klipper!

Please check if the Klipper service is running and klippy_uds_address is correctly configured in the moonraker.conf.

klipper
v0.12.0-0 > v0.12.0-6
"

The following is the extract from the moonracker.log
"
2025-03-28 07:17:26,163 [application.py:log_request()] - 101 GET /websocket?token=Z7PQ75MEB6TDRLVVIZMSYS66H7N3BIFP (127.0.0.1) [TRUSTED_USER] 4.47ms
2025-03-28 07:17:26,164 [websockets.py:open()] - Websocket Opened: ID: 281472862615248, Proxied: False, User Agent: , Host Name: 127.0.0.1
2025-03-28 07:17:26,749 [file_manager.py:get_file_list()] - Updating File List …
2025-03-28 07:17:27,253 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
2025-03-28 07:17:27,254 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
2025-03-28 07:17:27,255 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
2025-03-28 07:17:27,255 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
2025-03-28 15:36:51,979 [authorization.py:_check_trusted_connection()] - Trusted Connection Detected, IP: 192.168.132.200
2025-03-28 15:36:51,984 [application.py:log_request()] - 101 GET /websocket (192.168.132.200) [TRUSTED_USER] 8.93ms
2025-03-28 15:36:51,985 [websockets.py:open()] - Websocket Opened: ID: 281472844922448, Proxied: True, User Agent: BBL-Slicer/v01.09.05.51 (light) Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 Edg/107.0.1418.52, Host Name: 192.168.132.82
2025-03-28 15:36:51,989 [websockets.py:_handle_identify()] - Websocket 281472844922448 Client Identified - Name: mainsail, Version: 2.13.2, Type: web
2025-03-28 15:37:10,571 [klippy_connection.py:_on_connection_closed()] - Klippy Connection Removed
2025-03-28 15:37:11,841 [klippy_connection.py:_do_connect()] - Klippy Connection Established
2025-03-28 15:37:14,131 [klippy_connection.py:_request_initial_subscriptions()] - Webhooks Subscribed
2025-03-28 15:37:14,134 [klippy_connection.py:_request_initial_subscriptions()] - GCode Output Subscribed
2025-03-28 15:37:14,138 [klippy_connection.py:_check_ready()] -
No section: ‘Variables’

Once the underlying issue is corrected, use the “RESTART”
command to reload the config and restart the host software.
Printer is halted

2025-03-28 15:37:14,663 [file_manager.py:get_file_list()] - Updating File List …
2025-03-28 15:37:15,134 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
2025-03-28 15:37:15,135 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
2025-03-28 15:37:15,136 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
2025-03-28 15:37:15,137 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: server.files.metadata, Code: -32601, Message: Metadata not available for
"

I am out off ideas as to what went wrong after a successful print ?

2

So thank you all for the replies Sovol CS, I was dumb founded with the amount off response.
I wonder if you all realize that if you want repeat customers , you really should put in some effort on at least a token reply…

PS
I did solve my issue, by getting rid of your customized Kliiper install and followed the the great work put in by Rapettor and Co at GitHub - Rappetor/Sovol-SV08-Mainline: Getting the Sovol SV08 onto mainline Klipper.

3

Posting to help others with what worked on my system for this error.

This same “No section: ‘Variables’” error hit me today, on a Sovol Zero, also a Klipper based system.

My system had run out of disk space mid print. Since I had run out of space in the past I knew where to go and clean. I cleared out some of my bigger older gcode files “~/printer_data/gcodes” and restarted.

After I restarted, I hit the “No section: ‘Variables’” issue. Turns out the “Variables” in the saved_variables.cfg file that the “~/printer_data/config/printer.cfg” file points to was empty, resulting in it’s being seen as a corrupted file and Klipper failed. This file is updated while printing with various variables so it can be used across restarts etc… My system probably ran out of diskspace just prior to it’s being updated. Ref: Commands templates - Klipper documentation

These lines in printer.cfg point to the saved_variables.cfg file location.
[save_variables]
filename: /home/sovol/printer_data/config/saved_variables.cfg

To repair the saved_variables.cfg file, you can modify it either directly from CLI or Mainsail device interface Machine → Selecting “Config” and selecting the saved_variables.cfg file.

Note, default saved_variables.cfg files are probably the same, to be safe be sure to pull from the correct repo. I used Sovol Zero, this thread is about a Sovol SV08.

  1. Backup your local saved_variables.cfg file.
  2. Copy the contents of the original default saved_variables.cfg file from Sovol’s github repo:
    2a. For Sovol Zero “https://github.com/Sovol3d/SOVOL-ZERO/blob/main/sovol/printer_data/config/saved_variables.cfg”
    2b. For Sovol sv08 “https://github.com/Sovol3d/SV08/blob/main/home/sovol/printer_data/config/saved_variables.cfg” 3. Replace the contents of the empty or corrupted saved_variables.cfg.

Then click the restart clipper button, with any luck the system should boot and you are back under way. Once the system looks stable, I’d recommend performing a shutdown and power cycling the system.

The above is a start and hopefully fixes the issue first try, depending on what was being written at the time of running out of space, other deeper issues may show up.

Cheers,
-Mike