[GH-ISSUE #1563] Error when running the new backup script #977

New issue

Closed

opened 2026-03-02 02:20:22 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 02:20:22 +03:00

Owner

Originally created by @josvink66 on GitHub (Jul 13, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1563

Server Info (please complete the following information):

OS:Ubuntu 20.04
Browser: n/a
RMM Version v0.15.12

Installation Method:

Standard
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): n/a
Agent OS: n/a

Describe the bug
When running the new backup.sh script it throw an error (see screenhot). The backup process does continue but in the end the file necessary for the mongo to postgresql conversion is not created. So I can't use the backup for the restore on the new OS,

To be absolute sure I was using the latest backup.sh I made sure to remove the old version.

To Reproduce
Steps to reproduce the behavior:
wget -N https://raw.githubusercontent.com/amidaware/tacticalrmm/master/backup.sh
chmod +x backup.sh
./backup.sh

Expected behavior
A full backup file with the file necessary for the mongo to postgresql conversion.

Screenshots

Additional context
Running the command that throws the error manually gives the same error:

Originally created by @josvink66 on GitHub (Jul 13, 2023). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1563 **Server Info (please complete the following information):** - OS:Ubuntu 20.04 - Browser: n/a - RMM Version v0.15.12 **Installation Method:** - [X] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): n/a - Agent OS: n/a **Describe the bug** When running the new backup.sh script it throw an error (see screenhot). The backup process does continue but in the end the file necessary for the mongo to postgresql conversion is not created. So I can't use the backup for the restore on the new OS, To be absolute sure I was using the latest backup.sh I made sure to remove the old version. **To Reproduce** Steps to reproduce the behavior: wget -N https://raw.githubusercontent.com/amidaware/tacticalrmm/master/backup.sh chmod +x backup.sh ./backup.sh **Expected behavior** A full backup file with the file necessary for the mongo to postgresql conversion. **Screenshots** ![image](https://github.com/amidaware/tacticalrmm/assets/21361769/5046ccad-358a-4666-bb33-df98bab6c319) **Additional context** Running the command that throws the error manually gives the same error: ![image](https://github.com/amidaware/tacticalrmm/assets/21361769/438df9c2-dc32-4a2a-b7d0-13edcc569839)

kerem closed this issue

2026-03-02 02:20:22 +03:00

kerem commented

2026-03-02 02:20:22 +03:00

Author

Owner

@dinger1986 commented on GitHub (Jul 13, 2023):

I just ran node /meshcentral/node_modules/meshcentral --dbexport on my trmm server and it worked fine.

Do you have anything else on that server?

@dinger1986 commented on GitHub (Jul 13, 2023): I just ran `node /meshcentral/node_modules/meshcentral --dbexport` on my trmm server and it worked fine. Do you have anything else on that server?

kerem referenced this issue

2026-03-14 04:25:02 +03:00

[GH-ISSUE #977] Automation Policies wont apply #2537