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

First reboot of omero* instances after updates may fail #71

Open
manics opened this issue Dec 12, 2017 · 2 comments
Open

First reboot of omero* instances after updates may fail #71

manics opened this issue Dec 12, 2017 · 2 comments
Labels
critical

Comments

@manics
Copy link
Contributor

manics commented Dec 12, 2017

As part of the standard deployment all servers are patched the first time and automatically rebooted if there as a kernel upgrade. If omeroreadwrite and omeroreadonly-N are rebooted simultaneously the omeroreadonly-N may hang since they mount omeroreadwrite with NFS, and when omeroreadwrite goes down the mounts are left hanging and never seem to recover, even after the server comes back up. The current solution is to force a hard reboot openstack server reboot --hard omeroreadonly-N

This is related to #68
@manics manics changed the title Fist reboot of omero* nodes after updates fails Fist reboot of omero* instances after updates may fail Dec 12, 2017
@joshmoore joshmoore changed the title Fist reboot of omero* instances after updates may fail First reboot of omero* instances after updates may fail Dec 12, 2017
@joshmoore
Copy link
Member

Also seen in the (rather strewn out) deployment of prod47.

@manics
Copy link
Contributor Author

manics commented Apr 16, 2018

Incidences of this should be reduced by #108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
critical
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joshmoore @manics