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>
22 lines
3.9 KiB
HTML
22 lines
3.9 KiB
HTML
<a name="obs_11_0056"></a><a name="obs_11_0056"></a>
|
|
|
|
<h1 class="topictitle1">Log Files</h1>
|
|
<div id="body1554982511704"><div class="section" id="obs_11_0056__section16839141103914"><h4 class="sectiontitle">Configuring Log Files</h4><p id="obs_11_0056__p397816524335">obsutil log files include tool logs and SDK logs. You can add the following parameters to the <strong id="obs_11_0056__b115605406291">.obsutilconfig</strong> file to enable the two logging functions.</p>
|
|
<ul id="obs_11_0056__ul14556173743515"><li id="obs_11_0056__li2491184323513">Tool logging (records the log information generated during obsutil running): configure <strong id="obs_11_0056__b16217153415416">utilLogPath</strong>, <strong id="obs_11_0056__b1245614373413">utilLogBackups</strong>, <strong id="obs_11_0056__b188021839134113">utilLogLevel</strong>, and <strong id="obs_11_0056__b12127164384113">utilMaxLogSize</strong>.</li><li id="obs_11_0056__li125561337183512">SDK logging (records the log information generated when using obsutil to call OBS server-side APIs): configure <strong id="obs_11_0056__b1954221917458">sdkLogPath</strong>, <strong id="obs_11_0056__b41896231459">sdkLogBackups</strong>, <strong id="obs_11_0056__b96611225144514">sdkLogLevel</strong>, and <strong id="obs_11_0056__b137359296454">sdkMaxLogSize</strong>.</li></ul>
|
|
<div class="note" id="obs_11_0056__note17325532123810"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="obs_11_0056__ul8955173817384"><li id="obs_11_0056__li159555387386">For details about the parameter description, see <a href="obs_11_0035.html">Configuration Parameters</a>.</li><li id="obs_11_0056__li51329419386"><strong id="obs_11_0056__b159459347465">utilLogPath</strong> and <strong id="obs_11_0056__b737743824615">sdkLogPath</strong> indicate the absolute paths of the log files, not the folders that store the log files.</li><li id="obs_11_0056__li17480175811388">If <strong id="obs_11_0056__b344512415501">utilLogPath</strong> and <strong id="obs_11_0056__b176111073508">sdkLogPath</strong> are not specified, tool logging and SDK logging are not enabled, and therefore no log file is generated during obsutil running.</li><li id="obs_11_0056__li154111537418">Log files that are rolled over are named as follows: <em id="obs_11_0056__i1683965510577">filename</em><strong id="obs_11_0056__b161071017589">.log.</strong><em id="obs_11_0056__i18118123115820">number</em></li></ul>
|
|
</div></div>
|
|
</div>
|
|
<div class="notice" id="obs_11_0056__note20947435113611"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="obs_11_0056__p294773511368">If multiple obsutil processes are running at the same time, log files may fail to be written concurrently or may be lost. In this case, add parameter <strong id="obs_11_0056__b14802153215329">-config</strong> when running commands to configure an independent configuration file for each process. Make sure that <strong id="obs_11_0056__b8292348114417">utilLogPath</strong> and <strong id="obs_11_0056__b97016520444">sdkLogPath</strong> are set to different paths for each process.</p>
|
|
</div></div>
|
|
<div class="section" id="obs_11_0056__section53132393016"><h4 class="sectiontitle">Collecting Log Files</h4><p id="obs_11_0056__p19313103123019">You can collect logs in either of the following methods:</p>
|
|
<p id="obs_11_0056__p34471133164012">Method 1: Use auxiliary commands by referring to <a href="obs_11_0045.html">Archiving Log Files</a>.</p>
|
|
<p id="obs_11_0056__p37441159174010">Method 2: Locate the paths specified by <strong id="obs_11_0056__b0398455111219">utilLogPath</strong> and <strong id="obs_11_0056__b103897291316">sdkLogPath</strong> in the configuration file, and then search for the log files in the corresponding paths in the local file system.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="obs_11_0054.html">Fault Locating</a></div>
|
|
</div>
|
|
</div>
|
|
|