#Stuck on “initializing”. Cannot get config from moonraker.

75 messages · Page 1 of 1 (latest)

loud verge
#

I’ve had a series of issues and if I had any I’d be pulling my hair out at this point.

First I was getting internal error on Axes Shaper Calibration, which would just crash the printer and force a restart.

I updated Kalico and Shake and Tune and then started getting an import error for numpy.core.multiarray.

I spent hours messing around trying to update dependencies, roll them back, and reinstall shake and tune.

Now I’m just getting stuck on “initializing” on the web interface and klipper screen is saying cannot get config from moonraker.

Not sure what to do. Would appreciate any help. Not sure if I just have to start from scratch, but I hope not… thanks in advance!

compact imp
#

Reinstalling s n t fixes numpy

#

Download klippy log and see what's at the end.

loud verge
#

How can I get klippy log through ssh?

compact imp
#

Yea. In printer data logs folder.

#

If mainsail is acting wonky

#

tail -50

Followed by the log you wanna see

#

Or nano

loud verge
#

this is what comes up when I do tail -50 klippy.log

#

tail -50 klippy.log
47 | (264.7, 5.0) | (264.7, 25.0)
48 | (269.8, 5.0) | (269.8, 25.0)
49 | (274.9, 5.0) | (274.9, 25.0)
...points 50 through 2499 truncated
bed_mesh: zero_reference_position is (125.00, 125.00)
beacon: loaded fnorm=5108589.90 temp=21.58 amfg=1.176 from nvm
beacon: built tempco model version 1 {'amfg': 1.1762354375115969, 'tcc': -9.319220947859699e-06, 'tcfl': -0.0006038022600923379, 'tctl': 0.0018284385291515352, 'fmin': 5108589.90252018, 'fmin_temp': 21.581714630126953}
Enabling Beacon accelerometer
Selected Beacon accelerometer scale 16g
Sending MCU 'beacon' printer configuration...
Configured MCU 'beacon' (0 moves)
[17:57:18:958241] nevermore-BLE 'nevermore' - connected to controller 28:CD:C1:12:A3:3C
Starting heater checks for extruder
Welcome to Kalico

Kalico is starting an opt-in analytics campaign, collecting anonymous data about our users
Submitted data will contain an anonymized copy of your current configuration, enabled Kalico modules and plugins, and some basic information about the host machine.

ENABLE_TELEMETRY will opt-in to the campaign
DISABLE_TELEMETRY will permanently opt-out

TELEMETRY_EXAMPLE will save a full example of what would be submitted as 'telemetry.json' in your configuration folder

For more information, visit https://kalico.gg/telemetry
Stats 22.1: gcodein=0 mcu: mcu_awake=0.000 mcu_task_avg=0.000000 mcu_task_stddev=0.000000 bytes_write=3698 bytes_read=6779 bytes_retransmit=9 bytes_invalid=0 send_seq=248 receive_seq=248 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=399991408 nhk: mcu_awake=0.000

#

there's a ton more of that type of stuff that's at the end

#

also seeing this in the mainsail-error log

#

2025/08/22 11:18:12 [error] 811#811: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.50.29, server: _, request: "GET /websocket HTTP/1.1", upstream: "http://127.0.0.1:7125/websocket", host: "192.168.50.236"

loud verge
#

ok I'm making some progress... I realized that somehow in kiauh kalico was not selected as my klipper repository. I did that and suddenly I'm in. got an error about the nevermore sensor so I reran the nevermore-controller installation

#

and now I have this error: unknown pin chip name 'probe'

#

and here's the log

#
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/printer.py", line 287, in _connect
    self._read_config()
  File "/home/pi/klipper/klippy/printer.py", line 227, in _read_config
    m.add_printer_objects(config)
  File "/home/pi/klipper/klippy/toolhead.py", line 965, in add_printer_objects
    config.get_printer().add_object("toolhead", ToolHead(config))
                                                ^^^^^^^^^^^^^^^^
  File "/home/pi/klipper/klippy/toolhead.py", line 329, in __init__
    self.kin = mod.load_kinematics(self, config)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/klipper/klippy/kinematics/corexy.py", line 124, in load_kinematics
    return CoreXYKinematics(toolhead, config)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/klipper/klippy/kinematics/corexy.py", line 12, in __init__
    self.rails = [
                 ^
  File "/home/pi/klipper/klippy/kinematics/corexy.py", line 13, in <listcomp>
    stepper.LookupMultiRail(config.getsection("stepper_" + n))
  File "/home/pi/klipper/klippy/stepper.py", line 623, in LookupMultiRail
    rail = PrinterRail(
           ^^^^^^^^^^^^
  File "/home/pi/klipper/klippy/stepper.py", line 424, in __init__
    self.add_extra_stepper(config)
  File "/home/pi/klipper/klippy/stepper.py", line 570, in add_extra_stepper
    pin_params = ppins.parse_pin(endstop_pin, True, True)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/klipper/klippy/pins.py", line 101, in parse_pin
    raise error("Unknown pin chip name '%s'" % (chip_name,))
klippy.pins.error: Unknown pin chip name 'probe'
webhooks client 547494009488: New connection
webhooks client 547494009488: Client info {'program': 'Moonraker', 'version': 'v0.9.3-102-gf20feff'}
[23:42:10:887009] nevermore-BLE 'nevermore' - discovered controller 28:CD:C1:12:A3:3C
[23:42:10:891413] nevermore-BLE 'nevermore' - connected to controller 28:CD:C1:12:A3:3C
#

ok fixed the pin error by resinstalling beacon

#

then got [shaketune] not valid

#

so reinstalled that and now I'm back to printer config failed to load and being stuck on initialize

loud verge
loud verge
#

I hadn’t included the logs themselves bc I didn’t know how to get them but just downloaded WinSCP to grab them. Any chance someone can take a look?

compact imp
#

That Moonraker is too big. Roll.the logs via mainsail then reboot the pi. Then see what happens.

#

Nothing stands out in klipp
y log. What is exact error

loud verge
compact imp
#

Shift F5 work?

loud verge
compact imp
#

Or a private browsing window

loud verge
#

I’ll try that

#

Shift F5 and private window did not work

compact imp
#

Ssh in

systemctl status moonraker

loud verge
#

what's the best way to post the output? it's fairly long

#

well here's what appears to be the error portion of it

#
Aug 23 08:45:07 DoomCube300 python[787]: :{"cs_pin":"PA9","spi_speed":4000000,"spi_software_sclk_pin":"PC6","spi_software_>
Aug 23 08:45:07 DoomCube300 python[787]: [23.3K blob data]
Aug 23 08:45:07 DoomCube300 python[787]: Traceback (most recent call last):
Aug 23 08:45:07 DoomCube300 python[787]:   File "/home/pi/moonraker/moonraker/components/klippy_connection.py", line 205, >
Aug 23 08:45:07 DoomCube300 python[787]:     decoded_cmd = jsonw.loads(data[:-1])
Aug 23 08:45:07 DoomCube300 python[787]:                   ^^^^^^^^^^^^^^^^^^^^^^
Aug 23 08:45:07 DoomCube300 python[787]: msgspec.DecodeError: JSON is malformed: invalid character (byte 131334)
Aug 23 08:45:12 DoomCube300 python[787]: [klippy_connection.py:wait()] - Request 'objects/query' pending: 60.00 seconds
Aug 23 08:45:27 DoomCube300 python[787]: [common.py:build_error()] - JSON-RPC Request Error - Requested Method: printer.ob>
compact imp
#

Should say status active

loud verge
#

it does

compact imp
#

Ok. So did this install ever work?

#

How did you install? Is this mainsailos?

loud verge
#

the original install was done by someone else, it is mainsailos. It was working over there. I brought the printer back home and did some updates to get nevermore-controller working over BT instead of USB. I went to run shake n tune and it kept crashing the machine (not physically)

#

so have since gone down the rabbit hole of trying to update everything. while I was doing that I also swapped the NH36 because the one one there was part of the recall

compact imp
#

If it was me I would back up all configs and reinstall.

#

I have a writeup for it in my profile here.

This way you know you have a clean os and printer stack. Then we upload the config one thing at a time.

loud verge
#

ok yea that was kind of what I was thinking might be the next step

#

I appreciate you taking a look and offering your help. You're always super generous with your time to answer questions, thank you so much!

compact imp
#

No problem. The write-up will make it easy

loud verge
#

Yea I think I followed it a year or so ago when I was building another 2.4

#

Really helpful

loud verge
#

oh i think I see. that's going to automatically be applied by the beacon macro?

loud verge
#

So I got the printer running. a few weird issues to work out. Had to disable the helper.cfg as I was getting an error and homing and QGL worked once and then I did a home all when the print head was at the back corner at the y endstop and the printer crashed into the bed and just kept trying to go down so I had to just cut the power

#

i did a home again when my finger on the switch and it worked fine...

#

otherwise things seem to be working fine, except for the fact that I can't turn the hotend on without getting smoke. can't figure out where the smoke is coming from and I don't see any damage

#

made another post to try to get some help troubleshooting it since I can't just keep the hotend on while tracking down the source of the smoke

#

but tl;dr fresh install and using your config setup worked a treat to at least get things moving

loud verge
#

@compact imp any idea what might be causing this error?

#

Error evaluating 'gcode_macro SQUIGGLY_PURGE:gcode': jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'max_extrude_cross_section'

compact imp
#

You are missing that value in your extruder section

Set it to like a hundred

loud verge
#

ah ok. yea my setup followed your config but I copied values over from my old config to keep what was working on mine still working and missed this variable. I see yours is set to 5

#

why set to 100 in my case?

compact imp
#

Use 5 then.

#

It's just a value you will never hit.

loud verge
#

ah gotcha

#

and what about putting in the pressure advance stuff I see in yours?

#

I know I'll be tuning each filament I use

#

but not sure what the values in the extruder section are for

compact imp
#

You can. I do pa par filament. So that's how I track them.

#

Orca does pa in slicer but i don't want to be bound to orca

loud verge
#

ah ok. I noticed you have a lot of information that I thought lived in the slicer in your config. that makes sense now

#

so do you add everything manually?

compact imp
#

Add what

#

Filament? Yea. There's macros for that.

loud verge
#

Ah ok yea that makes sense now. I was a bit confused about why it was stored in the config but I can see why you’d want to be independent of the slicer

#

I’m going to have to take a closer look at how all those macros work. Now I’m just trying to get something printed lol