"NFS services could not bind specific IPs, using wildcard" after 9.10.1 udpate?

Status
Not open for further replies.

norbs

Explorer
Joined
Mar 26, 2013
Messages
91
Beside the LSI driver p21 mismatch (which was already discussed in another thread), I got this new NFS alert right after the update.
NFS services could not bind specific IPs, using wildcard

My NFS service is not enabled and no NFS shares are configured.

Any ideas?

Code:
nas# dmesg | grep NFS
nas#


Screen Shot 2016-08-06 at 11.38.50 AM.png
Screen Shot 2016-08-06 at 11.39.08 AM.png
Screen Shot 2016-08-06 at 11.39.25 AM.png
 
D

dlavigne

Guest
That's interesting. Was NFS ever enabled on that system? eg I wonder if it's picking up something from an earlier config.
 

norbs

Explorer
Joined
Mar 26, 2013
Messages
91
That's interesting. Was NFS ever enabled on that system? eg I wonder if it's picking up something from an earlier config.
Yeah, there is a pretty good chance I had NFS on at one point.
 
D

dlavigne

Guest
Looks like something missing in the migration tool (or when cleaning up the db). Please create a bug report at bugs.freenas.org that contains your debug (made from System -> Advanced -> Save Debug) so that a dev can track down the culprit and fix the alert. Post the issue number here.
 
Status
Not open for further replies.
Top