[SERVER-20697] Running 'mongod.exe' with '--dbpath' containing the Cyrillic alphabet Created: 30/Sep/15 Updated: 02/Oct/15 Resolved: 01/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.1.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Zolotov Pavel | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Example: |
||||||||
| Participants: | |||||||||
| Description |
|
I want to run MongoDB to save data by the path, containing Cyrillic alphabet. Example: Thus mongod.exe does not start with an error ... [initandlisten] exception in initAndListen: 29 Data directory C:/Новая папка not found., terminating ... While this folder exists. And as is seen from example 'mongod.exe' write right path in console. May blame the interaction with WIndows regard Cyrillic symbols. |
| Comments |
| Comment by Spencer Jackson [ 01/Oct/15 ] | ||
|
Thank you for reporting that you've encountered this. I believe this is another manifestation of | ||
| Comment by Zolotov Pavel [ 01/Oct/15 ] | ||
Thank you. Perhaps the fact that Windows takes the path is not UTF-8, and in Windows-1251. Although this is just a guess, because I do not know exactly how the interplay between Mongo and Windows. | ||
| Comment by Zolotov Pavel [ 01/Oct/15 ] | ||
I had to choose Windows as the operating system.
This result is quite expected: C:\>md "Новая папка" C:\>dir "C:/Новая папка" Содержимое папки C:\Новая папка 01.10.2015 12:27 <DIR> . | ||
| Comment by Ramon Fernandez Marina [ 30/Sep/15 ] | ||
|
kaloian.manassiev is able to reproduce this behavior, but is not clear yet where the bug is. We'll post updates to this ticket as we find out more. | ||
| Comment by Ramon Fernandez Marina [ 30/Sep/15 ] | ||
|
Azriel, I'm not able to reproduce the same behavior on linux, so this may be indeed related to how Windows handles Cyrillic symbols or how your system is configured: you may need to change your system locale. Also, what happens when you run the following from a command prompt?
|