dmidecode alert

[TomasNZ78]

Hi there

Any one knows why I get this message on repeat:

Code:

alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name

Please help

 

[wblock]

Please identify the exact version of FreeNAS being used.

 

[BigDave]

Hi there

Any one knows why I get this message on repeat:

Code:

alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name

Please help

It's probably related to this bug...
https://bugs.freenas.org/issues/21915
I have these messages as well.
I'm running 9.10.2-U3

 

[TomasNZ78]

I'm running the same version as BigDave

 

[TomasNZ78]

I had a look at the bug and my mb is Asus Z87 not ASRock. I didn't have this error on U2 only after I've upgraded to U3

 

[BigDave]

I had a look at the bug and my mb is Asus Z87 not ASRock. I didn't have this error on U2 only after I've upgraded to U3

I don't think it's motherboard related as I run a X9-SCM-F and have these log messages as well. I can't wait for the devs to fix this, it drives me nuts.
Here's a small sample from my log this morning.

Code:

May 18 21:18:04 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 18 21:18:05 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 18 22:18:21 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 18 22:18:21 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 18 23:18:37 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 18 23:18:37 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 00:00:00 freenas syslog-ng[1645]: Configuration reload request received,  reloading configuration;
May 19 00:18:54 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 00:18:54 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 01:19:10 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 01:19:10 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 02:19:26 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 02:19:26 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 03:19:45 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 03:19:45 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 04:20:01 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 04:20:01 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 05:20:17 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 05:20:17 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 06:20:34 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 06:20:34 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 07:20:52 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 07:20:52 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
May 19 08:21:09 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s system-product-name
May 19 08:21:09 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sb  in/dmidecode -s baseboard-product-name
[root@freenas] ~#

 

[TomasNZ78]

yeah it is pretty annoying!

 

[Redcoat]

Fixed in 11 at least for my two systems. I had them with the 9.10 versions ...

 

[BigDave]

Fixed in 11 at least for my two systems. I had them with the 9.10 versions ...

Really! You are a brave soul @Redcoat.
There is no way in hell I'd trust my data to a Release Client or a Nightlie version.
I have a test platform on RC2 but that's for testing only.

 

[Redcoat]

Ah, actually not that brave. I installed in my main system after having in my backup only to "check it out", then reverted to 9.10.2-U3 again. The install on my backup cleared most of the annoying log messages and I wanted to see the effect on the FreeNAS Mini as the messages were not the same.

 

[TomasNZ78]

installed ver 11 and no more of this annoying message

 

[IceBoosteR]

I also get this message every hour, and this make my disk spin up every time.
This needs to be fixed asap.
(9.10.2-U3)

 

[nojohnny101]

I'm getting these messages as well on FreeNAS-9.10.2-U2 (e1497f2)

 

[Jailer]

Target version for the fix is 11 so it's not going away until then. I'm rolling back to 9.10.2-U1 until 11 is ready and tested by the masses.

 

[IceBoosteR]

Target version for the fix is 11 so it's not going away until then. I'm rolling back to 9.10.2-U1 until 11 is ready and tested by the masses.

Wow, rollback because of the message?
I will also wait some month or even half a year for stable 11, as a first user of 10 I have learned to wait ;)

I would like to see this to be fixed asap in current 9.10.2-U3 or 9.10.2-U4.

I have opened another bug for this, this messages annoy me.

 

[Jailer]

It's slated to be fixed in 11 release which is due out soon. No need to file a new bug report on it since it will likely be closed as a duplicate.

 

[IceBoosteR]

It's slated to be fixed in 11 release which is due out soon. No need to file a new bug report on it since it will likely be closed as a duplicate.

No its done.
We will see and mybe this is generating more focus on fixing this.
Where can I find the post when FN11 will be released? Thought this would take some month....

 

[Jailer]

It's not fixed in the release product which is 9.10.2. It is fixed in 11 which is in RC status. You can follow the roadmap progress along at bugs.freenas.org of you want to keep up on things but as always watch the forums, web page and blog for release announcements.