Klipper shutdown due to webhook request(s)
I've posted same in the "Klipper" sub. Recently set up V4 with all config finalized. Starting working through the initial beacon calibration and got a Klipper emergency stop. Is there something in the logs I should be looking for that would ID the problem and provide a clue how to clear it?
I'd appreciate any guidance to finally get this machine rolling.
2 Replies
Extruder max_extrude_ratio=0.266081 mcu 'mcu': Starting serial connect webhooks client 4086023480: New connection webhooks client 4086023480: Client info {'program': 'Moonraker', 'version': 'v0.9.3-0-g71f9e67'} b'Got EOF when reading from device' mcu 'mcu': Timeout on connect mcu 'mcu': Wait for identify_response Traceback (most recent call last): File "/home/pi/klipper/klippy/serialhdl.py", line 68, in _get_identify_data params = self.send_with_response(msg, 'identify_response') File "/home/pi/klipper/klippy/serialhdl.py", line 262, in send_with_response return src.get_response([cmd], self.default_cmd_queue) File "/home/pi/klipper/klippy/serialhdl.py", line 319, in get_response self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock, File "/home/pi/klipper/klippy/serialhdl.py", line 254, in raw_send_wait_ack self._error("Serial connection closed") File "/home/pi/klipper/klippy/serialhdl.py", line 61, in _error raise error(self.warn_prefix + (msg % params)) serialhdl.error: mcu 'mcu': Serial connection closedlooks suspect - maybe a loose usb connection? as well as
2025-02-13 22:41:25,315 [common.py:build_error()] - JSON-RPC Request Error - Requested Method: printer.gcode.script, Code: 400, Message: Shutdown due to webhooks requestso it is trying to access a file and got a "bad request" response @miklschmidt and @Helge Keck what is
printer.gcode.script used for?Thanks for digging into it. I'll check the Pi side, but the USB-C connection at the MoBo is a snug fit.
Swapped out USB-A/USB-C cord Pi to Mobo - no change. Ran RatOS doctor via ssh - no change.
In the event it might help narrow this down Pi is equipped with POE hat - internet via ethernet. No issues logging into pi via ssh.
Bought a new USB cord and I'm getting back into the dashboard. Thanks for the help!