Freenas 9.10 - misconfigurations, bugs or just too verbose?

[freenas-supero]

After a complete rebuild from 9.2.1.6 to 9.10 (with import of database and pool), I noticed the following messages in the console and in the security report:

1. IPMI

Code:

KLD file ipmi.ko is missing dependencies

Server runs a Supermicro X9SCL-F and has IPMI support. I would like to keep the Supermicro IPMI and Freenas separate from each others. I am not sure what the Network > IPMI setup does in Freenas exactly? Manual says :
"Beginning with version 9.2.1, FreeNAS® provides a graphical screen for configuring an IPMI interface."

Does it mean that I could access some kind of Freenas based IPMI interface at the IP indicated under the settings? If so, how can I deactivate this completely??

2. AES Encryption

Code:

aesni0: No AESNI support.

CPU is a Xeon E3-1220V2 and AFAIK has encryption support (AES). Why am I seeing this message?

3. NFS woes
I currently run 4 NFS shares for misc LAN clients. All seems to work well, except the following problems:

-after a reboot of Freenas, I see the following output in the console and I have to manually bump the NFS service for the shares to work again otherwise clients will get a "Mount permission denied" issued by Freenas:

Code:

Jul 3 20:17:59 freenas mountd[1807]: mount request denied from 192.168.0.200 for /mnt/zpool/storage/data
Jul 3 20:17:59 freenas mountd[1807]: mount request denied from 192.168.0.200 for /mnt/zpool/storage/backup
Jul 3 20:19:59 freenas mountd[1807]: mount request denied from 192.168.0.200 for /mnt/zpool/storage/data
Jul 3 20:19:59 freenas mountd[1807]: mount request denied from 192.168.0.200 for /mnt/zpool/storage/backup
Jul 3 20:19:59 freenas mountd[1807]: mount request denied from 192.168.0.200 for /mnt/zpool/media
Jul 3 20:20:07 freenas notifier: Stopping lockd.
Jul 3 20:20:07 freenas notifier: Waiting for PIDS: 1820.
Jul 3 20:20:07 freenas notifier: Stopping statd.
Jul 3 20:20:07 freenas notifier: Waiting for PIDS: 1817.
Jul 3 20:20:07 freenas notifier: Stopping nfsd.
Jul 3 20:20:07 freenas notifier: Waiting for PIDS: 1813.
Jul 3 20:20:07 freenas notifier: Stopping mountd.
Jul 3 20:20:07 freenas notifier: Waiting for PIDS: 1807.
Jul 3 20:20:07 freenas notifier: nfsuserd not running?
Jul 3 20:20:07 freenas notifier: gssd not running? (check /var/run/gssd.pid).
Jul 3 20:20:07 freenas notifier: Stopping rpcbind.
Jul 3 20:20:07 freenas notifier: Waiting for PIDS: 1538.
Jul 3 20:20:11 freenas notifier: mountd not running? (check /var/run/mountd.pid).
Jul 3 20:20:11 freenas notifier: Starting rpcbind.
Jul 3 20:20:11 freenas notifier: Starting mountd.

Then followed by this:

Code:

Jul 3 20:20:12 freenas notifier: NFSv4 is disabled
Jul 3 20:20:12 freenas notifier: Starting nfsd.
Jul 3 20:20:12 freenas notifier: Starting statd.
Jul 3 20:20:12 freenas notifier: Starting lockd.
Jul 3 20:20:12 freenas nfsd: can't register svc name

4. mDNSResponder?
Finally, the following is recurring in the console:

Code:

Jul  3 20:28:30 freenas notifier: Stopping mdnsd.
Jul  3 20:28:30 freenas mDNSResponder: mDNSResponder (Engineering Build) (Jun  7 2016 20:26:10) stopping
Jul  3 20:28:30 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000801483580 01   25 _ssh._tcp.local. PTR freenas._ssh._tcp.local.
Jul  3 20:28:30 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080147B580 01   30 _sftp-ssh._tcp.local. PTR freenas._sftp-ssh._tcp.local.
Jul  3 20:28:30 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080147D580 01   26 _http._tcp.local. PTR freenas._http._tcp.local.
Jul  3 20:28:30 freenas notifier: Waiting for PIDS: 3029.
Jul  3 20:28:30 freenas notifier: Starting mdnsd.
Jul  3 20:28:30 freenas mDNSResponder: mDNSResponder (Engineering Build) (Jun  7 2016 20:26:10) starting
Jul  3 20:28:30 freenas mDNSResponder:  10: Listening for incoming Unix Domain Socket client requests
Jul  3 20:28:30 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Jul  3 20:28:30 freenas mDNSResponder: CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for PCP & NAT-PMP announcements
Jul  3 20:28:31 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 freenas.local. (Addr) that's already in the list
Jul  3 20:28:31 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 8.0.168.192.in-addr.arpa. (PTR) that's already in the list

I hope someone can help either solve or deactivate these messages if they are mostly harmless..

Thanks

 

[joeschmuck]

Item #1
Just ignore it. IPMI will work like it use to.

Item #2
Yes, the CPU does support it. I suspect it's a message you can ignore, I've seen it many times and it seems irrelevant.

Item #4, I believe you can ignore those as well. I have these on my system all the time without ill effect but if you have a DNS, maybe checking to see if that all works is in order.

Item #3 is the only one which concerns me. I don't know that answer.

Question: Did you really upgrade directly from 9.2.1 to 9.10? That is a huge leap. Also do not upgrade your pool unless you really do not want to go back to any previous version of FreeNAS.

I would recommend you start with a clean install of FreeNAS 9.10 Stable and before importing your pool, ensure the messages all have a valid meaning. I'm curious that if you import your configuration file, it could be causing an issue. You might need to upgrade to 9.3 first and see how that goes.

You may need to list all the hardware you have and exactly which version of FreeNAS 9.10 you are using.

 

[Ericloewe]

2. AES Encryption
CPU is a Xeon E3-1220V2 and AFAIK has encryption support (AES). Why am I seeing this message?

I'd file a bug report to have a dev look at that. If it's noise, at least we'll have confirmation.

1. IPMI

Same as above.

Server runs a Supermicro X9SCL-F and has IPMI support. I would like to keep the Supermicro IPMI and Freenas separate from each others. I am not sure what the Network > IPMI setup does in Freenas exactly? Manual says :
"Beginning with version 9.2.1, FreeNAS® provides a graphical screen for configuring an IPMI interface."

Does it mean that I could access some kind of Freenas based IPMI interface at the IP indicated under the settings? If so, how can I deactivate this completely??

No. Not at all. It means you can use the host FreeNAS OS to set basic IPMI settings so you can restore access to it if you do something silly like change the subnet mask to 255.255.255.255 or set it to the wrong VLAN.

 

[freenas-supero]

Opened bug report for IPMI issue:
https://bugs.freenas.org/issues/16251

Opened bug report for AESNI encryption issue:
https://bugs.freenas.org/issues/16252

Opened bug report for mDNS issue:
https://bugs.freenas.org/issues/16253

 

[freenas-supero]

Follow up for others with similar issues, and a quick question regarding security reports.

IPMI issue:
This was caused by leftover tunable to load the IPMI module on the former 9.2 release. Removing the tunable and rebooting fixed this. Check with kldstat and if you see ipmi.ko then its already loaded.

AESNI encryption issue:
A BIOS restore was done by another user and by default AESNI is disabled in this BIOS. Enabling the setting of course allowed AESNI to work.

dmesg | grep AES should yield something like:

Code:

Features2=0x7fbae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT
,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
aesni0: <AES-CBC,AES-XTS> on motherboard

mDNS issue:
service is just too verbose.....

Now, I regularly get emails called "weekly run output" with the following content:

Code:

 [text/plain] Text (1 KB)
Security check:
    (output mailed separately)

-- End of weekly output --

But I never get the "output" mailed separately... Why?

 

[MrToddsFriends]

Now, I regularly get emails called "weekly run output" with the following content:
[...]
But I never get the "output" mailed separately... Why?

There's already a feature request dealing with this issue.
https://forums.freenas.org/index.ph...rid-of-the-weekly-security-output-spam.45704/