[SERVER-17652] Cannot start mongod due to "sockets higher than 1023 not being supported" Created: 19/Mar/15 Updated: 19/Sep/15 Resolved: 24/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Storage |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.0.2, 3.1.1 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Stennie Steneker (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | RPL 1 04/03/15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Issue Status as of Apr 02, 2015 ISSUE SUMMARY If a mongod process opens too many file descriptors early in the initialization process, the process may fail to start if later parts of the initialization process require the server to allocate a socket. For instance, this may arise when the mongod runs with the httpinterface option, and the storage engine needs to open a large number of file descriptors, as happens during recovery following an unclean shutdown. If you observe the following error, this may indicate that you've encountered this issue.
WORKAROUNDS Disable the httpinterface until mongod can effectively start with a smaller number of file descriptors. AFFECTED VERSIONS FIX VERSION Original descriptionThere are several community reports of users who have upgraded from 3.0.0 to 3.0.1 and are unable to restart mongodb, with an error message about sockets higher than 1023 not being supported, eg:
Some reports:
|
| Comments |
| Comment by Ramon Fernandez Marina [ 10/Apr/15 ] | ||||||||||||||||||
|
Hi leonty, apologies for not getting back to you sooner. In the future you may want to subscribe to mongodb-announce@googlegroups.com where we announce our releases. In this case you would have been able to download and test 3.0.2-rc0 (which had the same bits as 3.0.2) to confirm that this issue was actually addressed as early as April 2nd. | ||||||||||||||||||
| Comment by leonty [ 10/Apr/15 ] | ||||||||||||||||||
|
3.0.2 is finally released. Thank you! | ||||||||||||||||||
| Comment by leonty [ 30/Mar/15 ] | ||||||||||||||||||
|
Ramon, exactly. Restarts don't help. I ensured that the the upstart script sets needed limits. I also rised up limits globally for the "mongodb" user in /etc/security/limits.conf. Nothing helped. I had to downgrade mongodb to 3.0.0. | ||||||||||||||||||
| Comment by Greg White [ 30/Mar/15 ] | ||||||||||||||||||
|
I'm not able to restart one of my slaves once it gets in this state. I get the same error every time. Is there no workaround? | ||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 30/Mar/15 ] | ||||||||||||||||||
|
leonty, WiredTiger should only need to open lots of files when recovery is needed, so on the next restart the server should come up as recovery should not be needed. Are you saying that restarting after seeing the error above doesn't work? | ||||||||||||||||||
| Comment by leonty [ 30/Mar/15 ] | ||||||||||||||||||
|
But what's the workaround for 3.0.1? I can't just start the database... I have the following configuration:
| ||||||||||||||||||
| Comment by Githook User [ 26/Mar/15 ] | ||||||||||||||||||
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: (cherry picked from commit 2c6ab1eaae38caeee322f0c9afc4ef973fb667ea) | ||||||||||||||||||
| Comment by Githook User [ 26/Mar/15 ] | ||||||||||||||||||
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: (cherry picked from commit b9b1c95520824c377b4c800e6193d9855be1e14d) | ||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 20/Mar/15 ] | ||||||||||||||||||
|
Hi igor, as per the fixVersion we're targeting a 3.0.2 backport (the "backport approved" field went away). | ||||||||||||||||||
| Comment by Igor Canadi [ 20/Mar/15 ] | ||||||||||||||||||
|
It would be awesome if you guys could backport this to v3.0 branch. RocksDB creates a lot of files and we've run into this issue during our testing. | ||||||||||||||||||
| Comment by Githook User [ 19/Mar/15 ] | ||||||||||||||||||
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: | ||||||||||||||||||
| Comment by Githook User [ 19/Mar/15 ] | ||||||||||||||||||
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |