[SERVER-17653] ERROR: socket XXX is higher than 1023; not supported on 2.6.* Created: 19/Mar/15  Updated: 19/Sep/15  Resolved: 26/Mar/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.6.9
Fix Version/s: 2.6.10

Type: Bug Priority: Major - P3
Reporter: James O'Leary Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-17652 Cannot start mongod due to "sockets h... Closed
is related to SERVER-9818 Problems when starting MongoDB with >... Closed
is related to SERVER-15389 Cannot start mongod when opening too ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

The simplest way to repro was to set the oplogSize high enough (smallfiles true helps)

Participants:

 Description   

This looks like another regression of SERVER-9818 on 2.6. It may also be related to SERVER-15389.

Tested version were:

  1. 2.6.4
  2. 2.6.8
  3. 2.6.9-rc0
  4. 2.6.2
  5. 2.6.0

2015-03-18T18:01:55.364+0000 [initandlisten] waiting for connections on port 10001
2015-03-18T18:01:55.365+0000 [websvr] ERROR: socket 2057 is higher than 1023; not supported
2015-03-18T18:01:55.385+0000 [initandlisten] connection accepted from 10.126.10.236:36340 #1 (1 connection now open)
2015-03-18T18:01:55.385+0000 [rsStart] replSet I am luu437p:10001
2015-03-18T18:01:55.385+0000 [conn1] end connection 10.126.10.236:36340 (0 connections now open)
2015-03-18T18:01:55.399+0000 [rsStart] replSet STARTUP2
2015-03-18T18:01:55.400+0000 [rsSync] replSet SECONDARY
2015-03-18T18:01:55.400+0000 [rsMgr] replSet info electSelf 0
2015-03-18T18:01:56.401+0000 [rsMgr] replSet PRIMARY

My repro did not cause the server to fail to launch as the error was reported on the REST interface.

However, the original source did report a failure to launch of the mongod process at lease once:

2015-03-07T13:51:51.441+0100 [initandlisten] ERROR: socket 1088 is higher than 1023; not supported
2015-03-07T13:51:51.441+0100 [initandlisten] now exiting
2015-03-07T13:51:51.441+0100 [initandlisten] dbexit:

A subsequent restart allowed the process to start.



 Comments   
Comment by Githook User [ 27/Mar/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17653 Early allocate port for the HTTP interface

(cherry picked from commit 8136a4d3138ab17188e6eab14c42cf61444f901b)
Branch: v3.0
https://github.com/mongodb/mongo/commit/3830ebe12436c48cbf30176e4714a688b6a758fa

Comment by Githook User [ 26/Mar/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17653 Early allocate port for the HTTP interface
Branch: v2.6
https://github.com/mongodb/mongo/commit/19439b096459f0944f09e161375e93ec16c028dd

Comment by Githook User [ 26/Mar/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17653 Early allocate port for the HTTP interface
Branch: master
https://github.com/mongodb/mongo/commit/8136a4d3138ab17188e6eab14c42cf61444f901b

Comment by Eliot Horowitz (Inactive) [ 19/Mar/15 ]

SERVER-17652

Comment by James O'Leary [ 19/Mar/15 ]

Dev Only
This may be SERVER-17652.

BUT they are for different versions.(Then again, SERVER-17652 may be SERVER-15389)

Generated at Thu Feb 08 03:45:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.