Solved Save & Restart No longer works

[Laserbea4k43]

Hello,
When editing my config files and needing to restart klipper or firmware, klipper seems not to be able to connect.
I always have to restart my pi in order to get things working again.
I've attached logs, if anyone can help me out, thanks.

 

[NoGuru]

What happens if you SSH into the Raspberry PI and run sudo service klipper restart ?

 

[garrettwp]

Are you running mainsail or fluidd? What hardware are you running. More details would be helpful.

 

[Laserbea4k43]

Thanks guys,
I didn't realize i'd gotten replies!
It turns out I accidentally commented out a line in the printer.cfg

 

[Laserbea4k43]

Actually it didn't work.
I thought it did, I was wrong.
I'm using an RPi 4 B and BTT Octopus Pro with Fluidd

 

[Laserbea4k43]

What happens if you SSH into the Raspberry PI and run sudo service klipper restart ?

sudo service klipper restart

does work, but I'd hate to have to do that every time I need to restart it.

 

[egar]

I've been having a simiilar issue for a few weeks. I don't remember the exact message, but it is something like "can't connect to MCU". The issue doesn't happen every time I save and restart, but it does happen the majority of the time. The only way to restore operations is a full restart of the Raspberry PI. I have a suspicion that a recent update to Moonraker or Klipper may be part of the problem. I've searched Discord for the error message and there seem to be a few people there with similar issues -- mostly beginning in December.

 

[Laserbea4k43]

In the voron discord, the first pinned message in #klipper solved the problem for me(thanks @Dragonkitty)
sudo systemctl disable ModemManager.service then reboot the pi.
Apparently, there are conflicts with klipperScreen.
I’ve been hitting save & restart for fun

 

[egar]

@Laserbea4k43 - thanks for the lead! This sounds like it could be the cause of the issue I've been having. I'll check it out after work today.

 

[Laserbea4k43]

Good Luck!

 

[egar]

That fixed my issues! Thanks again!

BTW, on the KlipperScreen GitHub, they are now recommending using command sudo systemctl mask ModemManager.service as a more "persistent" solution.

Proabably a little bit beyond my understanding, but I'm guessing the masking, which seems to do a redirect, will prohibit the re-enablement of the service during updates/upgrades.

 

[Laserbea4k43]

So far, that works for me if the printer doesn't need it running.
Glad it worked!!

 

[120decibell]

That fixed my issues! Thanks again!

BTW, on the KlipperScreen GitHub, they are now recommending using command sudo systemctl mask ModemManager.service as a more "persistent" solution.

Proabably a little bit beyond my understanding, but I'm guessing the masking, which seems to do a redirect, will prohibit the re-enablement of the service during updates/upgrades.

Correct. It will prevent re-enabling by another process or update.

 

[Laserbea4k43]

@120decibell I didn't see the difference in the command until you'd quoted it! On it now. Thanks

 

[efjotess]

I have the same problem, but the suggested fix didnt work. What else could it be?
Hardware would be Pi5 and Octopus Max EZ.
I can provide more information if needed.

 

[Laserbea4k43]

I have the same problem, but the suggested fix didnt work. What else could it be?
Hardware would be Pi5 and Octopus Max EZ.
I can provide more information if needed.

did you get it working?

 

[efjotess]

Unfortunately not