-
Notifications
You must be signed in to change notification settings - Fork 216
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
0.62.2 broken (crashes on startup) #40
Comments
as stated at RocketChat/Rocket.Chat#10114 (comment) I was able to run |
I have created a copy of my environment and upgraded from 0.61.2 to 0.62.0 - the server started with no problems. Then I upgraded to 0.62.1 - and it dies at the same point as before:
|
I downgraded again, enabled debug logging in admin view and upgraded to 0.62.2. Similar result:
|
I ran the container with a sleep command, attached a shell and executed "node main.js" in the shell. Same result as above plus one more log line:
|
@micw this is weird.. please try removing your current image and pulling it again ( if after that you end up with same issue, please try using our own image: |
Same with freshly pulled image. With rocketchat/rocket.chat:0.62.2 it works - but that one uses node 8.9.3
|
Since it worked I've created a pull request to force image to use |
looking at @micw logs again I noticed I'll leave this closed and add this new info into RocketChat/Rocket.Chat#10114 so we can keep talking there, as it not seems to be a docker image issue |
@sampaiodiego Seems to be the combination of "OpLog: Disabled" and node 8.10. So the docker workaround might be a good thing until the root cause is fixed. |
Hello,
I got this issue when I switched from 0.61.2 to 0.62.2: RocketChat/Rocket.Chat#10114 (comment)
The cause is a segmentation fault with node js 8.10: nodejs/node#19274
The breaking change is between 0.62.0 and 0.62.1 docker image:
Proposed fix: use node version 8.9 as base image.
The text was updated successfully, but these errors were encountered: