Closed TheAussieTim closed 10 months ago
Clon1998
commented
10 months ago Hey,
Sorry to hear about that experience. However, I do not think that this is related to the companion. To me, it seems like Klipper has a problem connecting since it is in the disconnected state and both, octoeverywhere and companion report connection problems to moonraker.
Therefore, could you also upload the klipper.log file?
TheAussieTim
commented
10 months ago Oh really, that's interesting. I was successfully printing just before making the installation so that's what made me look into this first. Granted I'm not very technical on this side of printing, I can set things up but my troubleshooting game is weak.
Here's the klippy.log, figured it was easier to just put the whole thing on here. klippy.log
Clon1998
commented
10 months ago Thanks. Sadly the logs do not indicate any issue with klipper and therefore my assumption is wrong.
Thus, could you upload all log files (moonraker.log, mobileraker.log, ...). Can you also post the version of Moonraker you are using?
The companion it self is a passive listener except for the startup where it writes some meta data into the printer's database like its version. Besides that, all it does is listening to the same source as the GUIs do.
TheAussieTim
commented
10 months ago Sure thing - it's the latest version I believe, v0.8.0-239-gc4d15e4.
I have also just noticed that I still have Obico running on this thing too, I don't use it anymore - haven't for several months - but I think it seems to still be reaching out. Added the most recent log for that here too, though I don't believe it's conflicting with the operation. mobileraker.log moonraker.log moonraker-obico.log octoeverywhere.log
Clon1998
commented
10 months ago Thanks,
it seems like octoeverywhere is sending a database request close to every second which fails. Therefore, Id suggest to stop octoeverywhere and the mobileraker_companion services and restart moonraker just to see if we get the UIs back working.
Ensure you are connected via SSH to the printer and run:
sudo systemctl stop mobileraker.service
sudo systemctl stop octoeverywhere.service
sudo systemctl restart moonraker.serviceFantastic, that has restored the function again.
OK so I clearly need to focus more on general troubleshooting, thank you so much for your assistance, especially at this time of the year.
Clon1998
commented
10 months ago Fantastic, that has restored the function again.
OK so I clearly need to focus more on general troubleshooting, thank you so much for your assistance, especially at this time of the year.
Awesome, can you do me a favor and start the companion once again (Either via mainsail/Fluidd or by replacing the stop with start in the bash command above)
TheAussieTim
commented
10 months ago Yes, I have restarted the companion again, and testing with a small print job I am now receiving updates on my phone.
I've followed the installation steps to install the companion onto my RPi hosted Klipper/Mainsail (fully updated versions), however now I am not able to load the webgui - I'm stuck on the webpage saying "Initializing" and ERROR in the top of the browser.
I didn't see any errors during the installation. I have also added the companion update info to moonraker.conf
Fortunately I do still have SSH onto the Pi. When I inspect the moonraker.log I'm now seeing a repeat of this:
octoeverywhere.log is repeating this:
And mobileraker.log is showing this after the last restart:
Restarting moonraker and octoeverywhere services hasn't changed the experience unfortunately.
What else can I try? Thank you.