[SERVER-8910] Error while starting 2.4.0-rc2 on linux machine Created: 08/Mar/13 Updated: 11/Jul/16 Resolved: 08/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Rachit Mittal | Assignee: | Gregor Macadam |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Production |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Fri Mar 8 09:44:54.274 [initandlisten] MongoDB starting : pid=8998 port=27017 dbpath=/logs/test 64-bit host=ip-10-30-140-110 Fri Mar 8 09:44:54.373 [initandlisten] exception in initAndListen std::exception: locale::facet::_S_create_c_locale name not valid, terminating |
| Comments |
| Comment by Tad Marshall [ 12/Apr/13 ] |
|
I hit this on a new build on a Solaris 11 VirtualBox instance created from a "Import Appliance": OracleSolaris11_1-VM.tgz (OracleSolaris11_1.ova). The mongod I was running was built from source, but I don't know much about how the Solaris instance was configured. The "export LC_ALL=C" got me past the error; thanks for the tip! |
| Comment by Adam Comerford [ 08/Mar/13 ] |
|
In this specific case from the original report, the root user was being used to start mongod (not recommended in general). Since it is somewhat unclear as to how this was being done (sudo, su, actual log in) it is also unclear as to whether this was an issue with locale settings for the root user or some issue with the method used to invoke as root. If you see issues like this, the export (depending on your environment) of the LC_ALL variable as outlined above will temporarily fix it. If the issues is deeper, and (for example) there is an actual problem with /etc/locale.gen then for a full fix you need to correct the file to contain only valid locale entries, run the locale-gen command and then logout and back in. Occasionally, this can just be a case of problematic environment variables for a session - so a logout and a re-login can sometimes fix the problems without any other intervention. |
| Comment by Gregor Macadam [ 08/Mar/13 ] |
|
Re-opening so we can publicly document the solution. |
| Comment by Gregor Macadam [ 08/Mar/13 ] |
|
Hi |
| Comment by Rachit Mittal [ 08/Mar/13 ] |
|
Got it started by |
| Comment by Rachit Mittal [ 08/Mar/13 ] |
|
Can you guide me to the duplicate ticket stating the solution |