Rocketchat error 502 bad gateway after automatic pdate

ATSrl 2022-01-31 13:58:20 UTC #1

Hello,
after an automatic update Rocketchat does not work anymore. I get error 502 Bad Gateway nginx/1.18.0 (Ubuntu).
The docker logs rocketchat command returns:
Exception in callback of async function: errorClass [Error]: [Can’t find migration version 253]
at Object.Migrations._findIndexByVersion (app/migrations/server/migrations.js:403:8)
at Object.Migrations._migrateTo (app/migrations/server/migrations.js:254:24)
at Object.Migrations.migrateTo (app/migrations/server/migrations.js:179:20)
at module (server/startup/migrations/xrun.js:6:13)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at Module.moduleLink [as link] (/app/bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/lib/runtime/index.js:52:22)
at module (server/startup/migrations/index.js:1:5090)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at Module.moduleLink [as link] (/app/bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/lib/runtime/index.js:52:22)
at module (server/main.js:1:210)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at require (packages/modules-runtime.js:258:21)
at /app/bundle/programs/server/app/app.js:208672:15
at /app/bundle/programs/server/boot.js:401:38
at Array.forEach ()
at /app/bundle/programs/server/boot.js:226:21
at /app/bundle/programs/server/boot.js:464:7
at Function.run (/app/bundle/programs/server/profile.js:280:14)
at /app/bundle/programs/server/boot.js:463:13 {
isClientSafe: true,
error: “Can’t find migration version 253”,
reason: undefined,
details: undefined,
errorType: ‘Meteor.Error’
}

Nginx-error logs

22/01/31 09:37:21 [error] 909#909: *5 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2.236.119.178, server: ecm.atsrl.net, request: “GET /rocketchat/_timesync HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/_timesync”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/rocketchat/group/CIRA"
2022/01/31 09:37:25 [error] 909#909: *1344 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.26, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:38:19 [error] 909#909: *1395 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.220, server: ecm.atsrl.net, request: “GET /rocketchat/_timesync HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/_timesync”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/rocketchat/direct/4Pk3fh5a2iwckyBwFLkgMnriTyCBiCjZbn"
2022/01/31 09:38:21 [error] 909#909: *5 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2.236.119.178, server: ecm.atsrl.net, request: “GET /rocketchat/_timesync HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/_timesync”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/rocketchat/group/CIRA"
2022/01/31 09:38:29 [error] 909#909: *1344 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.26, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:38:46 [error] 909#909: *1580 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.34, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:38:47 [error] 909#909: *1581 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.34, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:38:51 [error] 909#909: *1581 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.34, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:38:55 [error] 909#909: *5 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2.236.119.178, server: ecm.atsrl.net, request: “GET /rocketchat/sockjs/info?cb=e3wdoq31fh HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/sockjs/info?cb=e3wdoq31fh”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/rocketchat/group/CIRA"
2022/01/31 09:39:07 [error] 909#909: *1581 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.34, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:19 [error] 909#909: *1395 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.220, server: ecm.atsrl.net, request: “GET /rocketchat/_timesync HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/_timesync”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/rocketchat/direct/4Pk3fh5a2iwckyBwFLkgMnriTyCBiCjZbn"
2022/01/31 09:39:21 [error] 909#909: *5 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2.236.119.178, server: ecm.atsrl.net, request: “GET /rocketchat/_timesync HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/_timesync”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/rocketchat/group/CIRA"
2022/01/31 09:39:45 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:45 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/home HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/home”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:46 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:50 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:52 [error] 909#909: *1618 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:52 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/home HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/home”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:53 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:54 [error] 909#909: *1669 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.80, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:55 [error] 908#908: *1676 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.80, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:57 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:39:59 [error] 908#908: *1676 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.80, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:40:11 [error] 909#909: *1581 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.34, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:40:13 [error] 909#909: *1620 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 151.25.59.151, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:40:15 [error] 908#908: *1676 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.80, server: ecm.atsrl.net, request: “GET /rocketchat/api/info HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/api/info”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/egroupware/index.php?cd=yes"
2022/01/31 09:40:19 [error] 909#909: *1395 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.0.0.220, server: ecm.atsrl.net, request: “GET /rocketchat/_timesync HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/_timesync”, host: “ecm.atsrl.net”, referrer: "https://ecm.atsrl.net/rocketchat/direct/4Pk3fh5a2iwckyBwFLkgMnriTyCBiCjZbn"
2022/01/31 09:40:21 [error] 909#909: *5 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2.236.119.178, server: ecm.atsrl.net, request: “GET /rocketchat/_timesync HTTP/1.1”, upstream: “http://127.0.0.1:3000/rocketchat/_timesync”, host: “ecm.atsrl.net”, referrer: “https://ecm.atsrl.net/rocketchat/group/CIRA”

the result of the curl call made from within the server returns:

Last login: Mon Jan 31 09:14:17 2022 from 10.0.0.48
atsrl@egw21:~$ curl https://ecm.atsrl.net/rocketchat

502 Bad Gateway

nginx/1.18.0 (Ubuntu)

the result of the curl call from the server’s interior contacting the localhost on port 3000

atsrl@egw21:~$ curl http://127.0.0.1:3000/rocketchat
curl: (56) Recv failure: Connection reset by peer
atsrl@egw21:~$ curl http://127.0.0.1:3000
curl: (56) Recv failure: Connection reset by peer

this is the message

Any Idea ?

StefanU 2022-01-31 14:57:22 UTC #2

Hi Gabriele.

What Update? 4.3.2 => 4.3.3 ?

There was no DB update. So you can revert the container update:

Stefan

ATSrl 2022-01-31 17:06:20 UTC #3

Hi Stefan,
thanks for your reply but as I don’t have Rocketchat running I can’t answer unless you give me some information about how to see which version of the database is running without being able to access Rocketchat.
It would be useful to know if there is a way to install RocketchChat separately from EGW or, in other words so that it responds to another URL in order to unbundle updates and make management more flexible.
Is there any documentation regarding how to do this?
Gabriele

StefanU 2022-01-31 18:19:59 UTC #4

What does it say in your

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

services:
  rocketchat:
    image: quay.io/egroupware/rocket.chat:stable

That should tell us what you’ve installed.

When watchtower performs the container update, this is also logged.

Of course, you can also integrate external Rocket.Chat into EGroupware.
You then have to install it yourself on a system:
https://docs.rocket.chat/quick-start/installing-and-updating

In EGroupware you then put Rocket.Chat under

/Admin/Applications/OpenID/OAuth2 Server/Clients

as an app.
Of course, you have to allow IFrame and configure OAuth in RC.

We do all this during the installation. And we configure OAuth in RC in the database. The community version doesn’t really allow that any more.

Hmmm…

You can always set everything the way you want it.
For example, you can set a fixed RC version:

I had already posted the link above.

Stefan

ATSrl 2022-01-31 20:07:08 UTC #5

Dear Stefan,
I probably don’t understand correctly. I checked the version we are using as you asked for, and I can confirm that it is the latest one, as I found the string “image: quay.io/egroupware/rocket.chat:latest” so it should be 4.3.3.

I don’t understand does the community version no longer allow you to use Rocketchat? Has this functionality been removed? What is the meaning of this statement?
Gabriele

StefanU 2022-01-31 20:12:07 UTC #6

OK.
Better still change it to stable.

Rocket.Chat community version…, not EGroupware.

Stefan

StefanU 2022-01-31 20:19:08 UTC #7

Hm…
The DB of 4.3.3 has

Have you had a higher version of Rocket.Chat running?

Is
rocketchat-mongo
running?

Stefan