-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moonraker is starting over and over #9
Comments
Hi there, I could not reproduce the described behaviour with the current nightly build, which is 0a2c190 as of writing this comment.
Please also attach your klippy.log and moonraker.log. -Markus |
Thank you for the fast reply. docker exec klipper cat /opt/klipper/.git/HEAD | cut -c 1-7:
docker exec moonraker cat /opt/moonraker/.git/HEAD | cut -c 1-7:
|
Image from moonraker was created on 2022-02-25 03:55:45 (Info from Portainer) |
Moonraker restarting is a symptom of a nonworking klipper process.
This is unusual, as the C code modules are compiled when building the klipper image. prind/docker/klipper/Dockerfile Lines 15 to 16 in df3199f
I started You could try to stop your stack, prune all Images and re-pull them again but this is grasping for straws. |
@Jodameister |
32bit |
Try to run the Image without any volumes or config.
This should yield the following error message, without any mention of C builds.
|
For the sake of testing, I removed the two lines from the klipper dockerfile that are responsible for compiling the C code in my local branch and built an image for
The actual errorcode seems to be the same, but your provided log is missing the line about gcc that is used to compile the modules.
|
I can confirm there is no C-builds error, when I do this:
|
Here is my printer.cfg:
|
This is really strange. The C modules are compiled before the config file is even loaded, so it should should trigger the same error on your system as with starting it through compose. I had to rebuild the current nightly Image for klipper because of an unrelated issue. Would you mind trying to start klipper with the image explicitly set to
Let me know if anything in the klippy.log file changed with the new Image. -Markus |
Is this still relevant @Jodameister ? |
Hello,
the moon raker is starting over and over. The docker runs on a raspy 3B+ with buster. I use the nightly build.
Here are the log:
This is the moonraker.cfg:
The text was updated successfully, but these errors were encountered: