Rocket.Chat's Community Open Call 🎤 Jan 19th, 2022 Join us!

Update 4.2 issue

Description

After trying to upgrade to RC4.2 and following the npm-stuff during update process we run into an issue with starting the server:

systemctl status rocketchat
● rocketchat.service - The Rocket.Chat server

  • Loaded: loaded (/lib/systemd/system/rocketchat.service; enabled; vendor preset: enabled)*
  • Active: failed (Result: exit-code) since Mon 2021-11-29 07:13:31 CET; 9s ago*
  • Process: 26751 ExecStart=/usr/local/bin/node /opt/Rocket.Chat/main.js (code=exited, status=1/FAILURE)*
  • Main PID: 26751 (code=exited, status=1/FAILURE)*

We find out, that 2 versions of node seems to be installed!?

/usr/local/bin/node -v
v12.22.1

/usr/bin/node --version
v10.24.0

How can we get rid of or solve the follwing npm message?

npm WARN old lockfile The npm-shrinkwrap.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
*npm WARN old lockfile *
npm WARN old lockfile This is a one-time fix-up, please be patient…
*npm WARN old lockfile *
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see Request’s Past, Present and Future · Issue #3142 · request/request · GitHub
npm WARN deprecated node-pre-gyp@0.14.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future

Server Setup Information

  • Version of Rocket.Chat Server: 4.1.1
  • Operating System: Debian 10
  • Deployment Method:
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version: 12.22.1
  • MongoDB Version: 4.4.10
  • Proxy: nginx
  • Firewalls involved:

issue solved after 3rd identical update process …