Closed NoLooseEnds closed 1 year ago
I'm really stuck here. As far as I can tell it's outputing the exact same output as a clean install up until the last part, just not coming to the point of showing (which should be next):
+---------------------------------------------------+
| SERVER RUNNING |
+---------------------------------------------------+
| |
| Rocket.Chat Version: 6.3.5 |
| NodeJS Version: 14.21.3 - x64 |
| MongoDB Version: 5.0.21 |
| MongoDB Engine: wiredTiger |
| Platform: linux |
| Process Port: 3000 |
| Site URL: https://chat.domain.tld |
| ReplicaSet OpLog: Enabled |
| Commit Hash: 5c9c3f7864 |
| Commit Branch: HEAD |
| |
+---------------------------------------------------+
(Gotton from a clean install)
Tried restoring the backup dump, but unfortunately that also gives the exact same error. Importing it "over" a default install messes up the install since it does not overwrite existing/duplicate keys (and doing that would probably make it go back to how it was).
Any help is much appreciated!
The best advice is a preventive one:
The problem could be depending on how complex your configuration is.
Important also to read the change logs to confirm any breaking change that can also be catch on a isolated environment away form the production one.
Thanks, I guess, that's the lesson to take. I figured I was pretty safe just dumping the DB regularly.
I ended up migrating away from RocketChat and over to Mattermost (something had been contemplating for a while anyway). And since I was completely stuck with this issue – it was the excuse I needed. I had all the data from the db, so I just needed to format the export a bit to get it over.
To answer your questions (for the record):
Very small instance with only a handfull of users.
Anyhow, closing this since it's not an active issue (for me) at least.
Lesson learned: Use a test environment, even for the smaller updates.
Description:
I updated my docker install from 6.3.0 directly to 6.3.5 (latest), but that broke the whole thing. Trying to go back to 6.3.0 (or 6.3.1) did not resolve it.
Any tips is hugely appreciated.
(I do have a few days old backup, but would ideally keep the last few days).
Steps to reproduce:
Expected behavior:
Should upgrade and work as normal.
Actual behavior:
It halts in the startup process, don't see the "running-badge" running. But no super obvious huge error? Usually the "running-badge" shows up right after where it halts.
See logs below
Server Setup Information:
Client Setup Information
Relevant logs:
Testing with curl @ domain:
Testing with curl @ localhost:
➜ rocketchat docker logs rocketchat
➜ rocketchat docker logs rocketmongo