Is my Mongodb installation correct?

[phenomlab]

@ahmed Sorry - should have been clearer. What I meant by config.json is the config file from your NodeBB installation. From what I see, you have authentication enabled in the config, but it doesn’t work?

[phenomlab]

@ahmed before you can enable authorization, a valid admin user needs to exist in the database. Try disabling the authorization for the time being, restart MongoDB and then see if you can login.

I expect this will work, but once you are able to login, put the authorization back, restart MongoDB and then try it again.

For more information, see

https://www.mongodb.com/docs/manual/tutorial/configure-scram-client-authentication/#create-the-user-administrator

[ahmed]

@phenomlab

root@localhost:~# sudo systemctl status mongod
× mongod.service - MongoDB Database Server
     Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2024-03-23 21:55:25 +03; 58s ago
       Docs: https://docs.mongodb.org/manual
    Process: 62746 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=14)
   Main PID: 62746 (code=exited, status=14)
        CPU: 60ms

Mar 23 21:55:25 localhost systemd[1]: Started MongoDB Database Server.
Mar 23 21:55:25 localhost mongod[62746]: {"t":{"$date":"2024-03-23T18:55:25.275Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MON>
Mar 23 21:55:25 localhost systemd[1]: mongod.service: Main process exited, code=exited, status=14/n/a
Mar 23 21:55:25 localhost systemd[1]: mongod.service: Failed with result 'exit-code'.

[phenomlab]

@ahmed can you post the content of /etc/mongod.conf

[ahmed]

@phenomlab said in Is my Mongodb installation correct?:

/etc/mongod.conf

# mongod.conf

# for documentation of all options, see:
#   http://docs.mongodb.org/manual/reference/configuration-options/

# Where and how to store data.
storage:
  dbPath: /var/lib/mongodb
#  engine:
#  wiredTiger:

# where to write logging data.
systemLog:
  destination: file
  logAppend: true
  path: /var/log/mongodb/mongod.log

# network interfaces
net:
  port: 27017
  bindIp: 127.0.0.1


# how the process runs
processManagement:
  timeZoneInfo: /usr/share/zoneinfo

security:
  authorization: enabled

#operationProfiling:

#replication:

#sharding:

## Enterprise-Only Options:

#auditLog:

[phenomlab]

@ahmed does the database service start if you remove the below

security:
  authorization: enabled

[ahmed]

@phenomlab said in Is my Mongodb installation correct?:

does the database service start if you remove the below

× mongod.service - MongoDB Database Server
     Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2024-03-24 04:52:10 +03; 12s ago
       Docs: https://docs.mongodb.org/manual
    Process: 64261 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=14)
   Main PID: 64261 (code=exited, status=14)
        CPU: 50ms

Mar 24 04:52:10 localhost systemd[1]: Started MongoDB Database Server.
Mar 24 04:52:10 localhost mongod[64261]: {"t":{"$date":"2024-03-24T01:52:10.940Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MON>
Mar 24 04:52:10 localhost systemd[1]: mongod.service: Main process exited, code=exited, status=14/n/a
Mar 24 04:52:10 localhost systemd[1]: mongod.service: Failed with result 'exit-code'.

[ahmed]

root@localhost:~# sudo chown -R mongodb:mongodb /var/lib/mongodb
root@localhost:~# sudo chown mongodb:mongodb /tmp/mongodb-27017.sock
root@localhost:~# sudo service mongod restart

root@localhost:~# sudo systemctl status mongod
● mongod.service - MongoDB Database Server
     Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2024-03-24 05:27:54 +03; 12s ago
       Docs: https://docs.mongodb.org/manual
   Main PID: 64421 (mongod)
     Memory: 170.8M
        CPU: 1.279s
     CGroup: /system.slice/mongod.service
             └─64421 /usr/bin/mongod --config /etc/mongod.conf

Mar 24 05:27:54 localhost systemd[1]: Started MongoDB Database Server.
Mar 24 05:27:54 localhost mongod[64421]: {"t":{"$date":"2024-03-24T02:27:54.700Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MON

502 Bad Gateway
nginx/1.18.0 (Ubuntu) happy ending when I log in to my website

[phenomlab]

@ahmed that would have been my next suggestion in relation to permissions. Glad you got it working

[ahmed]

@phenomlab

[phenomlab]

@ahmed that’s normal if you haven’t started your nodebb instance, or competed the installation yet.

[ahmed]

@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

[phenomlab]

@ahmed can you provide me with a url I can reach the installation on? If you’d rather not place this here, you can use the PM to do so.

[phenomlab]

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

[ahmed]

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

[phenomlab]

@ahmed anytime

[ahmed]

@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]

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

[ahmed]

@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]

@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.