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

0.62.2 broken (crashes on startup) #40

Closed
micw opened this issue Mar 13, 2018 · 9 comments
Closed

0.62.2 broken (crashes on startup) #40

micw opened this issue Mar 13, 2018 · 9 comments

Comments

@micw
Copy link

micw commented Mar 13, 2018

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:

docker run --rm -it library/rocket.chat:0.62.0 node --version
v8.9.4
docker run --rm -it library/rocket.chat:0.62.1 node --version
v8.10.0

Proposed fix: use node version 8.9 as base image.

@sampaiodiego
Copy link
Member

as stated at RocketChat/Rocket.Chat#10114 (comment) I was able to run 0.62.2 .. do you have any additional details?

@micw
Copy link
Author

micw commented Mar 13, 2018

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:

13.3.2018 19:14:39Will load cache for users
13.3.2018 19:14:3929 records load from users
13.3.2018 19:14:39Will load cache for rocketchat_room
13.3.2018 19:14:39180 records load from rocketchat_room
13.3.2018 19:14:39Will load cache for rocketchat_subscription
13.3.2018 19:14:39437 records load from rocketchat_subscription
13.3.2018 19:14:39Will load cache for rocketchat_settings
13.3.2018 19:14:39628 records load from rocketchat_settings
13.3.2018 19:14:42Updating process.env.MAIL_URL
13.3.2018 19:14:42Starting Email Intercepter...

@micw
Copy link
Author

micw commented Mar 13, 2018

I downgraded again, enabled debug logging in admin view and upgraded to 0.62.2. Similar result:

13.3.2018 19:20:55Will load cache for users
13.3.2018 19:20:5529 records load from users
13.3.2018 19:20:55Will load cache for rocketchat_room
13.3.2018 19:20:55180 records load from rocketchat_room
13.3.2018 19:20:55Will load cache for rocketchat_subscription
13.3.2018 19:20:55437 records load from rocketchat_subscription
13.3.2018 19:20:55Will load cache for rocketchat_settings
13.3.2018 19:20:55628 records load from rocketchat_settings
13.3.2018 19:20:57BaseCache ➔ debug rocketchat_settings Falling back observe to model with query: undefined
13.3.2018 19:20:58BaseCache ➔ debug rocketchat_settings Falling back observe to model with query: undefined
13.3.2018 19:20:58Updating process.env.MAIL_URL
13.3.2018 19:20:58Starting Email Intercepter...
13.3.2018 19:20:59BaseCache ➔ debug rocketchat_settings Falling back observe to model with query: { _id: /theme-color-rc/i }

@micw
Copy link
Author

micw commented Mar 13, 2018

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:

Segmentation fault

@sampaiodiego
Copy link
Member

@micw this is weird.. please try removing your current image and pulling it again (docker rmi rocket.chat:0.62.2 and docker pull rocket.chat:0.62.2).

if after that you end up with same issue, please try using our own image: rocketchat/rocket.chat:0.62.2

@micw
Copy link
Author

micw commented Mar 14, 2018

Same with freshly pulled image. With rocketchat/rocket.chat:0.62.2 it works - but that one uses node 8.9.3

14.3.2018 06:23:00➔ +--------------------------------------------------------------+
14.3.2018 06:23:00➔ |                        SERVER RUNNING                        |
14.3.2018 06:23:00➔ +--------------------------------------------------------------+
14.3.2018 06:23:00➔ |                                                              |
14.3.2018 06:23:00➔ |  Rocket.Chat Version: 0.62.2                                 |
14.3.2018 06:23:00➔ |       NodeJS Version: 8.9.3 - x64                            |
14.3.2018 06:23:00➔ |             Platform: linux                                  |
14.3.2018 06:23:00➔ |         Process Port: 3000                                   |
14.3.2018 06:23:00➔ |             Site URL: [...]  |
14.3.2018 06:23:00➔ |     ReplicaSet OpLog: Disabled                               |
14.3.2018 06:23:00➔ |          Commit Hash: 07f0e3f77c                             |
14.3.2018 06:23:00➔ |        Commit Branch: HEAD                                   |
14.3.2018 06:23:00➔ |                                                              |
14.3.2018 06:23:00➔ +--------------------------------------------------------------+

@sampaiodiego
Copy link
Member

Since it worked I've created a pull request to force image to use 8.9.. let's see how it goes

@sampaiodiego
Copy link
Member

looking at @micw logs again I noticed ReplicaSet OpLog: Disabled , so I tried again using this same configuration and it crashed to me as well.

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

@micw
Copy link
Author

micw commented Mar 14, 2018

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants