[SERVER-2202] couldn't unlink socket file /tmp/mongodb-28017.sockerrno:1 Operation not permitted skipping Created: 10/Dec/10 Updated: 30/Mar/12 Resolved: 28/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Matthew Ford | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Linux |
| Participants: |
| Description |
|
After upgrading to 1.6.5 (and applying the upstart workaround), when I start mongodb I see: Fri Dec 10 00:35:18 MongoDB starting : pid=12278 port=27017 dbpath=/var/lib/mongodb 64-bit Not sure how to release the socket so that the webadmin can start. |
| Comments |
| Comment by Matthew Ford [ 10/Dec/10 ] |
|
Yes this solved the issue. Thanks |
| Comment by Scott Hernandez (Inactive) [ 10/Dec/10 ] |
|
It looks like there is a permissions issue. Just delete the file. sudo rm /tmp/mongodb-28017.sock I'm assuming this came up because you started things up as root and didn't shutdown correctly. |