Skip to content
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 sometimes has problems with the SSH service. #27

Closed
eliasbakken opened this issue May 14, 2024 · 5 comments
Closed

Moonraker sometimes has problems with the SSH service. #27

eliasbakken opened this issue May 14, 2024 · 5 comments
Labels
bug Something isn't working
Milestone

Comments

@eliasbakken
Copy link
Contributor

Moonraker sometimes has an error on first boot. This seems to be the offending line:
systemctl show -p ActiveState,SubState --value klipper KlipperScreen moonraker ssh
In Fluidd, it will look something like this:
image-ssh

@eliasbakken eliasbakken added the bug Something isn't working label May 14, 2024
@eliasbakken eliasbakken added this to the v1.0.1 milestone May 14, 2024
@eliasbakken
Copy link
Contributor Author

This is the log file from Moonraker as reported by Olle
message(1).txt

@obgr
Copy link
Collaborator

obgr commented May 14, 2024

I just reflashed again.
The error message did not show.

I checked the services recognized by moonraker and ssh was not there.
after a restart of moonraker, ssh made the list.

It may be likely that this issue occur if klipper starts before ssh.

@goeland86
Copy link
Member

It could also be that you need to restart moonraker so the service for definition updates the database with some entries for it to work properly too.

@eliasbakken
Copy link
Contributor Author

I've added a systemctl daemon-reload as a final command in the install script. I'm not sure if that does anything.
Having thought about this it should not make any difference the order in which the services starts. Moonraker checks if the services are running or not, so they should be able to be in any state.

@eliasbakken
Copy link
Contributor Author

I've not seen this issue since the daemon-reload was added. I think we close it for now since it no longer appears. If it persists as a problem, we can reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants