Error: No suitable servers found / jetmongod (MongoDB) Troubleshooting

In some cases, the mongod service has been down and you get this error through the shell or GUI.

General Error: 
Error: No suitable servers found (serverSelectionTryOnce set): [connection refused calling ismaster on 'localhost:27217']
typically this No suitable servers found can be caused by one of the following:

1. The partition that JetApps is located in is "full", which can be verified by using df -h if you notice that the partition is full, please try making some space and restarting the service.
  1. verify that the socket file is owned by user/group mongod:mongod: the file can be found at: /tmp/mongodb-27217.sock
  2. Verify the file permissions for /tmp are set to 1777

 


2. We also found cases where JetMongo fails to start due to this error which can be caused by having localhost set to ipv6 instead of ipv4 in the /etc/hosts file. 

# Do not remove the following line, or various programs
# that require network functionality will fail.
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

Please try setting the localhost to the default ipv4 IP (127.0.0.1) 

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

and then restarting the jetbackup5d service:
systemctl restart jetbackup5d

 

3. Verify another cron or process such as lfd is not killing the process. For example, the logs below show that jetmongod is being killed. 

[root@qa1 cron.d]# tail -f /var/log/lfd.log
Feb 26 09:28:27 qa1 lfd[451585]: *User Processing* PID:447832 Kill:1 User:mongod VM:1499(MB) EXE:/usr/local/jetapps/usr/bin/mongod CMD:/usr/local/jetapps/usr/bin/mongod --quiet -f /usr/local/jetapps/etc/mongod.conf run
Feb 26 09:29:27 qa1 lfd[456526]: *User Processing* PID:451649 Kill:1 User:mongod VM:1499(MB) EXE:/usr/local/jetapps/usr/bin/mongod CMD:/usr/local/jetapps/usr/bin/mongod --quiet -f /usr/local/jetapps/etc/mongod.conf run
Feb 26 09:30:27 qa1 lfd[462225]: *User Processing* PID:457624 Kill:1 User:mongod VM:1499(MB) EXE:/usr/local/jetapps/usr/bin/mongod CMD:/usr/local/jetapps/usr/bin/mongod --quiet -f /usr/local/jetapps/etc/mongod.conf run
Feb 26 09:31:28 qa1 lfd[466836]: *User Processing* PID:463118 Kill:1 User:mongod VM:1499(MB) EXE:/usr/local/jetapps/usr/bin/mongod CMD:/usr/local/jetapps/usr/bin/mongod --quiet -f /usr/local/jetapps/etc/mongod.conf run
Feb 26 09:32:28 qa1 lfd[471770]: *User Processing* PID:468109 Kill:1 User:mongod VM:1499(MB) EXE:/usr/local/jetapps/usr/bin/mongod CMD:/usr/local/jetapps/usr/bin/mongod --quiet -f /usr/local/jetapps/etc/mongod.conf run

 

To whitelist in LFD:

  • Go to "ConfigServer Security and Firewall"
  • Find the "lfd - Login Failure Daemon" section
  • In the "Edit lfd ignore file" dropdown menu, find "Process Tracking" or edit the /etc/csf/csf.pignore file
  • Add the following config: 
exe:/usr/local/jetapps/usr/bin/jetmongod
  • Restart CSF with csf -r

4. It is likewise important to ensure that your server is not blocking localhost traffic over port 27217. You can use the Ncat command to verify that traffic is allowed:

nc -v localhost 27217
Ncat: Connected to 127.0.0.1:27217.

If instead you get the output nc: connect to localhost (127.0.0.1) port 27217 (tcp) failed: Connection refused, you will need to work with your qualified systems administrator to resolve this.

 

 

  • 2 utilizatori au considerat informația utilă
Răspunsul a fost util?

Articole similare

Why are my Directories showing Invalid Dates when browsing?

Object-based storage such as AWS S3 destinations does not include any modified dates for...

Email Notifications Are Not Being Sent

JetBackup 5 uses Notification Integrations to send Notifications based on the configured...

What are the level of Alerts in JetBackup 5?

JetBackup 5 now has only 3 Alert levels compared to JetBackp 4. All 3 levels will appear on the...

Create Destination Error: This destination path is already owned by other destination

On JetBackup 5, you may notice the following error when creating a destination that uses the same...

Common Backup Job Exclude List for DirectAdmin Accounts

Information regarding how to exclude certain files/folders from a backup in JetBackup 5 can be...