Just started using Rockstore and so far going really well. Apologies if this has been asked before, but I tried searching for “email” and got no results.
I have successfully setup an email address and tested it, but I can’t find any information about what emails are sent? Is this documented anywhere? I looked at the documentation but I can only find the following:
“Rockstor includes an easy to use Postfix configuration facility to enable Email Notifications on system events and drive health status.”
My main question is does Rockstore send an email if a HDD in the storage pool fail (it looks like it should), but also can I customise these notifications at all?
Currently we simply forward all root emails. So anything sent to root on the system, all normal system events, will also be forwarded to the configured recipient email.
Only if it fails a scheduled S.M.A.R.T test. Which can be configured via the advanced ‘free form’ text box. We have plans to add a more sophisticated notification system but currently we simply forward root emails.
The following issue has some information about using logcheck to get more btrfs info emailed:
Thanks to @maxhq for sharing his particular solution there.
DEVICESCAN -a -o on -S on -n standby,q -s (S/…/…/./02|L/…/…/6/03) -W 4,35,40 -m “my@email”
If you email to root@localhost the result should be forwarded appropriately.
In short it’s a super unfriendly system to define the ‘interval’ and type and conditions of the tests and that is part of why we have yet to implement a nice Web-UI element for this. It’s definitely planned but we have had our hand full with other more pressing matters for a while now. So as the tool tip on S.M.A.R.T button on the Disks overview page indicated:
You can find all that you need in the manual page for smartd.conf
man smartd.conf
And make sure to take a look at that file also as it has a tone of notes/comment in there to guide your configuration. Once you have what you are after you can pop it into that Web-UI box and it will be auto-added to the “smartd.conf” file, examples of the locations are as follows:
OS
smartd version
smartd.conf location
CentOS
smartd 6.5 2016-05-07 r4318
/etc/smartmontools/smartd.conf
Leap 15.1
smartd 6.6 2017-11-05 r4594
/etc/smartd.conf
Leap 15.2
smartd 7.0 2018-12-30 r4917
/etc/smartd.conf
Though the versions may be out in that table as it was adapted from the following, now closed, issue:
So if you are using our CentOS based variant it’s in /etc/smartmontools/smartd.conf.
We could do with better docs on this really. But that time might also be spend on implementing an intergrated UI element as there is already the manual. Often these planned improvements come down to what we spend our limited resources on. But it would be great to have this this element of drive health testing/reporting far more refined than just entering raw config. So if anyone fancies taking on this task then do please consider adopting one of our related issues or making your own and announcing your intentions to work on this. I’re really like this myself as having to look up specific smartd.conf lines each time is not really workable.
@mlewis-everley Once you have your config ‘worked out’ do please consider sharing your findings as if nothing else it could help towards seeing what configs folks gravitate towards so that we might simplify this whole thing and have a few clicks to cover the vast majority of use cases.
Hope that helps, and do let us know who you get on.
