The issue for @oxyde was not actually an issue. His NVMe drives were in low power mode and thus his NVMe drives were very slowly counting the Power On Hours. I don’t know why some drives do this and some don’t, it just happens. Think of it as extending your warranty
The script is working still, whew!
Yeah, thanks a lot for your time!
In the user guide, I see a version note that says “Added Email Report ONLY on Alert (any Error Message).” But I can’t find how to do that in the user guide, nor in the config interface.
I would like to get the email only if it’s not “all good”.
Yea, the manual could be written clearer. But it was clear in my mind
This should do it for you, sort of. It will not report a Warning level event.
In the Cron Job, add the switch -m
to the command. For example (this is my command for the Cron Job: cd /mnt/farm/scripts && ./multi_report.sh -m
to get an email only during a Critical error.
While this is typically set by default, you should open the multi_report_config.txt file and edit the following lines, if they even need to be changed:
###### Alert Email Configuration - For Temperature and Critical Error monitoring when you suspect a problem.
### You must use the '-m' switch
AlertEmail="YourAlertEmail@Address.com" # Alert email address used with the '-m' switch.
AlertOnWarningTemp="true" # Send alert on Warning Temp. Default = "true"
AlertOnCriticalError="true" # Send alert on Critical Error. Default = "true"
I would recommend testing this as well by setting the drive temp critical warning value to below the current drive value. This should send you an email when you run the script. If it does, then change the value back and you should be good.
Thanks Joe. Sounds like I better not do that, as I want to be made aware of anything that is not “all good”, for example too many days without a SMART test. I guess I’ll leave it as is and check the daily email subject before deleting it.
You could make a quick edit to the script to trigger on anything. Pretty easy, Ha Ha. Look in your email today and I will send you a line to change in the script.
Okay Joe. I added the -m
to the CronJob command, verified that in the config file AlertOnWarningTemp
and AlertOnCriticalError
are both "true"
, and made that little secret change to the script. Thank you!
I ran the cron job and didn’t get an email, so it seems to be working. I’ll run that test later just to be sure.
I have grown to like the All Good emails I get from each server every morning. I know immediately even before coffee, if anything is wrong in the server room if one or both emails don’t show up. Give the emails a quick look see and off to other things.