Hi there, I have 389ds 1.3.4.0-26 running on OL7 and looks good related to RedHat and its clone clients.
But I am having issue to initialize Solaris 11. The 389ds came with 60nis.ldif and 60rfc4876.ldif and I have them imported successfully, I believe below searches show this.
# ldapsearch -h <ldapserver> -b "dc=domain,dc=com" -s sub "objectclass=duaconfigprofile" version: 1 dn: cn=solaris11,ou=Profile,dc=domain,dc=com serviceSearchDescriptor: passwd:l=AMER,dc=domain,dc=com?sub serviceSearchDescriptor: shadow:l=AMER,dc=domain,dc=com?sub serviceSearchDescriptor: group:ou=Groups,dc=domain,dc=com?sub defaultSearchScope: sub defaultSearchBase: dc=domain,dc=com defaultServerList: ldapserver.domain.com cn: solaris11 objectClass: top objectClass: duaconfigprofile
# ldapsearch -h ca-ldap01 -b "dc=domain,dc=com" -s sub "objectclass=nisdomainobject" version: 1 dn: nisdomain=us.domain.com,dc=domain,dc=com nisDomain: us.domain.com objectClass: top objectClass: nisdomainobject
And next step is failing.
# ldapclient -v init -a profileName=solaris11 10.x.x.x
Parsing profileName=solaris11 Arguments parsed: profileName: solaris11 defaultServerList: 10.x.x.x Handling init option About to configure machine by downloading a profile Can not find the solaris11 DUAProfile
Please let me know if someone has any feedback or any additional information is needed, thanks in advance.
Zarko Dudic wrote:
Hi there, I have 389ds 1.3.4.0-26 running on OL7 and looks good related to RedHat and its clone clients.
But I am having issue to initialize Solaris 11. The 389ds came with 60nis.ldif and 60rfc4876.ldif and I have them imported successfully, I believe below searches show this.
# ldapsearch -h <ldapserver> -b "dc=domain,dc=com" -s sub "objectclass=duaconfigprofile" version: 1 dn: cn=solaris11,ou=Profile,dc=domain,dc=com serviceSearchDescriptor: passwd:l=AMER,dc=domain,dc=com?sub serviceSearchDescriptor: shadow:l=AMER,dc=domain,dc=com?sub serviceSearchDescriptor: group:ou=Groups,dc=domain,dc=com?sub defaultSearchScope: sub defaultSearchBase: dc=domain,dc=com defaultServerList: ldapserver.domain.com cn: solaris11 objectClass: top objectClass: duaconfigprofile
# ldapsearch -h ca-ldap01 -b "dc=domain,dc=com" -s sub "objectclass=nisdomainobject" version: 1 dn: nisdomain=us.domain.com,dc=domain,dc=com nisDomain: us.domain.com objectClass: top objectClass: nisdomainobject
And next step is failing.
# ldapclient -v init -a profileName=solaris11 10.x.x.x
Parsing profileName=solaris11 Arguments parsed: profileName: solaris11 defaultServerList: 10.x.x.x Handling init option About to configure machine by downloading a profile Can not find the solaris11 DUAProfile
Please let me know if someone has any feedback or any additional information is needed, thanks in advance.
At a glance I don't see anything wrong with the profile. I'd look in the 389-ds access log to see what the query looks like and what is and what the error codes are, if any.
rob
I believe it breaks here ...
Line 1 : conn=211 op=2 SRCH base="dc=domain,dc=com" scope=2 filter="(&(objectClass=nisDomainObject)(nisDomain=us.domain.com))" attrs="distinguishedName" Line 2 : conn=211 op=2 RESULT err=0 tag=101 nentries=1 etime=0 Line 3 : conn=211 op=3 SRCH base="ou=profile,nisdomain=us.domain.com,dc=domain,dc=com" scope=2 filter="(&(|(objectClass=SolarisNamingProfile)(objectClass=DUAConfigProfile))(cn=solaris11))" attrs=ALL Line 4 : conn=211 op=3 RESULT err=32 tag=101 nentries=0 etime=0 Line 5 : conn=211 op=4 UNBIND
Is it expected to insert nisdomain after ou=profile, the line 3 ?
FYI, this has been resolved by adding ObjectClass"domain" to the "dc=xxxx,dc=xx"
# ldapsearch -h ca-ldap01 -b "dc=redhats,dc=rs" -s sub "objectclass=nisdomainobject" version: 1 dn: dc=redhats,dc=rs nisDomain: redhats.rs objectClass: top objectClass: domain objectClass: nisdomainobject dc: redhats
389-users@lists.fedoraproject.org