Re: Using SMARTd to monitor drives

Ray Andrews wrote:
> On 04/02/17 03:24 AM, Christian Franke wrote:
>> Ray Andrews wrote:
>>> On 31/01/17 01:21 AM, Christian Franke wrote:
>>>
>>>
>>> Your question suggests that you never checked the SYSLOG output of
>>> smartd. Please do this first before asking further questions here.
>>>
>>> On Debian, try:
>>>      grep -w smartd /var/log/daemon.log
>>> or for older logs:
>>>      zgrep -w smartd /var/log/daemon.log.*
>>>
> That is very useful thanks.  Honestly I thought you could only examine
> syslog under systemd using the official tools like 'journalctl' , they
> are always saying that it's binary now.  I had no idea you could just
> grep.

Fortunately, the traditional log files created by some variant of the 
syslog daemon (on Debian: rsyslogd) still exist even on systems that 
have moved to systemd.


>    The entire subject of access to logs is another thing that has
> become very difficult to understand. Until now, I've been using
> "journalctl -p err -b -1", and not seeing very much :(

Or course, as you restricted the messages to LOG_ERR or worse (-p err) 
and to previous boot (-b -1). Most of smartd's messages are invisible 
then because these use LOG_INFO level.

Note that systemd journals are often not persistent by default (at least 
on Debian). Using 'journalctl -b -1' always fails then.

Regards,
Christian


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot