-
Notifications
You must be signed in to change notification settings - Fork 594
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
MeshCentral v1.1.37 | Linux | k3s/Container | PostgreSQL: autobackup not working since v1.1.34 #6676
Comments
This will be because you haven't set the path correctly, but also, u shouldn't need to set it? You currently have it set to The path needs to be absolute, not just a file name. Have u tried removing that line, restarting the container, and then seeing if it can do the If so what container image are u using? As im sure the pg_dump is included in our image for this reason |
I'll just try that - but that seems to be like it was before...?
That's what I thought too. But I couldn't find
|
Just removed this config line and tried it again: |
Oh I've just realised! We include mongodb in the docker image And not the postgres! This has to be installed manually inside the container!!! |
Great, thanks a lot :) But it seemed to be working until v1.1.33 - were these postgres files included until then? |
Describe the bug
Since v1.1.34, my MeshCentral instance doesn't makes any further backups.
I do see following server error message:
WARNING: Unable to find pg_dump, PostgreSQL database auto-backup will not be performed.
Nothing has been changed on my side, a pg_dump location wasn't specified before. But even after setting the default value (see below), the backups doesn't work anymore.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect a working backup as it was before.
Screenshots
Server Software (please complete the following information):
Additional context
I have tried configuring additional values that seems to be introduced with e58d659
Here are my autobackup configurations:
Before, my backups were working flawlessly. It seems that with the introducion of these new values, something got messed up on my server...?
here the console output of
backupconfig
:Some values - e.g.
pgDumpPath
- are not visible here. Is this normal?Your config.json file
EDIT:
Here the console ouptut of autobackup:
The text was updated successfully, but these errors were encountered: