[SERVER-5242] mongod locks up on OSX after less than two days of uptime Created: 07/Mar/12 Updated: 15/Aug/12 Resolved: 11/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Arun Bhalla | Assignee: | Ben Becker |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
sys info: Darwin erh2.10gen.cc 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 BOOST_LIB_VERSION=1_40 |
||
| Attachments: |
|
| Operating System: | OS X |
| Participants: |
| Description |
|
I installed mongodb 2.0.3 for OSX on Monday on my workstation for development use. It's been working fine until just a few minutes ago, when it refused new DB connections. I was running mongod in a separate terminal in non-daemon mode; the process wouldn't respond to Ctrl-C. Ultimately I had to kill -9 the process. Console output before killing the process:
|
| Comments |
| Comment by Ben Becker [ 11/Apr/12 ] | |||||||||||||||||||||||||||||||||
|
Thanks Arun; please feel free to reopen this issue if you encounter this again. | |||||||||||||||||||||||||||||||||
| Comment by Arun Bhalla [ 11/Apr/12 ] | |||||||||||||||||||||||||||||||||
|
No. The mongod process has been running for a month with no issue. | |||||||||||||||||||||||||||||||||
| Comment by Ben Becker [ 11/Apr/12 ] | |||||||||||||||||||||||||||||||||
|
Hi Arun, Have you run into any issues since increasing the file descriptor limit? | |||||||||||||||||||||||||||||||||
| Comment by Ben Becker [ 12/Mar/12 ] | |||||||||||||||||||||||||||||||||
|
Thanks, please let me know if you run into this issue again. If everything works correctly with the increased limits, then this issue should be resolved by | |||||||||||||||||||||||||||||||||
| Comment by Arun Bhalla [ 12/Mar/12 ] | |||||||||||||||||||||||||||||||||
|
OK, I've restarted mongod with a limit of 4096 files. | |||||||||||||||||||||||||||||||||
| Comment by Ben Becker [ 10/Mar/12 ] | |||||||||||||||||||||||||||||||||
|
Hi Arun, It looks like you're running out of file descriptors. The results of ulimit show a maximum of 256 open files and connections, which includes database files and socket connections. Could you try increasing the limit as mentioned in this wiki page? | |||||||||||||||||||||||||||||||||
| Comment by Arun Bhalla [ 09/Mar/12 ] | |||||||||||||||||||||||||||||||||
|
Here's the ulimit -a output.
I have just a little bit more of the log output from Wednesday:
Let me know if you want me to run mongod any differently for debugging purposes, or if I should run any commands if this should happen again. | |||||||||||||||||||||||||||||||||
| Comment by Ben Becker [ 09/Mar/12 ] | |||||||||||||||||||||||||||||||||
|
Hi Arun, Could you run ulimit -a and paste the results? If mongod runs as a different user, please run this command as the other user (e.g. sudo su <username> then ulimit -a). Do you still have the full log output from the console? |