Hello,
since the last update to v0.13.0-148-gd120a313, I’ve been receiving an error message and Klipper is disconnected.
Attached is my moonraker.log.
Sorry for my bad english and for you’re Help.
moonraker.log (1.6 MB)
Hi @Onkel666 ,
Please upload a klippy.log so we can help!
klippy.log (6.7 MB)
Sorry, I forgot…
Can you be a bit more precise: Disconnected from what? From the Printer, from Moonraker, …?
In the web interface, the message appears:
“Moonraker is disconnected from Klipper.”
See Screenshot.
Have you tried to restart the SBC?
yes, but unfortunately no improvement.
Before the last update everything worked perfectly
Have you updated Moonraker and Mainsail as well?
Can be done with KIAUH.
- Reboot the SBC
- Log in via SSH
- Retrieve the klippy.log from
~/printer_data/logs/(should be only a few kilobytes) - Upload here
I’ve been following this but not sure if I can add anything because I simply don’t know anything about your setup.
I’m very surprised nobody has asked you to provide the information that was requested when you put in the following post (namely printer type, main controller board, SBC & klippy.log):
I think you’ll find that by providing the information initially required for a “General Discussion” request, you’ll make the process much more efficient.
Here is the Klippy.log
klippy.log (1.4 KB)
Interesting. It seems something weird is going on.
The log indicates that Klipper is constantly being killed (for whatever reason) at such an early stage that it does not even parse the configuration. Then it is restarted by the service definition.
Before investing a lot of time:
- Backup your configurations.
- Provision the SBC with a fresh Linux installation.
- Update the Linux system.
- Use KIAUH to install Klipper and the minimal setup, such as Moonraker and the web interface.
- Copy back your configuration. Start only with the
printer.cfgfile, then add the rest if Klipper is running.