Rocket.Chat Proxy Error

ATSrl 2021-06-07 16:46:43 UTC #1

Hi All,
We are encountering a serious problem with RochetChat crashing at startup after the automatic update.
The error is

Mongo.db is working,
the lock file has been deleted
all modules are fully functional
Does anyone have any indications?
Gabriele

StefanU 2021-06-07 18:02:04 UTC #2

Hi Gabriele.

What automatic update?

What Apache is this that is sending this message?

Ist that your reverse proxy for EGroupware?

If so: What says your apache-error-log?

Stefan

RalfBecker 2021-06-07 18:29:47 UTC #3

Two customers also reporting that, do you have an error-message from the starting Rocket.Chat container:

error: "Can't find migration version 225"

What version are you using, what’s the output of:

grep image /etc/egroupware-rocketchat/docker-compose.override.yml

Ralf

RalfBecker 2021-06-07 18:48:01 UTC #4

Just tried the todays new version 3.14.5 which works ok for me and stayed on migration 222, like 3.14.4 before.

Is it possible you tried to downgrade from rocketchat/rocket.chat:latest to :3.14.x?

Downgrades are not supported by Rocket.Chat and lead to a crash / exit when starting the container!

If that’s the case, you can only go back to latest.

Please note our newer packages use no longer rocketchat/rocket.chat:latest but mirror their releases in our repository on quay.io and use now quay.io/egroupware/rocket.chat:stable, which we only assign after some testing.

If you want to move to quay.io/egroupware/rocket.chat:stable, you can use our script:
/etc/egroupware-rocketchat/move2stable.sh
Which compares the versions and only does the move, if it would not attempt a downgrade.

Ralf

ATSrl 2021-06-07 19:22:13 UTC #5

Hi All
the error we are dealing with is
error: “Can’t find migration version 225”,
reason: undefined,
details: undefined,
errorType: 'Meteor.Error
These are the used modulistica
image: rocketchat/rocket.chat:latest
image: mongo:4.0
image: mongo:4.0
Our it guru is looking for http://move2stable.sh
Any advice ?
Gabriele

RalfBecker 2021-06-07 19:42:52 UTC #6

That means rocketchat accidently pushed 3.14.5 as latest

Don’t know if they already fixed it or not.
You can try to pull again:

cd /etc/egroupware-rocketchat
docker-compose pull
docker-compose up -d
docker logs -f rocketchat # use Ctrl-C to stop tail after RC is started

If that still gives you the same error, Rocket.Chat has not yet fixed it and you can only fix the tag manually:

cd /etc/egroupware-rocketchat
sed 's/rocket.chat:latest/rocket.chat:3.15.0/' -i docker-compose.override.yml
docker-compose pull
docker-compose up -d
docker logs -f rocketchat # use Ctrl-C to stop tail after RC is started

And don’t forget to go back to stable latest tag, or better our quay.io/egroupware/rocket.chat:stable, to continue receiving updates.

Ralf

ATSrl 2021-06-08 06:25:44 UTC #7

Hi All,
Our IT guru has applied the instructions in the post and in about 20 container compilations has always encountered this error on the database:

therefore he assumed that the DB engine should be downgraded from 4.4 to 4.0
Dumped the data from the db in use and running some scripts built to restore data in a new database created from scratch running the engine old version (the 4.0) everything started to work again.
Thanks to Giuseppe (our precious IT Guru) and all the contributors to this post whose help is really precious.
So … the problem seems to have been completely solved.

Thanks again.
Gabriele

RalfBecker 2021-06-08 07:13:03 UTC #8

Rocket.Chat so far only supports MongoDB 4.0 and that’s what’s in our docker-compose.yml:

github.com

EGroupware/build.opensuse.org/blob/master/server:eGroupWare/egroupware-rocketchat/egroupware-rocketchat/docker-compose.yml#L41


    - PORT=3000
    - MONGO_URL=mongodb://mongo:27017/rocketchat
    - MONGO_OPLOG_URL=mongodb://mongo:27017/local
  depends_on:
    - mongo
  ports:
    - 127.0.0.1:3000:3000
  container_name: rocketchat


mongo:
  image: mongo:4.0
  restart: unless-stopped
  volumes:
   - mongo:/data/db
   - /var/lib/egroupware/default/rocketchat/dump:/dump
  command: mongod --smallfiles --oplogSize 128 --replSet rs0 --storageEngine=mmapv1
  container_name: rocketchat-mongo


# this container's job is just run the command to initialize the replica set.
# it will run the command and remove himself (it will not stay running)
mongo-init-replica:

The other error from MongoDB init container is normal and unavoidable AFAIK, when using Watchtower. It simply means the previous running init container is no longer the latest mongo:4.0 version. This error can by safely ignored (in scripts I use: echo "y" | docker-compose up -d).

Please mark my first suggestion, simply pulling again, as solution.

Ralf

J_Roeleveld 2021-06-08 19:53:13 UTC #9

Where can I find the version used for the “quay.io/egroupware/rocket.chat:stable” ?
I just fixed it to 3.15.0 as I want to switch (and downgrade isn’t possible), but need to be able to see when I can switch over safely.

RalfBecker 2021-06-08 20:20:01 UTC #10

Use my script: /etc/egroupware-rocketchat/move2stable.sh

It checks if it’s save and only then migrates you to stable tag.

Ralf

RalfBecker 2021-06-08 20:24:13 UTC #11

Currently it’s 3.14.5.

I‘ll usually stay on a major version as long as it gets security updates.

Ralf