Add new comment

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Submitted by kir (registered user) on Mon, 2007-01-01 19:34.

Let me warn you that your configuration is wrong. You should always check the changes you made to a VE configuration using the vzcfgvalidate tool. In your case, it gives (at least) the following:

Error: othersockbuf.lim-othersockbuf.bar should be > 652800 (currently, 0)
Warning: tcprcvbuf.lim-tcprcvbuf.bar should be > 204800 (currently, 0)

The problem  is quite severe: since you set the barrier and the limit for othersockbuf to the same value, there is no "safety gap" between bar and lim, thus the system will act severe if there will be othersockbuf shortage. Same problem with tcprcvbuf.

For more info about these specific parameters, see http://wiki.openvz.org/UBC_secondary_parameters

For info of how to configure your UBC (and other resource management) settings, see http://wiki.openvz.org/Resource_shortage 

Overall UBC info is at http://wiki.openvz.org/UBC. 

Finally, it makes no sense to publish a config with IP_ADDRESS and NAMESERVER variables.

Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.

Reply

*
*
The content of this field is kept private and will not be shown publicly.


*

  • Images can be added to this post.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <div>
  • Lines and paragraphs break automatically.