Editing Reporting OpenVZ problem
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | + | To support OpenVZ users we maintain [http://forum.openvz.org/index.php?t=thread&frm_id=2 Support forum] and [http://openvz.org/mailman/listinfo/users Users mailing list]. If you analyze an activity at the forum, then you'll find out that the substantial portion of all the messages are requests to users to provide an additional information about their environments. Because of this, the time between the report of a problem and its solution is sometimes much longer than it could be. | |
− | |||
− | To support OpenVZ users we maintain [http://forum.openvz.org/index.php?t=thread&frm_id=2 Support forum] and [http://openvz.org/mailman/listinfo/users Users mailing list | ||
− | |||
This article described which information a user should report when reporting OpenVZ-related problem. We hope that it will make our support service more effective. | This article described which information a user should report when reporting OpenVZ-related problem. We hope that it will make our support service more effective. | ||
− | == You should always report == | + | == You should always report == |
− | * | + | * clear problem description |
− | + | It is necessary not just to describe the problem, but also post real commands, | |
+ | and real output on console. It is useful to run commands with <code>--verbose</code> option. | ||
* Kernel information | * Kernel information | ||
− | ** | + | ** kernel version, architecture and flavour (<code>uname -a</code>) |
− | ** | + | ** origin of your binary kernel (RPM from openvz.org, other repository, compiled from sources, ...) |
** .config file (if you compiled the kernel) | ** .config file (if you compiled the kernel) | ||
* Linux distribution used on [[HN]] | * Linux distribution used on [[HN]] | ||
− | * | + | * vzctl information |
** <code>vzctl --version</code> | ** <code>vzctl --version</code> | ||
− | * OpenVZ | + | * OpenVZ environment information |
− | |||
** <code>/etc/vz/vz.conf</code> file | ** <code>/etc/vz/vz.conf</code> file | ||
** <code>/etc/vz/<veid>.conf</code> file, where <code><veid></code> is an id of container in question. | ** <code>/etc/vz/<veid>.conf</code> file, where <code><veid></code> is an id of container in question. | ||
Line 23: | Line 20: | ||
** <code>/var/log/messages</code> | ** <code>/var/log/messages</code> | ||
** <code>/var/log/vzctl.log</code> | ** <code>/var/log/vzctl.log</code> | ||
− | |||
** Other | ** Other | ||
− | + | If other programs are involved in your problem, try to run they with increased verbosity and attach appropriate log files, if they exist. | |
− | == A program fails to run == | + | == A program fails to run == |
The most helpful tool here is <code>strace</code>. See [[stracing a program]]. | The most helpful tool here is <code>strace</code>. See [[stracing a program]]. | ||
− | == Network related problem == | + | == Network related problem == |
* interface/routing/filter configuration | * interface/routing/filter configuration | ||
You should run these commands in [[container]] '''and''' on [[HN]] | You should run these commands in [[container]] '''and''' on [[HN]] | ||
Line 42: | Line 38: | ||
* see also required information in [http://forum.openvz.org/index.php?t=tree&goto=27545&S=37542b6163cbf0da10ebc21fdd10b471#msg_27545 post on forum] | * see also required information in [http://forum.openvz.org/index.php?t=tree&goto=27545&S=37542b6163cbf0da10ebc21fdd10b471#msg_27545 post on forum] | ||
− | |||
{{Note|if you have public IP addresses, you should carefully mask them in a report. For example: 194.85.83.97 -> X.Y.83.97.}} | {{Note|if you have public IP addresses, you should carefully mask them in a report. For example: 194.85.83.97 -> X.Y.83.97.}} | ||
− | == Kernel Oops == | + | |
+ | == Kernel Oops == | ||
"[[When you have an oops]]" article explains how to identify Oops and what you should do when it happens. The key moment is that you should send us the '''full''' Ooops text. Sometimes it can be easily obtained from <code>/var/log/messages</code> file or <code>dmesg</code> output. In other cases, you can only see an Oops message on the monitor, and the system is completely stuck. In such a situation you should implement [[Remote console setup]]. As a rule, each production server should have a remote console set up. | "[[When you have an oops]]" article explains how to identify Oops and what you should do when it happens. The key moment is that you should send us the '''full''' Ooops text. Sometimes it can be easily obtained from <code>/var/log/messages</code> file or <code>dmesg</code> output. In other cases, you can only see an Oops message on the monitor, and the system is completely stuck. In such a situation you should implement [[Remote console setup]]. As a rule, each production server should have a remote console set up. | ||
− | == Access to the node == | + | == Access to the node == |
− | In some cases, a remote access to the problem node is the fastest way to diagnose and fix a problem, so sometimes an OpenVZ developer can request such access from you. Note that in should be root access | + | In some cases, a remote access to the problem node is the fastest way to diagnose and fix a problem, so sometimes an OpenVZ developer can request such access from you. Note that in should be a root access (either directly, or via <code>sudo</code>) to the [[hardware node]]. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | In case you can provide an access, post login information via forum PM or by e-mail, or ask for a public SSH key. | |
− | + | {{Warning|Do not post any login details to public forums, mailing lists etc.}} | |
− | |||
− | |||
[[Category: QA]] | [[Category: QA]] |