Cant update via snap

[alekdimitrov]

Description:

Cant update via snap from 6.13.0 to 7.0 edited

Steps to reproduce:

1. Switch to relase chanel 7.x
2. Snap refresh rocketchat-server
3. The server return: Start snap "rocketchat-server" (1633) services (systemctl command [start snap.rocketchat-server.rocketchat-mongo.service] failed with exit status 1: stderr:

Expected behavior:

Update to 7.0 edited

Actual behavior:

Server Setup Information:

• Version of Rocket.Chat Server: 6.13.0
• License Type: free
• Number of Users: 40
• Operating System: Ubuntu 20.04
• Deployment Method: snap
• Number of Running Instances:
• DB Replicaset Oplog:
• NodeJS Version:
• MongoDB Version:

Client Setup Information

• Desktop App or Browser Version:
• Operating System:

Additional context

Relevant logs:

Here is the logs from server after error:

systemctl status snap.rocketchat-server.rocketchat-mongo.service (logs)
https://pastejustit.com/asbx1cexen

journalctl -xe (logs)
https://pastejustit.com/yuyrbyesza

[reetp]

Which document did you follow?

List the exact commands you used please.

I suspect this is really a support issue and not a bug. I'll see if I can some insight into it.

In the meantime there are some more snap commands to help diagnose here:

https://docs.rocket.chat/docs/snaps-faq

Please use pastebin or similar for long logs - it gets hard to read on mobile!

[alekdimitrov]

Which document did you follow?
This one: https://docs.rocket.chat/docs/snaps-faq
List the exact commands you used please.:
snap refresh rocketchat-server (as a sudoer user)
After error commands that I use are:
systemctl status snap.rocketchat-server.rocketchat-mongo.service
journalctl -xe
There is no error in logs right after error receiving
Please use pastebin or similar for long logs - it gets hard to read on mobile!
Ok. My fault. I will edit it.

Thanks in advance
Best regard Alek

[reetp]

Is this you?

Can’t upgrade to 7 from 6

Why have you opened an issue? Github is for bugs, not general support.

You just create confusion and duplication.

And here is at least one that is probably a duplicate because you haven't searched here.

Search : is:issue apparmor="DENIED"

Make sure you read all of these.

#29385
#29011

Seems this is a common format for the command, as per the docs:

sudo snap refresh rocketchat-server --channel=7.x/stable

[alekdimitrov]

First, thanks for the links.
Second, this is another person with the same problem.
Regarding the apparmor="DENIED" problem, this is an old problem and from v.3 to v.6 I had no problem upgrading, but I will check it.
I think if there is no diference in syntax
snap switch rocketchat-server --channel=7.x/stable
snap refresh rocketchat-server
and
sudo snap refresh rocketchat-server --channel=7.x/stable
Please, no need for aggression. I just have a problem and since I can't find any errors in the logs, I decided it was a bug.
And the fact that another person other than me has the same problem leads to the conclusion that maybe it really is a bug.
But I definitely didn't offend anyone, so please let's stick to normal communication

[mikengocdo]

I have the same exact issue on ubuntu 20.04, but I didn't have 7.1.0, only 7.0.0 available. I also thought it was a bug, and have been watching this thread to see any solutions.

[alekdimitrov]

I have the same exact issue on ubuntu 20.04, but I didn't have 7.1.0, only 7.0.0 available. I also thought it was a bug, and have been watching this thread to see any solutions.

Thank you friend. I dont have as 7.1 its my fault. Its 7.0. Now I will edit it.

[reetp]

Note I don't work for Rocket - I am solely a volunteer so it is my own personal time doing this. Regrettably no one else in the 'Community' seems to be bothered.

Github is largely ignored as they have an internal tracker for issues. So it I don't look at it then quite possibly no one will....

Some info here on issue diagnosis. The proper place to ask in the first instance is the forums or open.rocket.chat as you are more likely to get a response.

https://gist.github.com/reetp/a66149d5f060f260643a353ca7067a98

Second, this is another person with the same problem.

OK. It still doesn't make it a bug or the same issue.

Regarding the apparmor="DENIED" problem, this is an old problem and from v.3 to v.6
I had no problem upgrading, but I will check it.

Yup.

I think if there is no difference in syntax

snap switch rocketchat-server --channel=7.x/stable
snap refresh rocketchat-server

sudo snap refresh rocketchat-server --channel=7.x/stable

As there are two ways of doing it then it is worth a try. I do not use snaps at all - don;t trust them an inch - so have little experience of them. Just trying to work through the case one stage at a time.

I decided it was a bug.

No, the people here decide if it is a bug. Probably me.

And the fact that another person other than me has the same problem leads to the conclusion that maybe it really is a bug.

No, that isn't necessarily the case and is a really bad assumption to make. That's how we get XY Problems.

I have asked if the snap guy at Rocket can have a look but i have have no guarantee of that. Paid customers come first.

[alekdimitrov]

I have asked if the snap guy at Rocket can have a look but i have have no guarantee of that. Paid customers come first.

Thank you in advance for this.
Note that there is no "urgent" label anywhere nor an ultimatum.
I am sharing information about a problem on a template You decide whether it is a bug or not I agree that.
I will stay on v. 6.13.1 until I find a solution to the problem I have. Github is an open platform. I suppose you could make a closed ticket platform for paid users. But I do not accept the remark "You just create confusion and duplication" based on assumptions.
Thank you for your time spent

[reetp]

suppose you could make a closed ticket platform for paid users.

They already have that. There is an entire system you cannot see. Bug tracker with support tickets and all sorts. (Yes I worked at Rocket for a while so I know how it all works)

Github is really just where they publish their completed code. It is NOT where they do any real work.

But I do not accept the remark "You just create confusion and duplication" based on assumptions.

Having been debugging stuff for longer than I care to remember I can tell you absolutely that you are wrong. It is also why you are here asking questions, and I am here trying to solve them.

Also see:

https://xyproblem.info

Remember that if your diagnostic theories were accurate, you wouldn't be asking for help right?

[reetp]

I have asked if the snap dev can comment.

He may, or he may not. There's a lot of paying customers to look after...

I can't do more, and I am on vacation!

[alekdimitrov]

I have asked if the snap dev can comment.

He may, or he may not. There's a lot of paying customers to look after...

I can't do more, and I am on vacation!

Thank you. Wish you happy vacation!

[RAurelian]

Hi,
In case it helps, we have the same issue on Ubuntu 24.04.1 LTS - we cannot update from RC v6.13.0 to v7.x via snaps. And we cannot find a specific error.

[reetp]

In case it helps, we have the same issue on Ubuntu 24.04.1 LTS - we cannot update from RC v6.13.0 to v7.x via snaps. And we cannot find a specific error.

Nope it doesn't. Every server is different.

Follow directions above and tell us about your own specific setup.

Then some debugging info again as per above.

[RAurelian]

I have a support case opened and will keep the discussion there for now, so it is not spread over multiple threads.

[DiNerve]

I have a support case opened and will keep the discussion there for now, so it is not spread over multiple threads.

Any news? There doesn't seem to be much traction on the forums thread either... :(

[reetp]

I have a support case opened and will keep the discussion there for now, so it is not spread over multiple threads.

Any news? There doesn't seem to be much traction on the forums thread either... :(

See my previous responses.

It's with the internal teams, and the previous user has a support ticket open as well. There is a huge system hidden from view. It takes a long time to procesd stuff. Github for Rocket is really just where they output the final code.

Again note.... If you are on a "free" tier, support is on a "best effort" basis. If you want 24/7 support there are paid tiers....

[DiNerve]

I have a support case opened and will keep the discussion there for now, so it is not spread over multiple threads.

Any news? There doesn't seem to be much traction on the forums thread either... :(

See my previous responses.

It's with the internal teams, and the previous user has a support ticket open as well. There is a huge system hidden from view. It takes a long time to procesd stuff. Github for Rocket is really just where they output the final code.

Again note.... If you are on a "free" tier, support is on a "best effort" basis. If you want 24/7 support there are paid tiers....

Thanks, I took note of your responses and thanks for redirecting to paid tiers, I was actually quoting and asking the user about his support case and if he had seen any progress.

[RAurelian]

Hi all, an update here:

We had multiple MongoDB Index Issues (errors such as "An equivalent index already exists with the same name but different options."). We`ve solved some of these, but not all. This has been a recurring issue over the years with RocketChat, but this is not what blocked the update in this case.

However, what fixed our problem of updating our Snap to v7.0.0 was running this command in MongoDB:
db.adminCommand({ setFeatureCompatibilityVersion: "5.0" });
After this, the snap updated without issues.

Apparently, our MongoDB featureCompatibilityVersion was set to 4.4, but the upgrade requires 5.0, 5.3, or 6.0. I do not know why this was the case, we never set this manually.

Please note that each environment is different and I do not recommend taking any steps mentioned here since they may not work for your environment or have adverse effects. Still, maybe anyone experiencing the same issue can do a MongoDB Feature compatibility version check as per this: https://www.mongodb.com/docs/manual/reference/command/setFeatureCompatibilityVersion/#get-featurecompatibilityversion
and see if yours is also set to something unsupported in RC v7.

[alekdimitrov]

Hi all, an update here:

We had multiple MongoDB Index Issues (errors such as "An equivalent index already exists with the same name but different options."). We`ve solved some of these, but not all. This has been a recurring issue over the years with RocketChat, but this is not what blocked the update in this case.

However, what fixed our problem of updating our Snap to v7.0.0 was running this command in MongoDB: db.adminCommand({ setFeatureCompatibilityVersion: "5.0" }); After this, the snap updated without issues.

Apparently, our MongoDB featureCompatibilityVersion was set to 4.4, but the upgrade requires 5.0, 5.3, or 6.0. I do not know why this was the case, we never set this manually.

Please note that each environment is different and I do not recommend taking any steps mentioned here since they may not work for your environment or have adverse effects. Still, maybe anyone experiencing the same issue can do a MongoDB Feature compatibility version check as per this: https://www.mongodb.com/docs/manual/reference/command/setFeatureCompatibilityVersion/#get-featurecompatibilityversion and see if yours is also set to something unsupported in RC v7.

Cool. Thank you very much for this comment. I was able to update to v.7 after that step:

However, what fixed our problem of updating our Snap to v7.0.0 was running this command in MongoDB: db.adminCommand({ setFeatureCompatibilityVersion: "5.0" }); After this, the snap updated without issues.

[RAurelian]

Great, I`m glad this was helpful to you!

[reetp]

However, what fixed our problem of updating our Snap to v7.0.0 was running this command in MongoDB:
db.adminCommand({ setFeatureCompatibilityVersion: "5.0" });
After this, the snap updated without issues.

Can anyone else confirm if this works?

I am going to ask the team about it - this should probably have been scripted in the snap upgrade.

[DiNerve]

However, what fixed our problem of updating our Snap to v7.0.0 was running this command in MongoDB:
db.adminCommand({ setFeatureCompatibilityVersion: "5.0" });
After this, the snap updated without issues.

Can anyone else confirm if this works?

I am going to ask the team about it - this should probably have been scripted in the snap upgrade.

Will give it a go in a few hours and update this post with the result.

[DiNerve]

However, what fixed our problem of updating our Snap to v7.0.0 was running this command in MongoDB:
db.adminCommand({ setFeatureCompatibilityVersion: "5.0" });
After this, the snap updated without issues.

Can anyone else confirm if this works?

I am going to ask the team about it - this should probably have been scripted in the snap upgrade.

Hey there, can confirm this command worked, cheers.