RC1 - "Edit Share..." window takes a long time to open

[survive]

Hi guys,

I'm having a problem editing both CIFS & NFS shares with 8.0.1 RC1.

When I click on the "edit" button for either share type with the "Active Directory" service enabled I get the "Edit..." window with the progress bar and a "Loading..." message that will stay there for a long time...over 5 minutes, long enough for me to think it was broken & type out this ticket. If I disable the "Active Directory" service the "Edit Share..." window pops up almost immediately.

The first time I tried to edit a share I got a traceback message, but I didn't capture it because I wanted to turn off the AD service & see if that influenced things as it has in other share related tickets.

Now I don't get the traceback message, the "Edit Share..." window just hangs there for a long time before popping open the proper edit window.

The one thing I do recall from the traceback error is that it was referencing line 827, but I do not recall which file...I do think it is related to looking up my users & groups for the premissions dropdown boxes.

-Will

-Will

[william]

How many users do you have within your AD?

[survive]

Hi William,

Not that many...maybe 20?

-Will

[jhixson]

Hi Will,

I've isolated your problem to DNS.

The LDAP code uses DNS to determine where the domain controllers and global catalog servers are for your Active Directory.

These are the domain controllers for your AD setup:

[root@filer ~]# host -t srv _ldap._tcp.masterrave.com
_ldap._tcp.masterrave.com has SRV record 0 100 389 vigilance.masterrave.com.
_ldap._tcp.masterrave.com has SRV record 0 100 389 dc3.masterrave.com.
_ldap._tcp.masterrave.com has SRV record 0 100 389 dc9.masterrave.com.

The first host returned here is vigilance.masterrave.com. If you try to reach it on port 389, you get the following:

[root@filer ~]# telnet vigilance.masterrave.com 389
Trying 10.34.34.40...
^C

The other 2 hosts are reachable. They all have the same weight and priority, so whatever is returned first will be tried first. You can fix this issue by changing the weight and/or priority of the SRV records or just removing the record for vigilance.masterrave.com. Otherwise, a connection is attempted and you have to wait for it to timeout, which is clearly taking a while.