-
-
Notifications
You must be signed in to change notification settings - Fork 426
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 not starting after update #352
Comments
Same! |
It has to do with that and with Pip. |
Same! |
This isn't related to #349, its related to an upstream bug introduced by pip. See #351. Edit: wait, you also can't run the install script with sudo. However you will still run into the issue with pip. Also, your log is showing a duplicate section error. Make sure you don't have a section in the config twice. For example, if you have |
same here :( |
thanks @Arksine ! I tried without sudo as well and now removed the extra sections completely. So I guess I/we have to wait until the upstream problem is fixed? |
how we can go back? |
If you haven't run
If you ran the install script with the |
same here |
Thank you so much! This worked for me. I will follow the discussion here and update once pip is fixed. |
In my case: I dont remember run this before: "install-moonraker.sh -r" |
Same with me, restart the pi and it might work. Worked for me. |
Thanx Arksine,temp fix worked for me |
it dont work for me please another solution... |
having the exact same problem here... just comenting so I can follow for the solution. |
same problem |
Same issue here, but doing the SSH commands listed above with a couple restarts got me back to printing. |
I believe I have a workaround. SSH into your machine and run the following:
See the post below if you previously ran If you haven't installed the policykit rules you may want to go ahead and do so now:
Please respond with feedback if this worked for you. Thanks, and I apologize for the downtime here. |
Also, if you previously ran the install script with
|
This worked for me, thanks! |
Including the previous step, this part ultimately worked for me, thank you! |
This also works for me. |
as already reported in discord seems to work fine 👍 eric the hero of the "invalid doctype sunday" As i said before you need to make a kofi account or similar! |
worked for me, too!! Thank you @Arksine for the fast support |
Thanks, It works ;-) |
it works nice for the support---- |
This worked for me as well, also, pip just got updated, which i upgraded as well. Unsure if it helped or not. |
Saldy doesnt work for me |
@stephbellemare Thanks. FWIW, pip 22.0.1 might cause issues the next time Moonraker needs to install a dependency. I believe that 22.0.2 when released will resolve it, so keep an eye out for it and upgrade pip again when it is released. Previously Moonraker always updated pip before fetching dependencies, however I have disabled that functionality for the time being. |
@wissencat1 Was an error produced during the install process? What is the output from:
|
I had to run it two times now it is working :) |
@Arksine I also just found out pip 22.0 also breaks Klipperscreen. Quite a fun weekend |
Worked for me. |
Worked for me! Thank you :) |
sadly, none of this has worked for me... I have completely removed moonraker, removed the directory, then let kiauh re install moonraker tried |
@marchande If Moonraker is running then its likely an unrelated issue. To keep it separate from this thread, you may open up a new issue with a description, To all: |
@Arksine, ultimatly after getting moonkraker working again, I had to remove and re install mainsali and that fixed my problems, wich is as you said a diferent problem but figured added an update here just incase any one else ends up with the same problem I did.. |
Checking in. Ran the data above through SSH Issue was resolved. Rolled me back to -310. |
It shouldn't have been necessary to roll back. The warnings were due an underlying change in Moonraker, see #349 for details.. The next time you update the warnings will return and you will have to take action to resolve them. Alternatively you can stay at 0.7.1-310 if you would prefer. |
#349 Solved my issue, thanks. |
I want to thank everyone for their feedback in this issue. The pip issue has been resolved upstream, and going forward most users are going to face #349. I'm going go ahead and close this issue to give bump 349 and give it more visibility. |
### this worked for me |
Very nice @JoeDiesAtTheEnd |
I'm the only one who this update has deinstalled/messed up pyton3? I've fixed it with: |
Oh thank you! It was driving me crazy. This fixed my issue with moonraker too! |
I had a mental breakdown trying to fix this, thank you so much |
What happened
After updating klipper, moonraker and system packages today, moonraker doesn't start anymore. Log file shows that dbus is not available.
Tried to use "install-moonraker.sh" by
pi@mainsailos:~/moonraker $ sudo sh ./scripts/install-moonraker.sh
but it also fails with:
###### Installing python virtual environment... ERROR: Could not open requirements file: [Errno 2] No such file or directory: '//scripts/moonraker-requirements.txt'
I also added the two recommended [machine] section options:
`[machine]
provider: none
[update_manager]
enable_packagekit: False
`
Any idea to get it back up running?
Client
Mainsail
Browser
Firefox
How to reproduce
see in description
Additional information
_No response
moonraker.log
_
The text was updated successfully, but these errors were encountered: