RocketChat / RocketChat/Rocket.Chat
rocketchat-server.backupdb error after 1502 upgrade (ubuntu 20) #33
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Daily cron job return errors since this update :
snap stop rocketchat-server.rocketchat-server => Stopped.
systemctl is-active snap.rocketchat-server.rocketchat-server => inactive
snap run rocketchat-server.backupdb
=> [-] Please shutdown Rocket.Chat first to get a clean backup
=>[-] Use 'sudo snap stop rocketchat-server.rocketchat-server'
=>/snap/rocketchat-server/1502/bin/backupdb.sh: line 24: log: command not found
=>/snap/rocketchat-server/1502/bin/backupdb.sh: line 26: log: command not found
=>/snap/rocketchat-server/1502/bin/backupdb.sh: line 28: log: command not found
The generated backup is not consistent since directory "dump" is empty.
/snap/rocketchat-server/1502/bin/backupdb.sh does not contain any log function.
Steps to reproduce:
Expected behavior:
Actual behavior:
Server Setup Information:
- Version of Rocket.Chat Server: 4.2.2
- Operating System: Ubuntu 20
- Deployment Method: snap
- Number of Running Instances: 1
- DB Replicaset Oplog:
- NodeJS Version: v12.22.7
- MongoDB Version: MongoDB3.6.23 / wiredTiger (oplog )
Client Setup Information
- Desktop App or Browser Version: Chrome
- Operating System:Win10
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 with /snap/rocketchat-server/1502/bin/backupdb.sh and compare its behavior with the reported snap stop and snap run commands on Ubuntu 20. Reproduce the backup and inspect the generated dump directory and command output. Done means the script runs after Rocket.Chat is stopped, produces a consistent non-empty dump, and no longer reports missing log commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, shell, ubuntu
- Domain
- database, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100