-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore not working #134
Comments
I am not sure why, I think it works sometime but not always. But unfortunately, i don't have bandwidth to address this now. |
related to #114 |
Here's a clearer version in English: No, it’s not. I found the issue: the validation:
database:
host: 127.0.0.1
port: 27017
database: db_name However, there’s a new problem: time="2024-10-27T15:20:44Z" level=info msg="Running restore command with : mongorestore --archive=/storage/apartx-kz/apartx-kz-1730015066.gz --gzip --host "***" --port 27017 -u \"admin\" --nsInclude apartx.* --authenticationDatabase admin " plan=apartx-kz
time="2024-10-27T15:20:44Z" level=info msg="Validation: restore backup with : mongorestore --archive=/storage/apartx-kz/apartx-kz-1730015066.gz --gzip --host 127.0.0.1 --port 27017 --nsInclude apartx.* " plan=apartx-kz
2024/10/27 15:20:47 "GET http://10.42.3.126:8090/status HTTP/1.1" from 10.42.3.1:44596 - 200 57B in 47.848µs The logs indicate that the restore process begins and shows the correct command for it. However, while the validation command runs, it seems the actual restore command is not being executed. The restore process isn’t starting because the necessary code for it is missing in the source files. |
Backup work, but restore throws panic
Manual exec cmd that mgob produce is working
Startup logs:
The text was updated successfully, but these errors were encountered: