<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>Hi,</p>
<p>As you are in CentOs 7 maybe try to got through :</p>
<p><code># journalctl |grep -E
"Lustre|LustreErrors|LNet|LDISKFS|ustre"</code></p>
and see if you got what you need<br>
<br>
regards,<br>
J.<br>
<br>
<div class="moz-cite-prefix">On 08/13/2018 02:00 PM, Thomas Roth
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4728fd75-221a-b427-edc7-65c66a7aebbe@gsi.de">
<pre wrap="">Hi all,
we have this rather rare phenomenon of too few Lustre log entries - it would seem.
This is a cluster running Lustre 2.10.4 on CentOS 7.4
I do not think I have done anything to deviate from the defaults - neither with Lustre nor
rsyslogd-Config.
However,
# dmesg | grep LustreError | wc -l
50
# grep -r LustreError * | wc -l
0
Before I saw the LustreErrors on the console, I just assumed that newer Lustre versions are not that
chatty and this shiny new cluster just didn't show many errors.
"Lustre:" messages make it to /var/log/messages, as in "kernel: Lustre: haven't heard from client...",
obviously I have not cut off Lustre completely.
What did I do wrong?
Many regards,
Thomas
</pre>
</blockquote>
<br>
</body>
</html>