RocketChat / RocketChat/Rocket.Chat
Error showing After Upgrading from 7.0.0 to 7.4.1
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
I am running self hosted community version of Rocket Chat in Container. After upgrading it from image tag 7.0.0 to 7.4.1. Rocket chat is running fine. But I am getting this following error in log.
FYI, I am using host filesystem as volume.
# docker compose logs -f rocket-chat
rocket-chat | [2025-03-21T21:22:32.665Z] INFO b3cd58b0-434a-43e7-96ef-55412162cd1d/TRANSIT: Reconnecting...
rocket-chat | [2025-03-21T21:22:32.666Z] ERROR b3cd58b0-434a-43e7-96ef-55412162cd1d/TRANSPORTER: Server error. Error: listen EADDRINUSE: address already in use :::33147
rocket-chat | at Server.setupListenHandle [as _listen2] (node:net:1937:16)
rocket-chat | at listenInCluster (node:net:1994:12)
rocket-chat | at Server.listen (node:net:2099:7)
rocket-chat | at /app/bundle/programs/server/npm/node_modules/moleculer/src/transporters/tcp/tcp-reader.js:62:11
rocket-chat | at new Promise (<anonymous>)
rocket-chat | at TcpReader.listen (/app/bundle/programs/server/npm/node_modules/moleculer/src/transporters/tcp/tcp-reader.js:46:10)
rocket-chat | at TcpTransporter.startTcpServer (/app/bundle/programs/server/npm/node_modules/moleculer/src/transporters/tcp.js:155:22)
rocket-chat | at /app/bundle/programs/server/npm/node_modules/moleculer/src/transporters/tcp.js:122:21
rocket-chat | at processTicksAndRejections (node:internal/process/task_queues:105:5) {
rocket-chat | code: 'EADDRINUSE',
rocket-chat | errno: -98,
rocket-chat | syscall: 'listen',
rocket-chat | address: '::',
rocket-chat | port: 33147
rocket-chat | }
Steps to reproduce:
- Upgrade container image tag from 7.0.0 to 7.4.1
- Stop and Remove running container
docker compose up -dto bring the rocket container up with the new image tag.
Expected behavior:
No error should be shown in container's log
Actual behavior:
Getting the error mentioned above
Server Setup Information:
Rocket.Chat Version: 7.4.1
NodeJS Version: 22.13.1 - x64
MongoDB Version: 6.0.13
MongoDB Engine: wiredTiger
Platform: linux
Process Port: 3000
Site URL: https://chat.test.com
ReplicaSet OpLog: Enabled
Commit Hash: fb0f4eaf59
Commit Branch: HEAD
Client Setup Information
- Desktop App Version: 4.2.0
- Operating System: macOS 15.3.2
Additional context
Relevant logs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the 7.0.0-to-7.4.1 container upgrade with the reported docker-compose setup and inspect the Moleculer TCP transporter entries shown in the stack trace: tcp-reader.js and tcp.js. Verify why port 33147 is already in use during startup; done means the upgrade starts without the EADDRINUSE error and the service remains operational.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, node.js, typescript
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100