-
Notifications
You must be signed in to change notification settings - Fork 10.5k
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
Rocketchat not starting when upgrading from 3.7.2 to 3.8.0 #19537
Comments
I had the same issue. A node update to version 12.18.4 fixed the problem for me. |
Confirm @Slupi , made the same experience. |
Same issue here with node 12.19.0 |
Maybe some of you fell into the same pit as me (manual installation on Ubuntu 20.04) - Rocket.Chat doesn't seem to use the system's version of node but instead relies on the Check the output of: As a solution I ended up with symlinking the Edit: This way Rocket.Chat uses node 12.19.0 (system's version) and executing correctly for me. |
I confirm installing the specific version of 12.18.4 through n fixes the problem, which I guess is indeed the listed version. Not sure if we expect compatibility with any other versions. Should I close this or leave it for further investigation? |
I'm on Debian Stretch 9.13, what fixed my issue was installing node 12.18.4 using 'n' by doing: $ sudo n install 12.18.4
$ /usr/local/bin/node --version
v12.18.4 By default, following the install documentation ( https://docs.rocket.chat/installation/manual-installation/debian/ ) had me install NodeJS 12.19.0 |
Yes and no - it install 12.19.0 (current version of node-js supplied through the debian package). Later in the guide the specific version 12.14.0 gets installed (under /usr/local/bin/ - higher preference in the PATH):
As 12.14.0 doesn't seem to be current enough anymore you can either install 12.18.4 (as many did) but 12.19.0 (supplied through the debian package) seems to also be fine:
|
Worked for Ubuntu 18.04 as well. |
Confirming for CentOS 7 running: Then following the standard manual upgrade procedure fixed the issue. |
You're actually right, one would need to edit the tutorial I guess. |
I've proposed a PR to update the manual install doc => https://github.com/RocketChat/docs/pull/1826 |
|
I can't install 12.18.4 with so used this command
|
I'm using node 12.19.1, I'm not able to start the server using command
I also tried to start service via systemd using
I've tried versions Someone can help? |
Did you run |
@irgendwie Yes |
UpdateI've tried node versions using n: every version returns the same error after trying command I've deleted and run npm install between node version change. when I set the env var for MONGO_URL the error gone but the command |
On Debian 10 (buster), as suggested on a previous comment, i've symlink system NJS to local dir : mv /usr/local/bin/node /usr/local/bin/node.old node --version It works : |
My problem was too: first I forgot to set env var for MONGO and second my droplet on digital ocean hasn't enough ram to run the server. I simply stop all processes that was running in droplet, start the server, then I start other proccesses again. |
Without this change, RocketChat does not start anymore with NodeJS 12.14.0. Resolves RocketChat/Rocket.Chat#19537
Docs should be updated now. Thanks for reporting/contributing everyone! 🚀 |
Description:
Rocketchat fails to start after updating from 3.7.2 to 3.8.
Steps to reproduce:
sudo systemctl stop rocketchat
sudo rm -rf /opt/Rocket.Chat
curl -L https://releases.rocket.chat/latest/download -o /tmp/rocket.chat.tgz
tar -xzf /tmp/rocket.chat.tgz -C /tmp
cd /tmp/bundle/programs/server && npm install
sudo mv /tmp/bundle /opt/Rocket.Chat
sudo chown -R rocketchat:rocketchat /opt/Rocket.Chat
sudo systemctl start rocketchat
Expected behavior:
Rocketchat will work.
Actual behavior:
It no longer starts, see logs below.
Server Setup Information:
Client Setup Information
not relevant
Relevant logs:
Nov 14 03:54:53 xxx.eu rocketchat[4845]: /opt/Rocket.Chat/programs/server/node_modules/fibers/future.js:280
Nov 14 03:54:53 xxx.eu rocketchat[4845]: throw(ex);
Nov 14 03:54:53 xxx.eu rocketchat[4845]: ^
Nov 14 03:54:53 xxx.eu rocketchat[4845]: TypeError: AsyncLocalStorage is not a constructor
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at module (server/sdk/index.ts:23:34)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at fileEvaluate (packages/modules-runtime.js:336:7)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at Module.require (packages/modules-runtime.js:238:14)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at Module.moduleLink [as link] (/opt/Rocket.Chat/programs/server/npm/node_module>
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at ee/server/broker.ts:1:80
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at module (ee/server/broker.ts:345:2)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at fileEvaluate (packages/modules-runtime.js:336:7)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at Module.require (packages/modules-runtime.js:238:14)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at Module.moduleLink [as link] (/opt/Rocket.Chat/programs/server/npm/node_module>
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at module (server/main.js:1:8)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at fileEvaluate (packages/modules-runtime.js:336:7)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at Module.require (packages/modules-runtime.js:238:14)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at require (packages/modules-runtime.js:258:21)
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at /opt/Rocket.Chat/programs/server/app/app.js:191678:15
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at /opt/Rocket.Chat/programs/server/boot.js:401:38
Nov 14 03:54:53 xxx.eu rocketchat[4845]: at Array.forEach ()
Nov 14 03:54:53 xxx.eu systemd[1]: rocketchat.service: Main process exited, code=exited, status=1/FAILURE
The text was updated successfully, but these errors were encountered: