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.

Sign up for GitHub

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

Jump to bottom

Executing Boot() more than once in succession causes "Transport endpoint is not connected" #690

Closed
Torxed opened this issue Nov 6, 2021 · 2 comments · Fixed by #691
Closed

Executing Boot() more than once in succession causes "Transport endpoint is not connected" #690

Torxed opened this issue Nov 6, 2021 · 2 comments · Fixed by #691
Labels
bug Something isn't working

Comments

@Torxed
Copy link
Member

Torxed commented Nov 6, 2021

Not sure yet what causes this:

image
@Torxed Torxed added the bug Something isn't working label Nov 6, 2021
@Torxed Torxed added this to the v2.3.0 milestone Nov 6, 2021
@Torxed
Copy link
Member Author

Torxed commented Nov 6, 2021 •
edited
Loading

Still haven't worked out the issues, but by testing the latest code in torxed-fix-690 I get this now:
image

I can't quite figure out why I'm getting Directory tree X is currently busy...

Tested with systemd-run instead of machinectl and I get slightly better error messages (the pic above uses it).
But suspect it might be because I'm not tapping off self.session.stdout properly. But .poll() should take care of it.

@Torxed
Copy link
Member Author

Torxed commented Nov 7, 2021

screenshot

Works, it appears that I was simply dropping out from shutdown now too quickly and there was no reasonable time given to the subsystem to quit before the next call came along.

@Torxed Torxed linked a pull request Nov 7, 2021 that will close this issue
Fixes #690 by Clearing storage['active_boot'] if shutdown was successful #691
Merged
Torxed added a commit that referenced this issue Nov 7, 2021
@Torxed
Fixes #690 by Clearing storage['active_boot'] if shutdown was success…
565464c 
…ful (#691)

* Clear storage variable if shutdown was successful

* Adding shutdown monitoring and debug output.

* It seams systemd-run gets a connection reset from running 'shutdown now', but in a good way - so it doesn't raise any exceptions. Or at least that's what it looks like.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes #690 by Clearing storage['active_boot'] if shutdown was successful archlinux/archinstall
1 participant
@Torxed