-
Notifications
You must be signed in to change notification settings - Fork 85
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
Fluidd can't reach Moonraker #11
Comments
Hi there, The provided Log implies that moonraker can not create its logfile.
Did you modify the docker-compose.yaml in regards to the log volume? -Markus |
Only modified what is on the guide. files on #11 (comment) |
Please upload the configs as files to your reply. |
Changed their extensions as otherwise it wouldn't let me upload them. |
Thanks, your Configs seem to be allright.
|
Identical result:
|
It does not seem to be the logging volume that is causing the issues. Please execute the following commands from within your prind directory.
|
I have noticed I cannot cd to the log volume location:
Which means permission denied. Is this normal under debian raspberry pi? |
The permissions seem to be ok. While developing this stack, I ran into an issue where I had to chown the config directory to uid/gid 1000, otherwise moonraker would not start. It is normal that the user Could you try starting the stack as user |
Did start it as root, had to move compose to /usr/local/lib/docker/cli-plugins, but the outcome is the same:
|
We'll have to look inside the Container to check for permissions.
|
|
Hm, did a full upgrade of my install by switching to bullseye repo (was on buster) and doing apt upgrade. Stack starts ok now and im looking at the fluidd web! Think might be related with this: docker-library/python#674 |
I just pushed a change for Klipper and Moonraker images and rebuilt the most recent images. (8055c18)
|
Great find. |
When starting the stack without the -d option, this is the log:
These last 7 lines are then repeated over and over again.
The text was updated successfully, but these errors were encountered: