SOLVED Why am I getting FreeNAS telemetry alerts when it tries to read baseboard info....

[mysticpete]

Keep getting these telemetary errors while freenas is trying to read the baseboard info, how do i turn it off?

Code:

Mar 14 03:38:15 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 03:38:15 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 04:38:25 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 04:38:25 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 04:45:49 freenas kernel: pid 56373 (Plex Media Scanner), uid 972: exited on signal 11
Mar 14 05:38:53 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 05:38:53 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 06:38:59 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 06:38:59 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 07:39:04 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 07:39:04 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 08:39:09 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 08:39:09 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 09:05:09 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot -r "media@auto-20170314.0900-2y"
Mar 14 09:39:14 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 09:39:14 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 10:39:20 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 10:39:20 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 11:39:24 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 11:39:25 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 12:24:38 freenas ugen4.2: <vendor 0x8087> at usbus4 (disconnected)
Mar 14 12:24:39 freenas ugen4.2: <vendor 0x8087> at usbus4
Mar 14 12:39:30 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 12:39:30 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 13:39:35 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 13:39:35 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 14:39:40 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 14:39:40 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 15:39:45 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 15:39:45 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 16:39:50 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 16:39:50 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 17:15:27 freenas kernel: arp: 192.168.1.4 moved from 02:ff:a0:00:04:0a to 70:85:c2:04:88:83 on epair0b
Mar 14 17:39:55 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 17:39:55 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 14 18:40:01 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 14 18:40:01 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name

Thanks in advance for any suggestions.

 

[m0nkey_]

https://bugs.freenas.org/issues/21915

 

[mysticpete]

https://bugs.freenas.org/issues/21915

So when is it released?

 

[mysticpete]

So when is it released?

Bump

 

[Jaesii]

My FreeNAS box is getting flooded with the same messages.

 

[AliAhmadi]

I am getting the same exact issue in my logs (repeating after every AFP access through time machine)

Mar 26 18:10:05 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 26 18:10:05 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 26 19:10:22 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 26 19:10:22 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 26 20:10:39 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 26 20:10:39 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 26 21:10:56 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 26 21:10:56 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 26 22:11:12 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 26 22:11:12 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar 26 23:11:28 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar 26 23:11:28 ALIAfreenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name

 

[fireheadman]

I also am getting these messages.
Per the bug report, I am not running a ASRock MB, I have an ASUS Sabertooth FX990

How is this issue/thread marked SOLVED when the link to the BUG report is still OPEN?
Is the intention to release a fix on the next update release? I do not subscribe to nightlies for stability reasons.

From BUG Report
#7

Updated by William Grzybowski 29 days ago
Erik Thorsell wrote:
William Grzybowski wrote:
It showing in the logs is just an overly verbose call.

The alert were designed to do periodically checks, 60 minutes was the chosen value.
It is not a big deal, the logs have already been removed in nightlies and I'll increase the time check.
Is there a way to turn this off? As for now my otherwise quite clean and informative log gets clogged with these outputs.
No.

 

[mysticpete]

@fireheadman The answer is in the paste you did of the bug report.... pretty much acting as designed

 

[maxx]

To fix this, do:

Code:

[root@FreeNAS] cd  /usr/local/www/freenasUI/system/alertmods
[root@FreeNAS] vi freenas_bmc.py

Change:

Code:

interval = 60

to

interval = 1440  # Or whatever you want.

Save. Reboot. Done.

 

[JFD]

To fix this, do:

Code:

[root@FreeNAS] cd  /usr/local/www/freenasUI/system/alertmods
[root@FreeNAS] vi freenas_bmc.py

Change:

Code:

interval = 60

to

interval = 1440  # Or whatever you want.

Save. Reboot. Done.

I have the same issue on my Freenas system. But I need some help on the "save" action. After entering both codes I find the interval text and change it to 1440. But (1) this only means it is done less but with the same result? And (2) how do I save the change?