@Trexx If you wouldn’t mind running the multi_report.sh script with -dump emailextra so I can see what is going on. Please also note that I am not at home so I can’t do much right now. How did version 3.07 work? If you have not run it, please make sure it works.
Hi Joe,
V3.07 works fine without the error. Debug Dump running currently and should be in your mailbox soon. No worries about how quickly you get it resolved, just wanted to give you a heads-up about the issues. Enjoy the time with the grandkids. 
Thanks, that helps a lot. I will reach out to you soon.
Version 3.0.7 stopped working here after upgrading TrueNAS SCALE to version 24.10.1, released yesterday.
I have two other boxes, one with Core 13.0-U6.4 and one with SCALE 24.04.2.5 and they both managed to send their daily reports today.
I am using SendGrid as a relay, and have confirmed that the missing mails were not relayed to the service.
I can assist with debugging, if you tell me how to proceed.
P.S.: both the scheduled report and a manually started one via Shell do not submit their e-mails. There are no error messages when starting ./multi_report.sh manually. Also, the boxes were on 24.10.0.2 before, and the reports were being sent flawlessly.
TrueNAS 24.10.1 broke the “sendmail” function of the script. It is not just you. I found out late last night of this wonderful development. I hope to have it sorted out within the next 24 hours (less is better).
I’m not saying that sendmail is broken, I just have not identified the issue yet, but TrueNAS 24.10.1 has a few symlinks for sendmail. It is just another way to drive me crazy.
4 Likes
FWIW, I have a few homemade rclone backup scripts that send mail reports on completion, and I just got those, even for the boxes running SCALE 24.10.1.
They have the mail utility location hard-coded at /usr/bin/mail - this is probably too inflexible for your script, but I thought it was worth mentioning.
I actually was planning to look into using mail vice sendmail but I need to see what changes I would need to make to the script. sendmail should still work, I just don’t understand why it doesn’t. If it turns out to be a TrueNAS build issue, then I’d like to have them fix it.
More to follow. Just spent $40K USD, my bank account hurts!
Looks like a completely different format. However in the long run it might be better. More research first. And maybe I can figure out why sendmail suddenly stopped.
3 Likes
Doing a test email send from Scale 24.10.1 located at: System > General settings > Mail works. Using SMTP (with all the settings that go along with that) if this helps any in troubleshooting.
Upgraded to ElectricEel-24.10.1 and multi_report stopped working. Not getting the daily reports as usual. I tried reinstalling latest version with no luck. Getting the following email with errors.
Multi-Report v3.1 dtd:2024-12-10 (TrueNAS Scale 24.10.1)
Checking for Updates
Current Version 3.1 – GitHub Version 3.0.7
No Update Required
Message from Joe
Running Drive Self-test Script: /mnt/Storage/scripts/drive_selftest.sh
Joe’s SMART Drive Self-test Script - Run: 21 December 03:53:19 AM
Script Version: 1.0 (10 December 2024), TrueNAS Scale 24.10.1
Logging Enabled
Using External Configuration File
Short Test Mode:(2) “Short SMART Test All Drives”, Running Week Option, No Sorting
Long Test Mode:(1) “Long SMART Test on 1 Drive(s) Per Day”, Running Week Option, Sorting by: Serial
Sorting Drive Test Order …
Authorized Test Days: Mon, Tue, Wed, Thu, Fri, Sat, Sun
Total Drives Recognized: 6
Drive(s) previously scheduled to be tested: sde, nvme0, sdc, sda, sdb
Drive(s) scheduled for testing today: sdd
Drive(s): “sdd” were removed from the Short testing list
It/They are already scheduled for the Long test, no need to duplicate efforts
RUNNING SHORT TEST: sda sdb sdc sde nvme0
Drive: sda in Short Test
Drive: sdb in Short Test
Drive: sdc in Short Test
Drive: sde failed to start Short Test
SHIT!!! - “sde” did not accept the smartctl command.
Here is the return message:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.44-production+truenas] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org Short offline self test failed [unsupported field in scsi command]
Drive: nvme0 in Short Test
RUNNING LONG TEST:
Drive: sdd failed to start Long Test
CRAP!!! - “sdd” did not accept the smartctl command.
Here is the return message:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.44-production+truenas] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org Long (extended) offline self test failed [device not ready]
ALL TESTS COMPLETED OR RUNNING IN BACKGROUND
03:53:30.99: Main Program End, Wrapping things up…
Elapsed Time: Program 0 minutes and 11.69 seconds elapsed.
Your 130 Second Delay, Please Standby…
Saving Log (file name: /mnt/Storage/scripts/DS_Logs/drive_test_21.txt)
Exiting Joe’s SMART Drive Self-test Script
Collecting Report Data…
jq: error: syntax error, unexpected ‘[’, expecting FORMAT or QQSTRING_START (Unix shell quoting issues?) at , line 1:
.nvme_smart_health_information_log.temperature_sensors.[0] | values
jq: 1 compile error
jq: error: syntax error, unexpected ‘[’, expecting FORMAT or QQSTRING_START (Unix shell quoting issues?) at , line 1:
.nvme_smart_health_information_log.temperature_sensors.[1] | values
jq: 1 compile error
Yeah, sendmail has been removed from Truenas, and the alternative seems to be a bit tricky to get to work.
Multi-Report fails to send Email in TrueNAS 24.10.1
I am working the issue however it does not appear to be an easy one to solve, either due to my ignorance or I possibly will need to rewrite the email section of the script. It is not a simple fix. And this is due to a security change in TrueNAS.
If you do not need to use 24.10.1, then I recommend you rollback or remain on 24.10.0.2 until I fix this, or just not run Multi-Report.
There is also an issue with the new drive selftest script, it appears some scsi drives refuse the testing commands. I’m working this issue as well. I don’t know if this problem persists in 24.10.0.2 as well, I hope someone tells me soon, but I would expect it to be there as well.
With all that said, you may be better off remaining on version 3.07 for now. I would appreciate any help troubleshooting if you try version 3.1 and have a failure on 24.10.0.2 or earlier.
Sorry about the issues, the email thing was out of my control. I will push updates to github for the two scripts but officially being released is on hold until these two issues are sorted out.
Thanks for understanding.
4 Likes
On my 24.04 system /etc/exim4/update-exim4.conf.conf has a line that goes:
dc_eximconfig_configtype='local'
Which according to the manpage is “local delivery only; not on a network”.
Compare that to a setting like “internet” for “internet site; mail is sent and received directly using SMTP”.
Is it the same in 24.10.1?
Does the official GUI test mail use some form of relaying that your attempts aren’t (yet) using?
Yes, it is the same.
I changed it o internet an ran update-exim4.conf and then tried to send an email via the shell.
That connected alright to a mail server, but something else seems to be wrong, maybe the way I created the test mail…
It’s good to know that it progresses further in the chain if that setting is changed, but I am not sure it’s an ideal thing to have to alter. Especially since the “Send Test Mail”-button somehow manages to do it even when it’s set to local.
That what full file looks like, apart from the change from local to internet, which I am not sure if it is a good idea.
I guess it will be the same, assuming iX is using exim before the update.
This is 24.04.2.5:
dc_eximconfig_configtype='local'
dc_other_hostnames='tnsbuilds01.tn.ixsystems.net'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname=''
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
So yeah, the same.
Well, even sending a simple email via exim failed, so far. " root@ " always apears a the sender of the email, and that not being a valid email/domain, does not work. The connection to the mailprovider work seem to work, they just do not get the necessary infos to send something.
Does that happen even if you set a sender address with the -f flag?
No, that does not work either. Maybe there is some more configuration needed in other places…