[SERVER-8606] Remove to change frightening OpenVZ message at mongod startup Created: 18/Feb/13 Updated: 11/Jul/16 Resolved: 08/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | 2.5.3 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Erik Beebe | Assignee: | Ian Whalen (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux OpenVZ |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
When mongod detects an environment using OpenVZ, it logs a warning: [initandlisten] ** WARNING: You are running in OpenVZ. This is known to be broken!!! This is a holdover from much older versions of OpenVZ - this appeared to first be reported more than 2.5 years ago in |
| Comments |
| Comment by Fernando Kosh [ 09/Aug/14 ] |
|
+1 on this warning triggers on Debian 7. I am running mongodb in OpenVZ for over 8 months and have not seen issues. |
| Comment by Vincent [ 30/May/14 ] |
|
This warning triggers even on distribs not related with RHEL (Debian in my case). |
| Comment by auto [ 08/Oct/13 ] |
|
Author: {u'username': u'IanWhalen', u'name': u'Ian Whalen', u'email': u'ian@mongodb.com'}Message: |
| Comment by Eric Milkie [ 09/May/13 ] |
|
It's still scheduled to be included in the next release (2.6). The coding part is easy; we just need to spend a bit of time on the investigation. |
| Comment by Kenny Gorman [ 08/May/13 ] |
|
+1 will a pull request help things along? |
| Comment by Pykler [ 24/Mar/13 ] |
|
I am running mongodb in OpenVZ (via ProxMox 2.1, 2.2, and 2.3) for over 6 months and have not seen issues. The latest mongo command line shell shows the server init warnings including this one which is frightening and disheartining everytime it loads. Is there still known issues with OpenVZ and MongoDB? I have not seen the memory related errors previously mentioned in issue |