forked from docs/doc-exports
weihongmin1
a41a4e0331
Reviewed-by: Sabelnikov, Dmitriy <dmitriy.sabelnikov@t-systems.com> Co-authored-by: weihongmin1 <weihongmin1@huawei.com> Co-committed-by: weihongmin1 <weihongmin1@huawei.com>
14 lines
1.5 KiB
HTML
14 lines
1.5 KiB
HTML
<a name="obs_11_0078"></a><a name="obs_11_0078"></a>
|
|
|
|
<h1 class="topictitle1">How Can I Find Out Why Some Tasks in a Batch Task Failed?</h1>
|
|
<div id="body0000001201000435"><p id="obs_11_0078__p16265126183914">After a batch task is completed, there will be results telling you how many tasks succeeded or failed. To find out why those tasks failed, you can check their failure result file or obsutil log file.</p>
|
|
<p id="obs_11_0078__p1570616214244">After a batch task is executed, its task ID will be generated. You can query the failure result file in the <strong id="obs_11_0078__b17281826506">.obsutil_output</strong> directory based on the task ID. The file is named in the <strong id="obs_11_0078__b764515511804">cp_{failed}_report_</strong><em id="obs_11_0078__i1333295711017">Time</em><strong id="obs_11_0078__b4941121417113">_</strong><em id="obs_11_0078__i74376182110">TaskId</em><strong id="obs_11_0078__b2055692415115">.txt</strong> format and contains detailed error information about each failed task.</p>
|
|
<p id="obs_11_0078__p8060118">In addition, you can view the obsutil log file to query the error records during obsutil running. You are advised to set the log level to <strong id="obs_11_0078__b103571215329">DEBUG</strong> for fault locating. For details about the log configuration and log path, see <a href="obs_11_0056.html">Log Files</a>.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="obs_11_0074.html">FAQs</a></div>
|
|
</div>
|
|
</div>
|
|
|