-
Notifications
You must be signed in to change notification settings - Fork 852
Cluster can not start after crashes #7293
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
Comments
there should not be any permission issues, cuz the cluster is start as root account. |
Just so we get a more complete picture: Is this only happening to the one agent or to all services and all machines?
and share the resulting archive with us? Kind regards, |
Hi Kaveh, I have checked and it should be OK for us to share. node1.tar.gz Please have a look with these files. Cheers, |
Hi @pingpongballs, thanks for providing the logs. From what I can tell, it seems we're having trouble changing the memory-mapped protections on the file. We've seen this before with certain fileystems, or with certain mount options (in particular, |
Hi Daniel, Thanks for the response. We are using the "noexec". Here is the output: Cheers |
@pingpongballs Would it be possible to remount without the |
Hi Daniel, Thanks for your direction. after i remount without "noexec" and now we can join back the downed node. Makes sense to me now, there are some binaries within the db folders. Resolved this issue. Cheers |
Uh oh!
There was an error while loading. Please reload this page.
My Environment
Problem:
Expected result:
When restart the cluster, should pick up the previous state and continue.
The text was updated successfully, but these errors were encountered: