Exact same issue here. Unable to upgrade from 6.13 to 7.x. Any news on a fix or proper upgrade procedure?
1 Like
I do have the same issue in my own thread and no idea what to do now.
Glad I pulled a dump from mongo before I started.
Hope we can get help to solve this issue
You donāt that on a regular basis anyway? 
You mean you hope Rocket get to fix it for you? 
As per the bug.
I have asked again but nothing yet.
Remember Christmas probably cost 3+ weeks of time so everything is behind.
you are not helpingā¦
Also: I do daily backups automatically, since there had been activity on the chat, I decided to pull a dump just to be safe.
You didnāt realize that users are active on chats, do you?
Iām not a dev though I know most of them very well.
Let us know your server details including licence type.
If you have paid support, use it.
If not you are in the lap of the gods. The nature of open source.
Excellent. You didnāt make that clear.
As (non employed/non paid) Community Liaison and moderator here and open.rocket.chat Iām perfectly aware thanks.
You also might like to know that noapparent activity Iām the one that has been pushing in the background for a solution as I speak pretty well all day every day with several Rocket employees. However, I also have a day job and donāt control the dev, eng & product teams.
And Rocket also have paying customers that will come first.
sorry for being a bit rude but your āfacepalmā emotes triggered me,
as well as rocket chat failing to update to 6.4.0/stable from 6.13.0/stable
or updating to 7.0.0/stable from 6.13.0/stable
using the command:
sudo snap switch --channel=latest/stable rocketchat-server
to switch to the 6.4.0 stable channel
and then issuing
sudo snap refresh rocketchat-server
This doesnāt result in errors, but even when manually starting the server, nothing starts and no listener listens on 3000
if I revert it works fine again.
I have tried both versions, rocketchat-server is not starting up at all when in 6.4.0 or 7.0.0
and journalctl does not give any useful information when trying to start either version.
Only mentions caddy which I donāt use (i use a perfectly fine working nginx) and have disabled in env (yet it still appears in log file)
If I revert back to 6.13.0 it starts up fine again,
but mentions that it is supported until may, 1st 2025 and it frustrates me quite a lot not knowing what the issue really is.
community license, canāt afford a higher license due to very high costs that arenāt worth for what we would get in return for a private small community
Apps Engine v:
1.46.0
Node:
v14.21.2
database migration:
304 (January 9, 2025 20:40)
MongoDB:
5.0.15 / wiredTiger (oplog Enabled)
Check this issue comment:
I have asked the team as to why this happens - it should be taken care of automagically.
no bueno here,
after issuing:
sudo snap run rocketchat-server.mongo
show dbs
use parties (yes my instance uses āpartiesā)
db.adminCommand({ setFeatureCompatibilityVersion: ā5.0ā });
exit
sudo snap switch --channel=7.x/stable rocketchat-server
sudo snap refresh rocketchat-server
I am getting the errors:
/snap/rocketchat-server/1634/helpers/mongo.sh: line 50: ((: {"t":{"$date":"2025-01-11T15:15:08.358Z"},"s":"I", "c":"NETWORK", "id":5693100, "ctx":"js","msg":"Asio socket.set_optioailed with std::system_error","attr":{"note":"connect (sync) TCP fast open","option":{"level":6,"name":30,"data":"01 00 00 00"},"error":{"what":"set_option: Protocol not available",ssage":"Protocol not available","category":"asio.system","value":92}}}
1 : syntax error: operand expected (error token is "{"t":{"$date":"2025-01-11T15:15:08.358Z"},"s":"I", "c":"NETWORK", "id":5693100, "ctx":"js","msg":"Asio socket.set_option failedth std::system_error","attr":{"note":"connect (sync) TCP fast open","option":{"level":6,"name":30,"data":"01 00 00 00"},"error":{"what":"set_option: Protocol not available","messageProtocol not available","category":"asio.system","value":92}}}
1 ")
[ERROR] mongod server start wait timed out
[ERROR] pre refresh migration script /snap/rocketchat-server/1634/migrations/pre_refresh/feature_compatibity/00-adopt_version.sh
-----)
Dont know what this means or what I can do.
I got it to work, somehow, here is what I have done prior to setting the feature compatibility to 5.0:
just for safety, a mongodump:
snap run rocketchat-server.backupdb
stopping the snap:
snap stop rocketchat-server
refreshing diretly to a new channel:
snap refresh rocketchat-server --channel=7.x/stable
console output: rocketchat-server (7.x/stable) 7.0.0 von Rocket.Chat (rocketchatā) aufgefrischt
restarting rocketchat-server
snap start rocketchat-server
Seems to be running, for some strange reason, even though the service is disabled, masked in systemd and disabled in snap, caddy is still running, even though I have stopped it prior:
snap info rocketchat-server
rocketchat-server.rocketchat-caddy: simple, disabled, active
FWIW all snaps do - historical reasons.
Docker does not.
Was it before? Has this started after the upgrade?
Not sure which caddy version you are using but this is the doc. Please advise if this right or wrong.