SOLVED Many error messages in log after re-provisioning ad

[TomS]

Hi there,

because of some other error messages I decided to disable and then re-enable my ad service on FreeNAS.

Since having done so, I keep getting many, many messages logged like:

freenas kernel: limiting icmp unreach response from 912 to 200 packets/s.

After some debugging, I found that there are many DNS queries which are not answered, as there seems no local DNS server running. I think I remember that there was a DNS server running before (well, all the ad stuff is based in DNS, right?)

There is another suspicious entry in the logs which I don't unterstand and which comes before those icmp lig entries:

Nov 16 00:11:41 freenas notifier: provision_smb4()
Nov 16 00:11:41 freenas notifier: File "/usr/local/libexec/nas/generate_smb4_conf.py", line 1165, in provision_smb4
Nov 16 00:11:41 freenas notifier: if not Samba4().sentinel_file_create():
Nov 16 00:11:41 freenas notifier: TypeError: sentinel_file_create() takes exactly 2 arguments (1 given)
Nov 16 00:11:42 freenas notifier: Performing sanity check on Samba configuration: OK
Nov 16 00:11:42 freenas notifier: Starting samba.
Nov 16 00:11:42 freenas samba[52766]: [2015/11/16 00:11:42.079022, 0] ../source4/smbd/server.c:370(binary_smbd_main)
Nov 16 00:11:42 freenas samba[52766]: samba version 4.1.18 started.
Nov 16 00:11:42 freenas samba[52766]: Copyright Andrew Tridgel

Any clues on that?
I performed an FreeNAS update to the latest version some time ago. Might this issues be related?

Best regards,
TomS

 

[dlavigne]

Good, I see you opened a bug.

 

[TomS]

Well, I'm not sure whether or not it's a bug, so I was reluctant to do so, but then I thought that it also might help others if the devs have a look at that...

 

[TomS]

The bug was confirmed and fixed.