CIFS/AD Health Check Before Upgrade

[butwelld]

Hi Guys,

First post so please go easy on me :)

So I have a 9.2.1.7 install running CIFS with AD integration to a 2012 R2 domain (member server only). All of the shares and permissions work correctly and there are no issues.

I ran a GUI upgrade to 9.2.1.8 and the AD integration broke. After some searching I found this was a bug and rolled back to 9.2.1.7.

After the release of 9.2.1.9 I tried again, and again the AD integration broke. After another roll back I tried 9.3-BETA with the same result.

I would really like to get onto the new 9.3 code, but wondered if there is any way I can 'assure' the health of what I have before attempting the upgrade. Any pointers on what to look for or check?

More than happy to just run the upgrade and troubleshoot from there, I was just after a warm fuzzy feeling before starting.....

Cheers,

D

 

[dlavigne]

Safest bet would be to setup a test 9.3. system first...

 

[butwelld]

Sorry for the delay in the reply.

So I have just built a 9.2.1.7 and a 9.3 VM for testing. The 9.2.1.7 joins the AD straight away and behaves exactly like the real system.

On the 9.3 front it looks like it is unable to bind to the domain:

Dec 13 13:17:21 fresh93 winbindd[18131]: [2014/12/13 13:17:21.707863, 0] ../source3/winbindd/winbindd_util.c:634(init_domain_list)
Dec 13 13:17:21 fresh93 winbindd[18131]: Could not fetch our SID - did we join?
Dec 13 13:17:21 fresh93 winbindd[18131]: [2014/12/13 13:17:21.708322, 0] ../source3/winbindd/winbindd.c:1240(winbindd_register_handlers)
Dec 13 13:17:21 fresh93 winbindd[18131]: unable to initialize domain list

This looks like the same error I was getting when trying the upgrade.

Would really appreciate some help troubleshooting and resolving this please.

D

 

[dlavigne]

If you create a bug report at bugs.freenas.org, post the issue number here.

 

[butwelld]

Report opened as requested:

https://bugs.freenas.org/issues/7181