Closed WaaromZoMoeilijk closed 4 years ago
Indeed @Spearfoot rocks!
I think I can answer your first one as I don't have an issue. By chance are you running FreeNAS as a VM in ESXi? I am and have use_ipmi=1
in the script and don't have an issue. When I change use_ipmi=0
I'm able to replicate your issue.
use_ipmi=1
=
=== CPU (2) ===
CPU 1: [46C]
CPU 2: [41C]
use_ipmi=0
=
=== CPU (8) ===
sysctl: unknown oid 'dev.cpu.0.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 0: C
sysctl: unknown oid 'dev.cpu.1.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 1: C
sysctl: unknown oid 'dev.cpu.2.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 2: C
sysctl: unknown oid 'dev.cpu.3.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 3: C
sysctl: unknown oid 'dev.cpu.4.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 4: C
sysctl: unknown oid 'dev.cpu.5.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 5: C
sysctl: unknown oid 'dev.cpu.6.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 6: C
sysctl: unknown oid 'dev.cpu.7.temperature'
get_hdd_temp.sh: line 72: [: : integer expression expected
CPU 7: C
If that is the issue you also have to add ipmi relevant data to the script, ipmihost, user, pwfile, path to ipmitool.
Hey man,
I don't have an IPMI capable Mobo. So enabling it isn't an option. I'd like to figure out a way to fix this.
Are you running FreeNAS as a VM or baremetal? I called out IPMI as with an ESXi install (myself), I believe the only way to easily retrieve cpu temp is via IPMI as ESXi doesn't pass it through.
But honestly, @Spearfoot is the man to ask, I was just attempting to lend a hand if I could. Clearly I = FAIL ... sorry about that.
Sorry forgot to mention I run it on a dedicated server no ESXi server present. We'll wait till he gets around. Thanks for the time though!
Sorry for taking so long to look at this... It seems that FreeNAS (FreeBSD) no longer reports the CPU temperatures via the sysctl command, which the script uses to obtain them. This may be because support for this sysctl OID is no longer supported with newer versions of FreeBSD.
I don't have a hardware-based FreeBSD/FreeNAS installation to debug with -- all of my installations run as ESXi virtual machines.
You might use the suggestions on the following website and see if you can get the appropriate cpu temperature module to load on your system:
https://www.cyberciti.biz/faq/freebsd-determine-processor-cpu-temperature-command/
Hey thanks for these scripts, i hope we can fix them for the most current release.
File is created actually the config_passphrase with perm 0600 Seems to hang at the last output line...
Seems to hang here too..
I do have a UPS! Before you ask :)
The last 3 don't seem to send the actual email, i receive nothing. FreeNAS notifications do work.