Errors during boot up, can these be ignored

[SunnyG]

Hello Experts,

I have noticed that since adding my Freenas to my Active Directory, the following error is posted during boot:

Code:

Starting rpcbind.
ERROR: {'desc': 'Connect error', 'errno': 2, 'info': 'No such file or directory'}
Traceback (most recent call last):
  File "/usr/local/libexec/nas/generate_krb5_conf.py", line 549, in <module>
	main()
  File "/usr/local/libexec/nas/generate_krb5_conf.py", line 480, in main
	timeout=fs().directoryservice.kerberos.timeout.start))
  File "/usr/local/lib/python3.6/site-packages/middlewared/client/client.py", line 434, in call
	raise ClientException(c.error, c.errno, c.trace, c.extra)
middlewared.client.client.ClientException: {'desc': 'Connect error', 'errno': 2, 'info': 'No such file or directory'}
Starting watchdogd.

can this be safely ignored or am i missing something in my configuration?

 

[dlavigne]

You shouldn't be getting a traceback. What is the FreeNAS build version from System -> Information?

 

[SunnyG]

You shouldn't be getting a traceback. What is the FreeNAS build version from System -> Information?

here is the system info:

 

[dlavigne]

Assuming you're not using Kerberos, that should be a benign error (though a proper error message would be bettter than a traceback). If you decide to report it at bugs.freenas.org, post the issue number here.

 

[SunnyG]

Assuming you're not using Kerberos, that should be a benign error (though a proper error message would be bettter than a traceback). If you decide to report it at bugs.freenas.org, post the issue number here.

I have reported it under Bug #46069