FreeNAS

Can you reproduce? If so, I'd like to know what traceback you are getting. Can you please either take a screen shot or cut & paste the traceback into the ticket? Cut & paste is preferable since I can see the entire traceback.

Hi John,

Yes, I can reproduce this. I get it both starting & stopping the AD service. I'm also getting the yellow alert warning me that "tried 10 attempts to recover service activedirectory".

Attached is the traceback & request details.

-Will

survive - wrote:

Hi John,

I updated to 11-RELEASE & while I can't seem to reproduce the traceback error anymore I was greeted by the blinking yellow warning light with the "WARNING: June 14, 2017, 3:45 p.m. - tried 10 attempts to recover service activedirectory" when I logged on.

I disabled the AD service to test, re-enabled it and got a second line "WARNING: June 14, 2017, 3:45 p.m. - tried 10 attempts to recover service activedirectory" message when I clicked on the warning light again.

So I cleared the warnings & checked the stoplight again & got 2 lines of "WARNING: June 14, 2017, 3:45 p.m. - tried 10 attempts to recover service activedirectory", clear those, refresh & when the clock ticked over I got 2 lines of "WARNING: June 14, 2017, 3:50 p.m. - tried 10 attempts to recover service activedirectory"

Is my AD service really trying to restart itself over ten times a minute?

-Will

The code that prints this out should probably not print this out unless it actually can't recover the service (assuming it needs recovering!). It just means it ran for a certain amount of times and then stopped, which is correct. The warning should probably go away ;-) I'll keep this bug open to indicate that.

John - Still going to try and nuke this warning for -U3 or is this a 11.1 task?

Kris Moore wrote:

John - Still going to try and nuke this warning for -U3 or is this a 11.1 task?

Original isssue was fixed. Second issue is fixed in master but I'm hesitant to merge to U3 since it includes all the new async stuff. If I retarget for 11.1, it seems pointless since 11.1 will include the fix ;-) I can of course backport, but is it worth it? It's an annoyance for sure, but isn't breaking anything.

John: in that case should this ticket be closed or set to resolved?

Dru Lavigne wrote:

John: in that case should this ticket be closed or set to resolved?

I leave this to you guys ;-) The issue is fixed, but can't directly be merged to stable without duplicating work (essentially a rewrite of fixes). If it is important enough, I can do that, otherwise, it will be in 11.1.

Kris: what are your thoughts?

Lets have this go into 11.1 as originally planned.

Test passes