Snap upgrade from 7.13.5 (rev 1785) to 8.x/stable fails in pre-refresh hook 00-adopt_version.sh

[williamz64]

Description:

Upgrading Rocket.Chat Snap from 7.13.5 (rev 1785) to 8.x/stable (rev 1788) consistently fails during the pre-refresh hook.

The upgrade never reaches the installation phase of the new revision because the pre-refresh migration script exits with an error.

While investigating, I found what appears to be a typo in the migration script:

is_mongod_running && stop_monngod

The helper function actually present in the snap package is:

stop_mongod()

I am not certain this is the root cause, but it appears suspicious because the failing hook exits immediately after running this script.

Steps to reproduce:

1. Install Rocket.Chat Snap 7.13.5 (rev 1785)
2. Verify MongoDB is running with FCV 7.0
3. Run:

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

4. Observe the upgrade failure during pre-refresh hook execution

Expected behavior:

The snap should successfully upgrade from 7.13.5 to 8.x/stable.

Actual behavior:

Upgrade fails before revision 1788 is installed.

Output:

error: cannot perform the following tasks:
- Run pre-refresh hook of "rocketchat-server" snap if present

Additional output from:

sudo snap tasks <change-id>

[ERROR] pre refresh migration script
/snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

Server Setup Information:

• Version of Rocket.Chat Server: 7.13.5
• License Type: Community
• Number of Users: N/A
• Operating System: Ubuntu 24.04 LTS
• Deployment Method: Snap
• Number of Running Instances: 1
• DB Replicaset Oplog: Enabled
• NodeJS Version: Managed by Snap package
• MongoDB Version: 7.0.31

Client Setup Information

• Desktop App or Browser Version: N/A
• Operating System: N/A

Additional context

Current snap version:

Name               Version  Rev   Tracking
rocketchat-server  7.13.5   1785  7.x/stable

Target version:

8.x/stable (rev 1788)

MongoDB version:

7.0.31

Feature Compatibility Version:

7.0

Replica set is healthy and PRIMARY.

The following script appears to be the failing migration:

/snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

Script content:

#!/bin/bash

source $SNAP/helpers/mongo.sh

start() {
    local v
    { is_mongod_running || start_mongod; } && is_mongod_ready && v=$(mongod_fcv) && is_mongod_primary && { is_feature_compatibility $v || set_feature_compatibility $v; } && stop_mongod
    is_mongod_running && stop_monngod
}

Searching for the typo-like function:

grep -R "stop_monngod" /snap/rocketchat-server/1785

returns:

/snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh:
    is_mongod_running && stop_monngod

Searching for the actual helper:

grep -R "stop_mongod()" /snap/rocketchat-server/1785/helpers

returns:

/snap/rocketchat-server/1785/helpers/mongo.sh:stop_mongod() {

Relevant logs:

2026-06-20T08:14:53+08:00 ERROR run hook "pre-refresh":

[ERROR] pre refresh migration script
/snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

I am happy to run additional diagnostics or test a patched revision if needed.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Pre-refresh hook fails: SNAP_ARCH not set → broken LD_LIBRARY_PATH → mongod cannot find libcrypto.so.1.1 #41001

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[williamz64]

Thanks for the duplicate suggestion.

I reviewed issue #41001.

My case appears to be different because mongod starts successfully during the pre-refresh hook.

The logs show:

about to fork child process, waiting until server is ready for connections.
forked process: 15263
child process started successfully, parent exiting

Initialized wire specification
Successfully registered PrimaryOnlyService

which suggests MongoDB was able to start and accept connections.

I do not see any errors related to:

• SNAP_ARCH
• LD_LIBRARY_PATH
• libcrypto.so.1.1

During investigation I also found the following line in:

/snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

is_mongod_running && stop_monngod

while the actual helper function is:

stop_mongod()

and stop_monngod appears only once in the entire snap package.

I cannot confirm this is the root cause, but it seems unrelated to issue #41001 and may warrant separate investigation.

[p4tpr0]

Possible workaround (worked for us):

• fix a copy of the file
• mount the fixed copy over the original.

for example:

cp /snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh /tmp/00-adopt_version.sh
vim /tmp/00-adopt_version.sh
mount -o ro,bind /tmp/00-adopt_version.sh /snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

then upgrade:

snap refresh rocketchat-server --channel=8.x/stable

hope this helps.

[varioous]

Same bug.

This helped me and v 8.0 in snap is running now:

#alten Bind-Mount lösen
sudo umount /snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

#vollständigen Fix schreiben (if-Konstrukt statt && + return 0)
cat > /root/snapfix/00-adopt_version.sh <<'EOF'
#!/bin/bash
source $SNAP/helpers/mongo.sh
start() {
local v
{ is_mongod_running || start_mongod; } && is_mongod_ready && v=$(mongod_fcv) && is_mongod_primary && { is_feature_compatibility $v || set_feature_compatibility $v; } && stop_mongod
if is_mongod_running; then stop_mongod; fi
return 0
}
EOF
chmod +x /root/snapfix/00-adopt_version.sh

sudo mount --bind /root/snapfix/00-adopt_version.sh
/snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

sudo snap refresh rocketchat-server

[Object9050]

Thank you, @varioous and @p4tpr0 ! This saved me from having to use the crowbar called backup-delete :)

What worked for me (I used the new version of the script from revision 1786 which was luckily on most of our servers):

umount /snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

mkdir /root/snapfix

vim /root/snapfix/00-adopt_version.sh

#!/bin/bash

source $SNAP/helpers/mongo.sh

start() {
        if !is_mongod_running; then
                start_mongod
        fi
        is_mongod_ready
        is_mongod_primary
        local v="$(mongod_fcv)"
        echo "Expected FCV: $fcv"
        if is_feature_compatibility "$v"; then
                echo "Expected FCV matches current FCV"
                return
        fi
        if set_feature_compatibility "$v"; then
                echo "FCV set to $v"
        else
                echo "Failed to set FCV to $v"
                exit 1
        fi
}

chmod +x /root/snapfix/00-adopt_version.sh

mount -o ro,bind /root/snapfix/00-adopt_version.sh /snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

snap refresh rocketchat-server --channel=8.x/stable

[pyrates999]

can we get a new release with this added to fix the upgrade?

[p4tpr0]

I’m not at all familiar with Snap, but I think it’s not possible to fix with a new release: release 7.13.5 (rev 1785) includes a defective file (00-adopt_version.sh). In order to fix that file with a new release you must be able to install that new release. But the defect in 00-adopt_version.sh prevents you to install that new release.

[pyrates999]

Oh so it's been fixed in 8.5.1 then?

[pyrates999]

I also have backup on refresh disabled, as it takes longer then 10 minutes to do a backup. And snap limits it to 10 minutes to do the backup.

[Fiodin]

Was reported on the 28th of April: RocketChat/server-snap#82 (comment)

[pyrates999]

I was able to update rocketchat-server to 8.5.1.

This did not have stop_monngod in the file /snap/rocketchat-server/1785/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

But instead the path was: /snap/rocketchat-server/1786/migrations/pre_refresh/feature_compatibility/00-adopt_version.sh

And this was the file that had stop_mongod in it: /snap/rocketchat-server/1786/migrations/post_refresh/feature_compatibility/XX-confirm_mongo_startup.sh: start_mongod && is_mongod_ready && stop_mongod

I think rev 1785 was updated to 1786 before I had tried updating rocketchat-server again.

[Abigor666]

So I updated the version. In my case there was enough free space, but it looks like backups were the cause of the problem.

root@server:~# snap refresh rocketchat-server --channel=8.x/stable
error: cannot perform the following tasks:
- Run pre-refresh hook of "rocketchat-server" snap if present (run hook "pre-refresh":
-----
[*] Creating backup file...

<exceeded maximum runtime of 10m0s>
-----)

I disabled backups during the upgrade (I already have a VM snapshot, so I didn’t need them):

# Disable backup
sudo snap set rocketchat-server backup-on-refresh=disable
# Check that backup is disabled
snap get rocketchat-server
# Upgrading
sudo snap refresh --channel=8.x/stable rocketchat-server

After this, the upgrade worked.

[pyrates999]

I disabled backups during the upgrade (I already have a VM snapshot, so I didn’t need them):

You should do a manual backup then before the upgrade. That's what I do. I also think they should give you a way to increase the timeout time.