Reporting OpenVZ problem - Revision history

95.93.143.227 at 11:51, 11 May 2018

2018-05-11T11:51:24Z

Kir: fix closing bracket

2016-08-08T22:08:27Z

fix closing bracket

Kir: fix English

2016-08-08T22:06:11Z

fix English

Kir: proper indentation and capitalization

2016-08-08T22:03:24Z

proper indentation and capitalization

Sergey Bronnikov: Marked this version for translation

2015-12-26T08:36:43Z

Marked this version for translation

Sergey Bronnikov: add 'translate' tags

2015-12-25T22:38:24Z

add 'translate' tags

Sergey Bronnikov: mention Vz problem report

2015-09-02T08:45:51Z

mention Vz problem report

Sergey Bronnikov: add link to bugtracker

2015-09-01T17:15:54Z

add link to bugtracker

Sergey Bronnikov: small corrections

2015-09-01T17:07:30Z

small corrections

Kir: added to Category:QA

2015-03-11T22:21:34Z

added to Category:QA

@@ Line 1: / Line 1: @@
 <translate>
 <!--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]. 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]. For reporting bugs use [https://bugs.openvz.org/ OpenVZ bugtracker]. 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-->

@@ Line 55: / Line 55: @@
 <!--T:10-->
-{{Warning|Do not post any sensitive information (like login details to public forums, mailing lists etc.)}}
+{{Warning|Do not post any sensitive information (like login details) to public forums, mailing lists etc.}}
 == External resources == <!--T:11-->

@@ Line 49: / Line 49: @@
 == 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 a root access (either directly, or via <code>sudo</code>) to the [[hardware 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 to the [[hardware node]] — either directly, or via <code>su</code> or <code>sudo</code>.
 <!--T:9-->
-In case you can provide an access, post login information via forum PM or by e-mail, or ask for a public SSH key.
+In case you can provide access, post login information via forum PM or e-mail, or ask for a public SSH key.
 <!--T:10-->

@@ Line 7: / Line 7: @@
 == You should always report == <!--T:3-->
-* clear problem description
+* Clear problem description
-It is necessary not just to describe the problem, but also post real commands,
+: It is necessary not just to describe the problem, but also post real commands you entered and their real output. It is useful to run commands with <code>--verbose</code> option.
 * Kernel information
-** kernel version, architecture and flavour (<code>uname -a</code>)
+** Kernel version, architecture and flavour (<code>uname -a</code>)
-** origin of your binary kernel (RPM from openvz.org, other repository, compiled from sources, ...)
+** Origin of your binary kernel (RPM from openvz.org, other repository, compiled from sources, ...)
 ** .config file (if you compiled the kernel)
 * Linux distribution used on [[HN]]
-* console tools information
+* Console tools information
 ** <code>vzctl --version</code>
 * OpenVZ/Virtuozzo environment information
@@ Line 26: / Line 25: @@
 ** 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
-If other programs are involved in your problem, try to run they with increased verbosity and attach appropriate log files, if they exist.
+:: 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-->

@@ Line 1: / Line 1: @@
 <translate>
 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.
 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 == <!--T:3-->
 * clear problem description
 It is necessary not just to describe the problem, but also post real commands,
@@ Line 26: / Line 28: @@
 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 == <!--T:4-->
 The most helpful tool here is <code>strace</code>. See [[stracing a program]].
-== Network related problem ==
+== Network related problem == <!--T:5-->
 * interface/routing/filter configuration
 You should run these commands in [[container]] '''and''' on [[HN]]
@@ Line 41: / Line 43: @@
 * 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.}}
-== Kernel Oops ==
+== Kernel Oops == <!--T:7-->
 "[[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 == <!--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 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 sensitive information (like login details to public forums, mailing lists etc.)}}
-== External resources ==
+== External resources == <!--T:11-->
 * [https://bugs.openvz.org/ OpenVZ bugtracker]
 </translate>
 [[Category: QA]]

@@ Line 21: / Line 21: @@
 ** <code>/var/log/messages</code>
 ** <code>/var/log/vzctl.log</code>
 ** Other
 If other programs are involved in your problem, try to run they with increased verbosity and attach appropriate log files, if they exist.

← Older revision		Revision as of 17:15, 1 September 2015
Line 50:		Line 50:

	{{Warning\|Do not post any sensitive information (like login details to public forums, mailing lists etc.)}}		{{Warning\|Do not post any sensitive information (like login details to public forums, mailing lists etc.)}}
		+
		+	== External resources ==
		+
		+	* [https://bugs.openvz.org/ OpenVZ bugtracker]

	[[Category: QA]]		[[Category: QA]]

← Older revision		Revision as of 22:21, 11 March 2015
Line 50:		Line 50:

	{{Warning\|Do not post any login details to public forums, mailing lists etc.}}		{{Warning\|Do not post any login details to public forums, mailing lists etc.}}
		+
		+	[[Category: QA]]