Skip to content

Is my Mongodb installation correct?

Solved General
27 2 8.5k 1
  • @phenomlab
    I reset my server and set it up again.
    save as video
    Can you check if it is installed properly?
    especially the mongodb part

    @ahmed thanks for the url. I’ll check this later.

  • @ahmed thanks for the url. I’ll check this later.

    @phenomlab
    Thank you for taking the time to answer my questions.

  • @phenomlab
    Thank you for taking the time to answer my questions.

    @ahmed anytime

  • @phenomlab

    What could be the reason why mongodb gives this error when trying to take a backup?

    root@localhost:~# sudo systemctl stop mongod
    root@localhost:~# sudo systemctl status mongod
    ○ mongod.service - MongoDB Database Server
         Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
         Active: inactive (dead) since Sun 2024-03-24 18:48:04 +03; 21s ago
           Docs: https://docs.mongodb.org/manual
        Process: 61116 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=0/SUCCESS)
       Main PID: 61116 (code=exited, status=0/SUCCESS)
            CPU: 2.034s
    
    Mar 24 18:47:01 localhost systemd[1]: Started MongoDB Database Server.
    Mar 24 18:47:01 localhost mongod[61116]: {"t":{"$date":"2024-03-24T15:47:01.540Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MON>
    Mar 24 18:48:04 localhost systemd[1]: Stopping MongoDB Database Server...
    Mar 24 18:48:04 localhost systemd[1]: mongod.service: Deactivated successfully.
    Mar 24 18:48:04 localhost systemd[1]: Stopped MongoDB Database Server.
    Mar 24 18:48:04 localhost systemd[1]: mongod.service: Consumed 2.034s CPU time.
    lines 1-14/14 (END)
    [6]+  Stopped                 sudo systemctl status mongod
    root@localhost:~# mongodump
    2024-03-24T18:49:15.964+0300    Failed: can't create session: failed to connect to mongodb://localhost/: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: localhost:27017, Type: Unknown, Last error: connection() error occurred during connection handshake: dial tcp 127.0.0.1:27017: connect: connection refused }, ] }
    root@localhost:~#
    root@localhost:~#
    root@localhost:~# mongodump --port 27017 -u "nodebb" -p "Em26452645" --db=nodebb --out=backup/ahmed
    2024-03-24T18:50:25.654+0300    Failed: can't create session: failed to connect to mongodb://localhost:27017/: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: localhost:27017, Type: Unknown, Last error: connection() error occurred during connection handshake: dial tcp 127.0.0.1:27017: connect: connection refused }, ] }
    root@localhost:~#
    
    
  • @phenomlab

    What could be the reason why mongodb gives this error when trying to take a backup?

    root@localhost:~# sudo systemctl stop mongod
    root@localhost:~# sudo systemctl status mongod
    ○ mongod.service - MongoDB Database Server
         Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
         Active: inactive (dead) since Sun 2024-03-24 18:48:04 +03; 21s ago
           Docs: https://docs.mongodb.org/manual
        Process: 61116 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=0/SUCCESS)
       Main PID: 61116 (code=exited, status=0/SUCCESS)
            CPU: 2.034s
    
    Mar 24 18:47:01 localhost systemd[1]: Started MongoDB Database Server.
    Mar 24 18:47:01 localhost mongod[61116]: {"t":{"$date":"2024-03-24T15:47:01.540Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MON>
    Mar 24 18:48:04 localhost systemd[1]: Stopping MongoDB Database Server...
    Mar 24 18:48:04 localhost systemd[1]: mongod.service: Deactivated successfully.
    Mar 24 18:48:04 localhost systemd[1]: Stopped MongoDB Database Server.
    Mar 24 18:48:04 localhost systemd[1]: mongod.service: Consumed 2.034s CPU time.
    lines 1-14/14 (END)
    [6]+  Stopped                 sudo systemctl status mongod
    root@localhost:~# mongodump
    2024-03-24T18:49:15.964+0300    Failed: can't create session: failed to connect to mongodb://localhost/: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: localhost:27017, Type: Unknown, Last error: connection() error occurred during connection handshake: dial tcp 127.0.0.1:27017: connect: connection refused }, ] }
    root@localhost:~#
    root@localhost:~#
    root@localhost:~# mongodump --port 27017 -u "nodebb" -p "Em26452645" --db=nodebb --out=backup/ahmed
    2024-03-24T18:50:25.654+0300    Failed: can't create session: failed to connect to mongodb://localhost:27017/: server selection error: server selection timeout, current topology: { Type: Single, Servers: [{ Addr: localhost:27017, Type: Unknown, Last error: connection() error occurred during connection handshake: dial tcp 127.0.0.1:27017: connect: connection refused }, ] }
    root@localhost:~#
    
    

    @ahmed the database needs to be running to use MongoDump.

  • @ahmed the database needs to be running to use MongoDump.

    @phenomlab

    Nodebb.org documentation states that Mongodb must be stopped before backup
    nodebb.org documentation should be updated
    I think I saw it wrong

    I will try as you say

  • @phenomlab

    Nodebb.org documentation states that Mongodb must be stopped before backup
    nodebb.org documentation should be updated
    I think I saw it wrong

    I will try as you say

    @ahmed I never stop the database when backing up. Never did it with mysql either. I’m not saying it’s right but it’s always worked for me and the backup schedules I’ve created for others who have used that to perform recovery.

  • @ahmed I never stop the database when backing up. Never did it with mysql either. I’m not saying it’s right but it’s always worked for me and the backup schedules I’ve created for others who have used that to perform recovery.

    @phenomlab

    I’m trying to take a backup while Mongodb is running, but this time it gives an authentication error.

    root@localhost:~# mongodump --port 27017 -u "nodebb" -p "Em26452645" --db=nodebb --out=backup/ahmed
    2024-03-24T19:15:41.690+0300    Failed: can't create session: failed to connect to mongodb://localhost:27017/: connection() error occurred during connection handshake: auth error: unable to authenticate using mechanism "SCRAM-SHA-256": (AuthenticationFailed) Authentication failed.
    root@localhost:~#
    root@localhost:~#
    root@localhost:~#
    root@localhost:~# mongodump
    2024-03-24T19:15:54.554+0300    Failed: error creating intents to dump: error getting database names: (Unauthorized) Command listDatabases requires authentication
    
    
  • @phenomlab

    I’m trying to take a backup while Mongodb is running, but this time it gives an authentication error.

    root@localhost:~# mongodump --port 27017 -u "nodebb" -p "Em26452645" --db=nodebb --out=backup/ahmed
    2024-03-24T19:15:41.690+0300    Failed: can't create session: failed to connect to mongodb://localhost:27017/: connection() error occurred during connection handshake: auth error: unable to authenticate using mechanism "SCRAM-SHA-256": (AuthenticationFailed) Authentication failed.
    root@localhost:~#
    root@localhost:~#
    root@localhost:~#
    root@localhost:~# mongodump
    2024-03-24T19:15:54.554+0300    Failed: error creating intents to dump: error getting database names: (Unauthorized) Command listDatabases requires authentication
    
    

    @ahmed are you backing up remotely?

    Try this - obviously, substitute where necessary to match your environment

    mongodump -u root --password 'secret' --authenticationDatabase admin
    
  • @ahmed are you backing up remotely?

    Try this - obviously, substitute where necessary to match your environment

    mongodump -u root --password 'secret' --authenticationDatabase admin
    

    @phenomlab
    I think it finally happened 🙂

    mongodump --port 27017 -u "nodebb" -p "Em26452645eses" --db=nodebb --out=backup/ahmed
    2024-03-24T20:39:20.788+0300    writing nodebb.sessions to backup/ahmed/nodebb/sessions.bson
    2024-03-24T20:39:20.792+0300    done dumping nodebb.sessions (21 documents)
    2024-03-24T20:39:20.805+0300    writing nodebb.objects to backup/ahmed/nodebb/objects.bson
    2024-03-24T20:39:20.811+0300    done dumping nodebb.objects (714 documents)
    
  • @phenomlab
    I think it finally happened 🙂

    mongodump --port 27017 -u "nodebb" -p "Em26452645eses" --db=nodebb --out=backup/ahmed
    2024-03-24T20:39:20.788+0300    writing nodebb.sessions to backup/ahmed/nodebb/sessions.bson
    2024-03-24T20:39:20.792+0300    done dumping nodebb.sessions (21 documents)
    2024-03-24T20:39:20.805+0300    writing nodebb.objects to backup/ahmed/nodebb/objects.bson
    2024-03-24T20:39:20.811+0300    done dumping nodebb.objects (714 documents)
    

    yuuuuu.png


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Mongo Completely Broken.

    General mongodb
    20
    3 Votes
    20 Posts
    3k Views
    @Sampo2910 said in Mongo Completely Broken.: I can see you cringing Yes, that does make me slightly uncomfortable but OK.
  • Mongodb or Redis

    General database mongodb redis
    29
    11 Votes
    29 Posts
    6k Views
    @Madchatthew still a great catch.
  • mongodb backup problem

    Moved Configure mongodb
    3
    1
    1 Votes
    3 Posts
    923 Views
    You might want to also review this post https://sudonix.org/topic/389/mongodb-backup-script
  • mongodb replica set

    Configure mongodb docker ansible
    11
    2 Votes
    11 Posts
    2k Views
    @veronikya said in mongodb replica set: The host’s local dns resolution is not configured. The problem of the host’s hosts being unable to be resolved in docker has been solved. Surprisingly Solution: Edit the /etc/resovel.conf file Add 127.0.0.53 One immediate issue I can think of here is that editing resolv.conf directly is no longer supported and not recommended (because the changes do not survive a reboot) - unless you install the resolvconf package?
  • 3 Votes
    2 Posts
    681 Views
    @DownPW This isn’t something I have readily available, and because I’m not entirely familiar with the database structure of NodeBB, it’s something that would require research and development in terms of script. I think it’d be quicker to ask this in the NodeBB forums.
  • Nodebb: failed to restore a mongo dump

    Solved Configure mongodb
    2
    1 Votes
    2 Posts
    763 Views
    @phenomlab In fact I specified the sub rep and not the rep DON’T DO THIS: nodebb@nodebbpwclonedb:~/nodebb$ sudo mongorestore --username admin --password XXXXXXXXXXXXXX --nsInclude nodebb.objects --drop /home/nodebb/nodebb_DB_20230107/nodebb/ BUT THIS : nodebb@nodebbpwclonedb:~/nodebb$ sudo mongorestore --username admin --password XXXXXXXXXXXXXX --nsInclude nodebb.objects --drop /home/nodebb/nodebb_DB_20230107/
  • Mongodb Authorisation.

    Solved General mongodb
    17
    2 Votes
    17 Posts
    3k Views
    @Sampo2910 I just saw this on the NodeBB community site and it seems very much in line with the issue you are experiencing. Worth a look I think https://community.nodebb.org/topic/16826/does-nodebb-work-with-mongodb-6-0
  • Issues with 2nd NodeBB installation

    Solved General
    22
    3 Votes
    22 Posts
    5k Views
    @cagatay yes, that will be fine. Just watch for potential caching conflicts as you will have two sites writing to the one instance of iframely.