Basic Information:
Printer Model: Ender 3 S1
MCU / Printerboard: STM32F401
Host / SBC: Raspberry Pi 4
klippy.log (28 KB)
Describe your issue:
I haven’t used my 3D printer in a bit, and tried to get into my mainsail webui, but was only seeing a blank screen. I’m able to SSH into my pi and I’m seeing that klipper.service is active (exited). Trying to restart it immediately exits again.
Here’s the output of journalctl -xe -u klipper
pi@mainsail:~ $ journalctl -xe -u klipper
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit klipper.service has finished successfully.
░░
░░ The job identifier is 89.
-- Boot 76a1934cfce949d1a8921c0f717e39e5 --
Jan 14 15:17:17 mainsail systemd[1]: Started Klipper 3D Printer Firmware SV1.
░░ Subject: A start job for unit klipper.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit klipper.service has finished successfully.
░░
░░ The job identifier is 127.
-- Boot 3a040a64fe4c46f6a5acc9d82dc71b17 --
Jan 16 12:52:33 mainsail systemd[1]: Started Klipper 3D Printer Firmware SV1.
░░ Subject: A start job for unit klipper.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit klipper.service has finished successfully.
░░
░░ The job identifier is 111.
And the output of systemctl status klipper
● klipper.service - Klipper 3D Printer Firmware SV1
Loaded: loaded (/etc/systemd/system/klipper.service; enabled; vendor prese>
Active: active (exited) since Thu 2025-01-16 12:52:33 EST; 56min ago
Docs: https://www.klipper3d.org/
Process: 675 ExecStart=/home/pi/klippy-env/bin/python $KLIPPER_ARGS (code=e>
Main PID: 675 (code=exited, status=0/SUCCESS)
CPU: 135ms
Jan 16 12:52:33 mainsail systemd[1]: Started Klipper 3D Printer Firmware SV1.