MeshCentral fresh Install: WARNUNG: Unable to find mongodump, MongoDB database auto-backup will not be performed

NethServer Version: 7.9.2009
Module: MeshCentral

@mrmarkuz

Hi Markus

On a freshly installed NethServer as VM on Proxmox inside a Hetzner Cloud, I’m getting the following error on first log-in on MeshCentral. The server is completly up-to date as from NOW !

MeshCentral is installed as virtualhost with working LE SSL certs. NethServer has only one NIC, Internet / Firewalling is done with an OPNsense. LE is done by NethServer.

During the install of MeshCentral (done with SSH from remote) no issues were reported…

The Problem?

WARNUNG: Unable to find mongodump, MongoDB database auto-backup will not be performed.

How can this be fixed? (I suppose installing mongodump, but which version and how?).
I didn’t get this error the last time I installed MeshCentral (a few months ago).

Thanks iA!

My 2 cents
Andy

1 Like

I need to check, maybe something changed in newer versions of meshcentral…

1 Like

i see a similar problem on one of my vms.
and yes its with meshcentral latest.

1 Like
3 Likes

@pike

I installed last night, I still don’t see any Backup (yet).
It could be OK, but I’ll have to wait until tomorroy to verify…

At the moment, /var/lib/nethserver/meshcentral/backup is still empty…

My 2 cents
Andy

You may create a symlink in /usr/bin to /opt/rh/rh-mongodb36/root/usr/bin/mongodump, this way mongodump is found by meshcentral and the message should disappear.
I’m going to add the symlink in the next update.

1 Like

@mrmarkuz

Hi

Might be a bit difficult:

seems a “rh” is missing in /opt/rh/rh-mongodb36/root/usr/bin/mongodump

But if the path is corrected, your solution works!
Sorry, was a bit to early. the error still remains.

Thanks!

My 2 cents
Andy

1 Like

Nethserver-meshcentral depends on rh-mongodb36, so it should be installed…

[root@testserver2 ~]# yum deplist nethserver-meshcentral
...
  dependency: rh-mongodb36
   provider: rh-mongodb36.x86_64 3.0-18.el7.sc1

EDIT:

Yes, you are right, I’ll correct my post…

Seems to be all there…

1 Like

A reboot was needed - i suspected as much…

You know the old german saying:

“Reboot tut immer gut”…

freely translated into english:
“A reboot always does a lot of good”…

:slight_smile:

The error message is now gone.
Maybe a restart of the services would have been enough…

My 2 cents
Andy

1 Like

like this
:slight_smile:

more precisely:

ln -s /opt/rh/rh-mongodb36/root/usr/bin/mongodump /usr/bin/mongodump

:slight_smile: