Under 11.0-U4 a cron job script to report CPU and HDDtemps emailed me its output. Under 11.1 it doesn't. I have switched backwards and forwards between 11.0-U4 and 11.1 and tried the various combinations/permutations of Redirect Stdout and Redirect Stderr under 11.1 and no joy. Under 11.0-U4 with no boxes checked I get an email at the appointed cron job run time, under 11.1 nothing (11.1 test emails to root still work, BTW).
I'm back on 11.0-U4 until I sort this out, but I don't know what to do next...
In pursuit of an answer to the above issue, after checking everything I could think of, including letting the cron job run under 11.0-U4 at 12h00 EST and receiving the expected email output, booting into 11.1 and having the same cron job run at 12h30 EST and NOT getting the expected email output, I looked in the logs - nothing in var/log/messages, but here's what is in var/log/maillog (with correct email address edited out):
Code:
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Subject: Cron <root@freenasmini> PATH="/bin:/s
Dec 28 12:00:04 freenasmini /find_alias_for_smtplib.py[50071]: sending mail to -FCronDaemon,-odi,-oem,-oiFrom: Cron Daemon <root@freenasmini.local>
To: root
Subject: Cron <root@freenasmini> PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr
Dec 28 12:00:05 freenasmini /find_alias_for_smtplib.py[50071]: sending mail to xx@yy.comContent-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Subject: Cron <root@freenasmini> PATH="/bin:/s
Dec 28 12:30:08 freenasmini /find_alias_for_smtplib.py[12138]: sending mail to -FCronDaemon,-odi,-oem,-oiFrom: Cron Daemon <root@freenasmini.local>
To: root
Subject: Cron <root@freenasmini> PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr
Dec 28 17:30:09 freenasmini /middlewared[217]: sending mail to xx@yy.comContent-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Subject: Cron <root@freenasmini> PATH="/bin:/s
The 11.0-U4 lines timed at 12:00:04 and :05 were associated with an email being received, those 11.1 lines timed at 12:30:08 and 17:30:09 (?) did not.
Anyone have any ideas that can explain or resolve what's going on here? Is the above log info relevant to the issue, and/or are there other places to go?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.