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: | ||
<translate> | <translate> | ||
<!--T:1--> | <!--T: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 | + | 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. |
<!--T:2--> | <!--T:2--> | ||
Line 7: | Line 7: | ||
== You should always report == <!--T:3--> | == You should always report == <!--T:3--> | ||
− | * | + | * 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]] | ||
− | * | + | * console tools information |
** <code>vzctl --version</code> | ** <code>vzctl --version</code> | ||
* OpenVZ/Virtuozzo environment information | * OpenVZ/Virtuozzo environment information | ||
Line 25: | Line 26: | ||
** Virtuozzo allows to gather all useful logs into single report. Execute <code>prlsrvctl problem-report --send</code> and <code>prlctl problem-report [CTUID|VMUID] --send</code> and specify problem report ID number in bug. | ** Virtuozzo allows to gather all useful logs into single report. Execute <code>prlsrvctl problem-report --send</code> and <code>prlctl problem-report [CTUID|VMUID] --send</code> and specify problem report ID number in bug. | ||
** 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 == <!--T:4--> | == A program fails to run == <!--T:4--> | ||
Line 49: | Line 50: | ||
== Access to the node == <!--T:8--> | == Access to the node == <!--T:8--> | ||
− | 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]]. |
<!--T:9--> | <!--T:9--> | ||
− | In case you can provide access, post login information via forum PM or e-mail, or ask for a public SSH key. | + | In case you can provide an access, post login information via forum PM or by e-mail, or ask for a public SSH key. |
<!--T:10--> | <!--T:10--> | ||
− | {{Warning|Do not post any sensitive information (like login details | + | {{Warning|Do not post any sensitive information (like login details to public forums, mailing lists etc.)}} |
== External resources == <!--T:11--> | == External resources == <!--T:11--> |