[SERVER-40578] Not able to log in into mongodb server - E QUERY [js] Error: network error while attempting to run command 'isMaster' on host '127.0.0.1:37017' : connect@src/mongo/shell/mongo.js:328:13 @(connect):1:6 exception: connect failed Created: 11/Apr/19  Updated: 22/Apr/19  Resolved: 22/Apr/19

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Madhu N Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File mongod.log-bak    
Operating System: ALL
Participants:

 Description   

I am facing issue in login into mongodb server, when i check ps -eaf | grep mongo, proces still running but not able to login into mongodb server.

Below are the error  I am facing

 

MongoDB  version: 4.0.5

E QUERY [js] Error: network error while attempting to run command 'isMaster' on host '127.0.0.1:37017' :
connect@src/mongo/shell/mongo.js:328:13
@(connect):1:6
exception: connect failed

But when I restart the service it works for some time and again I face log in issue.

Thanks & Regards

Madhu



 Comments   
Comment by Danny Hatcher (Inactive) [ 22/Apr/19 ]

Hello Madhu,

The SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to a bug, we do not keep it open indefinitely. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag.

Danny

Comment by Madhu N [ 16/Apr/19 ]

Hi Danny,

 

Thanks for the response again.

Yes, that is why I am wondering  I see no shutdown logs exists on log file.

Yes both the mongod process running on same host.

one is running as a root user - which is running fine 

second one running as a mongodb user -  which has issue

FYI 

I made below changes -  I think everything looks fine.

vi /etc/security/limits.d/99-mongodb.conf

  • - nproc 64000
  • - nofile 64000
  • - fsize unlimited
  • - cpu unlimited
  • - memlock unlimited
  • - as unlimited
  • - rss unlimited

 

I will keep updated here in some time If I face any issues on this.

If no more issue I will update the same to close the ticket.

If you are okay, can this ticket be opened until I update on the same

 

Thanks & Best Regards

Madhu

Comment by Danny Hatcher (Inactive) [ 15/Apr/19 ]

There are no shutdown messages in the log which indicate that the process was hard-killed by either a user or the operating system. Are both of your mongod processes on the same host? If so, it is possible that you are experiencing out-of-memory issues due to both processes attempting to use the same memory resource. We *strongly recommend* that a Production mongod process is the only intensive process on the server.

If you split your mongod processes to different servers do you still see the issue?

Thanks,

Danny

Comment by Madhu N [ 11/Apr/19 ]

 Hi Danny,

Please find the requested complete log attached.

mongod.log-bak

And in the same server I am running another mongod service with same configuration port 27017 which has no issue running. But only issue I am facing in second service which is port 37017. 

( two services are different for different application)

Configuration is same  as given below.

---------------------------------------------------------------------------------

[mongodb@host]$ cat /etc/mongodIMS.conf                        // port 37017 
systemLog:
destination: file
path: "/mongodbIMS/log/mongod.log"
logAppend: true
logRotate: reopen
timeStampFormat: ctime
net:
bindIp: 0.0.0.0
port: 37017
storage:
dbPath: "/mongodbIMS/data/"
processManagement:
fork: true
pidFilePath: /mongodbIMS/data/mongod.pid
timeZoneInfo: /usr/share/zoneinfo
security:
authorization: enabled

----------------------------------------------------------------------------

[mongodb@host]$ cat /etc/mongod.conf                            //port 27017
systemLog:
destination: file
path: "/mongodb/log/mongod.log"
logAppend: true
logRotate: reopen
timeStampFormat: ctime
net:
bindIp: 0.0.0.0
port: 27017
storage:
dbPath: "/mongodb/data/"
processManagement:
fork: true
pidFilePath: /mongodb/data/mongod.pid
timeZoneInfo: /usr/share/zoneinfo
security:
authorization: enabled

Comment by Danny Hatcher (Inactive) [ 11/Apr/19 ]

Hello Madhu,

Please attach your full mongod log file covering the time frame from a restart until you start encountering issues.

Thanks,

Danny

Generated at Thu Feb 08 04:55:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.