Question: Is there any1 successfully updated Rocketchat from 6.X to 7.X

Community Support
1

Description

Is there any1 already upgraded their workspace from 6.X to 7.X?
Badly need your process to make it work. Im encountering multiple failures and different errors depends on the node versions i installed as version prerequisites.

Server Setup Information

  • Version of Rocket.Chat Server: 6.13.1
  • Operating System: Ubuntu 20.04
  • Deployment Method: Self Hosted | Ubuntu Server
  • Number of Running Instances: 6
  • DB Replicaset Oplog: wiredTiger (oplog Enabled)
  • NodeJS Version: v14.21.3
  • MongoDB Version: 5.0.27
  • Proxy: nginx
  • Firewalls involved:
2

Lots. Probably most have. You are out of support at the end of the month.

No details of how you deployed your server or any errors so no one can help you.

Would suggest you upgrade your Ubuntu though. It is out of standard support and likely Rocket will require a newer OS for dependencies.

Mongo 5+ also needs AVX extensions on your CPU.

Rocket 7+ has different licencing for some versions too eg air gapped.

Read ALL the release notes.

3

Hi reetp,

Thanks for providing some info.
Can you specify the recommended version of system (Ubuntu/Mongodb) for Rocketchat 7.5.1?
Made a clone for my existing server and updated my system to test updating with Rocketchat 7.5.1.
Ubuntu 22.04
Mongodb 6
Node 22.13.1

Below error i got from journal
rocketchat server 7.5.1 unable to start service, showing journalctl log “Apr 16 02:07:46 wa-rocketchat-clone rocketchat[4314]: strict mode: use allowUnionTypes to allow union type keyword at “#/properties/count” (strictTypes)
Apr 16 02:07:46 wa-rocketchat-clone rocketchat[4314]: strict mode: use allowUnionTypes to allow union type keyword at “#/properties/offset” (strictTypes)
Apr 16 02:07:47 wa-rocketchat-clone rocketchat[4314]: strict mode: missing type “object” for keyword “additionalProperties” at “#” (strictTypes)
Apr 16 02:07:47 wa-rocketchat-clone rocketchat[4314]: strict mode: missing type “object” for keyword “properties” at “#” (strictTypes)
Apr 16 02:07:47 wa-rocketchat-clone rocketchat[4314]: strict mode: missing type “object” for keyword “required” at “#/oneOf/0” (strictTypes)
Apr 16 02:07:47 wa-rocketchat-clone rocketchat[4314]: strict mode: missing type “object” for keyword “required” at “#/oneOf/1” (strictTypes)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: packages/core-runtime.js:189
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: throw error;
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: ^
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: Error: /opt/Rocket.Chat.releases/programs/server/npm/node_modules/isolated-vm/out/isolated_vm.node: undefined symbol: _ZN2v815ValueSerializer8Delegate19HasCustomHostObjectEPNS_7Isola>
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Object.Module._extensions..node (node:internal/modules/cjs/loader:1651:18)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.load (node:internal/modules/cjs/loader:1275:32)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.Mp.load (/tools/static-assets/server/runtime.js:35:31)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Function.Module._load (node:internal/modules/cjs/loader:1096:12)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.require (node:internal/modules/cjs/loader:1298:19)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.mod.require (/opt/Rocket.Chat.releases/programs/server/node_modules/@meteorjs/reify/lib/runtime/index.js:30:33)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at require (node:internal/modules/helpers:182:18)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Object. (/opt/Rocket.Chat.releases/programs/server/npm/node_modules/isolated-vm/isolated-vm.js:1:18)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module._compile (node:internal/modules/cjs/loader:1529:14)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.Mp._compile (/tools/static-assets/server/runtime.js:78:21)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.load (node:internal/modules/cjs/loader:1275:32)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.Mp.load (/tools/static-assets/server/runtime.js:35:31)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Function.Module._load (node:internal/modules/cjs/loader:1096:12)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.require (node:internal/modules/cjs/loader:1298:19)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.mod.require (/opt/Rocket.Chat.releases/programs/server/node_modules/@meteorjs/reify/lib/runtime/index.js:30:33)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at require (node:internal/modules/helpers:182:18)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at npmRequire (/tools/static-assets/server/npm-require.js:133:10)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.useNode (packages/modules-runtime.js:750:18)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at module (/opt/Rocket.Chat.releases/programs/server/packages/modules.js:238927:8)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at fileEvaluate (packages/modules-runtime.js:335:7)
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: at Module.require (packages/modules-runtime.js:237:14) {
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: code: ‘ERR_DLOPEN_FAILED’
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: }
Apr 16 02:07:48 wa-rocketchat-clone rocketchat[4314]: Node.js v20.19.0
Apr 16 02:07:48 wa-rocketchat-clone systemd[1]: rocketchat@3000.service: Main process exited, code=exited, status=1/FAILURE”

Thanks!

4

We upgraded successfully to 7.0.x but there is an issue if you use the docker images from rocketchat/rocket.chat in future versions. We noted that a user named “rocketchat” will now run the server, which in turn requires us to change the owner of uploaded files so they remain accessible.

5

Have you read the release notes?

It tells you on github.

As per your other reply you might want to consider

ERR_DLOPEN_FAILED

A search of github issues may help too.