Error Log, need help reading them

Sovol SV08
1

I was running a 19 hour long print and the printer suddenly stopped and asked to restart firmware or “something else” that I can’t recall. I SSH’s into the machine and was able to upload the logs directly to a website that analyzed them. The problem is that the way it parses the data it’s very hard for me to see relevant data.

  1. I did not accidentally click Emergency Stop
  2. Power Loss Recovery Lag - it failed to save the print and I’d like to turn it off if it helps with CPU load, it’s all or nothing with the prints for me.
  3. EMI with the toolhead, no idea how to check for this but AI is saying check it - any ideas??
  4. Fan/Thermal issues - I highly suspect this, just need to know it is the problem or not

Click this to go to the results:

  1. I modified the cooling fan for the mainboard, is the mainboard now overheating?
  2. I modified the filament auxiliary feeder to not make as much noise when feeding, is this hanging up the tool head now?
  3. Is there a “better” log parser?
  4. I saw a 79.6C for the host (which I think means the main motherboard) and I know things happen at 80C (I think, I can’t find where that limit is programmed at), did this limit shut me down?
  5. I see a blocking IO Error (Errno 11), did this occur due to over heating?
  6. Would NOT running the 0-3 FPS webcam help things? If so, how can I view the machine without taxing the motherboard?

Original Log links:

moonraker.log (2.0 MB)

2

Something sent an emergency stop to Moonraker. 2 clients were connected (Obico and Mainsail) but the log doesn’t show witch.

Check the Obico dashboard/app notification history around 2026-08-15 21:52 local time — a failure-detection alert would timestamp-match exactly.

As for log parsing, my gotos are:

Sovol cripples klippy.log by omitting the configuration settings so that complicates things.

See also:

For the prompts I used to drill into your logs. BEWARE !! Claude does Hallucinate !! If You feel an answer is sketchy ask for a link to the source.

3

I love you!

Correct me if I am wrong but Obico is for AI detection and nothing else. Should I “disconnect” Obico and just use Moonraker?

4

OK, I’m seeing more now:

12 hours into a 19 hour print and something triggered a shutdown, I’ve not been able to see it yet in the logs but I’m still looking.

I’m seeing that just before shutdown motherboard (host) temp was 77C and throughout the print the temps were in the mid to high 70C range:

image
image1713×303 73.2 KB

Extruder temp was well regulated at 220C so was heater bed at 55C and the toolhead’s motherboard (extra MCU or MCU?) was very solid at 64C.

image
image1763×309 48.3 KB

CPU load and memory were not taxed at all:

image
image1831×420 104 KB

5

Found this towards the end of the 14MB long Klipper.log file, maybe I did accidentally hit the Emergency Stop??:

image
image1906×477 28.3 KB

image
image669×485 60 KB

6

Is there an moonraker-obico log on your machine? It SHOULD admit it if it sent an E-Stop.

I’ve never used Obico but Sovol ships it preinstalled on all their machines. They even autostart the linux service even if you never sign up for Obico

IMO either there is $ and/or user data flowing from Obico > Sovol

If you don’t use it KIAUH will uninstall it. Make sure the service got removed (ask Claud).

Were you in front of your PC when it stopped unexpectedly? Mainsail has a setting to confirm before sending an E-stop… Some think it defeats the purpose of an EMERGENCY stop

7

If I understand correctly Obico is remote monitoring/control from inside or outside your firewall PLUS AI monitoring.

The free teer is useless and I’ve never had a paid subscription so I don’t really know.

8

image
image1893×1019 120 KB

i’m seeing a .cfg file but no log file.