[SERVER-39977] mongos auto restart and report error Created: 06/Mar/19  Updated: 06/Mar/19  Resolved: 06/Mar/19

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

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

Attachments: Text File mongo.txt    
Operating System: ALL
Participants:

 Description   
  • mongos version : 3.4.17
  • mongos log:

2019-03-06T09:28:02.100+0800 I SHARDING [mongosMain] mongos version v3.4.17
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] git version: 7c14a47868643bb691a507a92fe25541f998eca4
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] allocator: tcmalloc
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] modules: none
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] build environment:
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain]     distmod: rhel62
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain]     distarch: x86_64
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain]     target_arch: x86_64
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] db version v3.4.17
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] git version: 7c14a47868643bb691a507a92fe25541f998eca4
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] allocator: tcmalloc
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] modules: none
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] build environment:
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain]     distmod: rhel62
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain]     distarch: x86_64
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain]     target_arch: x86_64
2019-03-06T09:28:02.100+0800 I CONTROL  [mongosMain] options: { config: "/data3/mongos.conf", net: 

{ port: 47017 }

, processManagement: { fork: true }, security: { clusterAuthMode: "keyFile", keyFile: "/data3/keyFile" }, setParameter: { enableLocalhostAuthBypass: "true" }, sharding: { configDB: "cfgsvr/172.19.8.70:47019,172.19.8.71:47019,172.19.9.70:47019" }, systemLog: { destination: "file", logAppend: false, path: "/data3/mongos/log.txt" } }
2019-03-06T09:28:02.109+0800 E NETWORK  [mongosMain] listen(): bind() failed Address already in use for socket: 0.0.0.0:47017
2019-03-06T09:28:02.109+0800 E NETWOR



 Comments   
Comment by Danny Hatcher (Inactive) [ 06/Mar/19 ]

Hello,

The node did not start because there is already something using port 47017:

06T09:28:02.109+0800 E NETWORK  [mongosMain] listen(): bind() failed Address already in use for socket: 0.0.0.0:47017
2019-03-06T09:28:02.109+0800 E NETWOR

There may be a mongos process running already. I can't speak to why the process may have started without you initiating it but if you are running the mongos as a service the system may be configured to restart it automatically if it fails.

The SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to a bug, I will now close it. If you need further assistance troubleshooting, please post on the mongodb-user group or on Stack Overflow with the mongodb tag. Our Technical Support page may also be of help.

Thank you,

Danny

Comment by Gen Lin [ 06/Mar/19 ]

Question:

Q1:why mongos start failure?

Q2:we didn't start mongos , why mongos auto restart?

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