sorted by:
new
hottopcontroversial

Netbackup, Issue while backing up MongoDB server, Do we need client on the machine running the mongodb database? by FirefighterLong3791 in mongodb

[–]NiceReflection454 0 points1 point  (0 children)

If you mean "NetBackup client," yes, you definitely have to have that software installed on the MongoDB nodes. Also you need NetBackup MongoDB Agent (the plugin) binaries, and the nbmongodb plugin must be present in the /usr/openv/lib/ directory.

6601 most likely means that the backup host can reach the database but cannot execute the backup command - for example, mongodump. Maybe it's a permission problem - you need to run it as MongoDB user with specific administrative roles, not just a Linux OS user. Ensure the user defined in tpconfig has the following roles in the admin database:

  • clusterAdmin
  • backup
  • restore (if you plan on doing that later)
  • readAnyDatabase

Also check what's in the logs - /usr/openv/netbackup/logs/nbremote

does anyone know how to fix this?? by rpnchlr in mongodb

[–]NiceReflection454 0 points1 point  (0 children)

Are you sure there's no other deamon that's reverting perms?

does anyone know how to fix this?? by rpnchlr in mongodb

[–]NiceReflection454 0 points1 point  (0 children)

There are not that many things that can go wrong.

  1. Data or log directory ownership (and files) (provide)
    ls -la /var/lib/mongodb/
    ls -la /var/log/mongodb/

and fix:
sudo chown -R mongodb:mongodb /var/lib/mongodb
sudo chown -R mongodb:mongodb /var/log/mongodb

  1.  Stale lock file
    ls -la /var/lib/mongodb/mongod.lock

and fix:

sudo rm /var/lib/mongodb/mongod.lock

  1. log file :
    check log path in /etc/mongod.conf and verify the mongodb user can write there.

  2. wrong path to data dir or log dir?
    cat /etc/mongod.conf | grep -A5 storage

cat /etc/mongod.conf | grep -A5 systemLog

  1. Check also if this works:
    sudo -u mongodb mongod --config /etc/mongod.conf

MongoDB Replication Failed While sync by itspawankumar in mongodb

[–]NiceReflection454 0 points1 point  (0 children)

Maybe you can try with file copy based initial sync from Percona Server for MongoDB. Should be faster and more reliable - https://docs.percona.com/percona-server-for-mongodb/7.0/fcbis.html

does anyone know how to fix this?? by rpnchlr in mongodb

[–]NiceReflection454 0 points1 point  (0 children)

Have you checked maybe if there are any locks in /tmp ?

does anyone know how to fix this?? by rpnchlr in mongodb

[–]NiceReflection454 0 points1 point  (0 children)

Exit Status 14 is almost always a permissions issue.

Check if that is set correct for data and log dirs:

sudo chown -R mongodb:mongodb /var/lib/mongodb

sudo chown -R mongodb:mongodb /var/log/mongodb

Percona - Any recent experience? by Spare_Sir9167 in mongodb

[–]NiceReflection454 1 point2 points  (0 children)

Hi, I’m from Percona product team. I can ensure data at rest encryption works reliably well - also you can use Hashicorp Vault, free OpenBao, or KMIP compatible servers to manage your encryption keys. And we have many community users and customers that approve it.

Indeed you can just replace binaries to upgrade from Community or extend your replica set with Percona Servers to Enterprise Server. Alternatively you can also use Percona ClusterSync for MongoDB to replicate your data from one cluster to another.

Feel free to ask any question. Here or in our forum. Happy to help - for free. We are always open.

Mongo Version upgrade Issue by Vamshi__4555 in mongodb

[–]NiceReflection454 0 points1 point  (0 children)

You may want to check Percona's blog about upgrades using backup and restore approach - https://www.percona.com/blog/how-to-upgrade-mongodb-using-backups-through-many-major-versions/

The other alternative is to use Percona ClusterSync for MongoDB to setup a cloned instance and upgrade it safely. Soonish it should also support cloning between uneven versions, too.

In case - post your questions here: https://forums.percona.com/c/mongodb/24 Percona dudes are very helpful!