SOLVED alert.py dmidecode - bug reported

[Silvan Burch]

Hey guys

Since the update from FreeNAS 9.10.2-U1 to -U2, the following messages started to appear on the log:

Code:

Mar  8 15:15:23 fenix4k alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar  8 15:15:23 fenix4k alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar  8 16:15:28 fenix4k alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar  8 16:15:28 fenix4k alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name
Mar  8 17:15:33 fenix4k alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name
Mar  8 17:15:33 fenix4k alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name

so it seems they appear every hour. as far as i could figure out, dmidecode reads out hardware information right? I do not know if there's an 'alert' reading out or what?

if someone could tell me what this is supposed to mean, if it is a problem at all or what I should do about it, I would be really grateful.

Thanks for the support and best regards

 

[JohnDigital]

Its happening for me as well. As far as I can tell, its nothing to worry about. Ive used dmidecode often to display what motherboard and such is in a machine without cracking the case open. Im sure this is how FN gets its hardware info, probably just a bit chatty, but certainly a change from U1.

 

[burritodamus]

I'm getting the same thing as well...I'm not sure, but maybe this has something to do with trying to discern whether We are running ASRock Motherboards:

• An alert is shown when running on certain models of ASrock Rack motherboards with flawed BMC firmware that require an update. See ASrock Rack BMC Issue.

 

[dlavigne]

Looks like it has been reported: https://bugs.freenas.org/issues/21915.

 

[Silvan Burch]

thanks for the quick replies. as it is nothing important and the bug has been reported, I marked the problem as solved!

best regards