This looks like another regression of SERVER-9818 on 2.6. It may also be related to SERVER-15389.
Tested version were:
- 2.6.4
- 2.6.8
- 2.6.9-rc0
- 2.6.2
- 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.
- is related to
-
SERVER-9818 Problems when starting MongoDB with > 1023 FDs
- Closed
-
SERVER-15389 Cannot start mongod when opening too many files before getting a socket
- Closed
- related to
-
SERVER-17652 Cannot start mongod due to "sockets higher than 1023 not being supported"
- Closed