RE: [suse-autoinstall] LDAP error during autoyast
-----Original Message----- From: Nick Tzaperas [mailto:njt@thecatalis.com] Sent: Tuesday, November 15, 2005 4:44 PM To: Jiří Suchomel Cc: suse-autoinstall@suse.com; locilka@suse.cz Subject: Re: [suse-autoinstall] LDAP error during autoyast
Quick FYI, I tried commenting out the whole ldap section like I said in a previous e-mail and it didn't work either. Same dialog box and log entries. Is there anything else I can try?
If you're not using LDAP at all, you need to take out every reference to LDAP everywhere, throughout the control file, if you don't want that popup. Make sure that the <ldap> section is gone, along with pam_ldap and nss_ldap from the packages section. I'll agree, happily, that this shouldn't be the case, but my experience shows that it is. Not sure if it's been fixed in builds beyond the one included in Pro 9.3. On the other hand, if you _do_ have an LDAP server available and want it to work, then I think you may be short a couple of elements in the config section. Your LDAP section doesn't have nearly as many elements as mine, and I do remember getting errors if I didn't have _all_ of these defined -- or at least present. My config is for SuSE Pro 9.3, though, which may have some effect on your results. In any case, my ldap config section looks like this (and works just fine and dandy): <ldap> <base_config_dn>ou=ldapconfig,DC=sub,dc=domain,dc=com</base_config_dn> <bind_dn></bind_dn> <create_ldap config:type="boolean">false</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>DC=sub,dc=domain,dc=com</ldap_domain> <ldap_server>192.168.X.YYY, 192.168.X.yyy</ldap_server> <ldap_tls config:type="boolean">false</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <member_attribute>member</member_attribute> <nss_base_group></nss_base_group> <nss_base_passwd></nss_base_passwd> <nss_base_shadow></nss_base_shadow> <pam_password></pam_password> <start_autofs config:type="boolean">false</start_autofs> <start_ldap config:type="boolean">true</start_ldap> </ldap> Again, YMMV... - Ian
Marlier, Ian wrote:
-----Original Message----- From: Nick Tzaperas [mailto:njt@thecatalis.com] Sent: Tuesday, November 15, 2005 4:44 PM To: Jiří Suchomel Cc: suse-autoinstall@suse.com; locilka@suse.cz Subject: Re: [suse-autoinstall] LDAP error during autoyast
Quick FYI, I tried commenting out the whole ldap section like I said in a previous e-mail and it didn't work either. Same dialog box and log entries. Is there anything else I can try?
If you're not using LDAP at all, you need to take out every reference to LDAP everywhere, throughout the control file, if you don't want that popup. Make sure that the <ldap> section is gone, along with pam_ldap and nss_ldap from the packages section.
OK, I removed the <ldap> section from the top of the file and the only other ldap package was python-ldap. I removed that, yet these packages still get installed: ldapcpplib-0.0.3-21.3 openldap2-client-32bit-9-200411291942 openldap2-client-2.2.6-37.26 yast2-ldap-2.9.15-1.3 yast2-ldap-server-2.9.14-0.2 yast2-ldap-client-2.9.27-0.2 pam_ldap and nss_ldap do not get installed, though. Do I need to prevent any of these packages from getting installed too? Or is it just pam_ldap and nss_ldap that cause the popup? Thanks, Nick
On Tuesday 15 of November 2005 23:54, Nick Tzaperas wrote:
Marlier, Ian wrote:
-----Original Message----- From: Nick Tzaperas [mailto:njt@thecatalis.com] Sent: Tuesday, November 15, 2005 4:44 PM To: Jiří Suchomel Cc: suse-autoinstall@suse.com; locilka@suse.cz Subject: Re: [suse-autoinstall] LDAP error during autoyast
Quick FYI, I tried commenting out the whole ldap section like I said in a previous e-mail and it didn't work either. Same dialog box and log entries. Is there anything else I can try?
If you're not using LDAP at all, you need to take out every reference to LDAP everywhere, throughout the control file, if you don't want that popup. Make sure that the <ldap> section is gone, along with pam_ldap and nss_ldap from the packages section.
OK, I removed the <ldap> section from the top of the file and the only other ldap package was python-ldap. I removed that, yet these packages still get installed:
I don't think you have to remove any packages from the list. Did it work after removing just <ldap> section? Jiri -- Jiri Suchomel SuSE CR, s.r.o. e-mail: jsuchome@suse.cz Drahobejlova 27 tel:+420-2-96542385 190 00 Praha 9, Czech Republic http://www.suse.cz
Jiří Suchomel wrote:
On Tuesday 15 of November 2005 23:54, Nick Tzaperas wrote:
Marlier, Ian wrote:
-----Original Message----- From: Nick Tzaperas [mailto:njt@thecatalis.com] Sent: Tuesday, November 15, 2005 4:44 PM To: Jiří Suchomel Cc: suse-autoinstall@suse.com; locilka@suse.cz Subject: Re: [suse-autoinstall] LDAP error during autoyast
Quick FYI, I tried commenting out the whole ldap section like I said in a previous e-mail and it didn't work either. Same dialog box and log entries. Is there anything else I can try?
If you're not using LDAP at all, you need to take out every reference to LDAP everywhere, throughout the control file, if you don't want that popup. Make sure that the <ldap> section is gone, along with pam_ldap and nss_ldap from the packages section.
OK, I removed the <ldap> section from the top of the file and the only other ldap package was python-ldap. I removed that, yet these packages still get installed:
I don't think you have to remove any packages from the list. Did it work after removing just <ldap> section?
Jiri
Nope, tried that. Exact same error message and popup. Nick
On 11/15/05 5:54 PM, "Nick Tzaperas" <njt@thecatalis.com> wrote:
Marlier, Ian wrote:
-----Original Message----- From: Nick Tzaperas [mailto:njt@thecatalis.com] Quick FYI, I tried commenting out the whole ldap section like I said in a previous e-mail and it didn't work either. Same dialog box and log entries. Is there anything else I can try?
If you're not using LDAP at all, you need to take out every reference to LDAP everywhere, throughout the control file, if you don't want that popup. Make sure that the <ldap> section is gone, along with pam_ldap and nss_ldap from the packages section.
OK, I removed the <ldap> section from the top of the file and the only other ldap package was python-ldap. I removed that, yet these packages still get installed:
ldapcpplib-0.0.3-21.3 openldap2-client-32bit-9-200411291942 openldap2-client-2.2.6-37.26 yast2-ldap-2.9.15-1.3 yast2-ldap-server-2.9.14-0.2 yast2-ldap-client-2.9.27-0.2
pam_ldap and nss_ldap do not get installed, though. Do I need to prevent any of these packages from getting installed too? Or is it just pam_ldap and nss_ldap that cause the popup?
Did it work? My experience was that with pam_ldap and nss_ldap in the package selection list, even without an <ldap> section, the popup occurred. I don't explicitly install any other ldap packages, but any others in the <minimal> selection group _are_ still installed, and that almost certainly includes the yast2 packages (and possibly the others as well). So, basically: my guess would be, without the <ldap> section, and given that none of the ???_ldap packages are being installed, you should be fine. As always, YMMV :-) - Ian
Ian Marlier wrote:
On 11/15/05 5:54 PM, "Nick Tzaperas" <njt@thecatalis.com> wrote:
Marlier, Ian wrote:
-----Original Message----- From: Nick Tzaperas [mailto:njt@thecatalis.com] Quick FYI, I tried commenting out the whole ldap section like I said in a previous e-mail and it didn't work either. Same dialog box and log entries. Is there anything else I can try?
If you're not using LDAP at all, you need to take out every reference to LDAP everywhere, throughout the control file, if you don't want that popup. Make sure that the <ldap> section is gone, along with pam_ldap and nss_ldap from the packages section.
OK, I removed the <ldap> section from the top of the file and the only other ldap package was python-ldap. I removed that, yet these packages still get installed:
ldapcpplib-0.0.3-21.3 openldap2-client-32bit-9-200411291942 openldap2-client-2.2.6-37.26 yast2-ldap-2.9.15-1.3 yast2-ldap-server-2.9.14-0.2 yast2-ldap-client-2.9.27-0.2
pam_ldap and nss_ldap do not get installed, though. Do I need to prevent any of these packages from getting installed too? Or is it just pam_ldap and nss_ldap that cause the popup?
Did it work?
My experience was that with pam_ldap and nss_ldap in the package selection list, even without an <ldap> section, the popup occurred. I don't explicitly install any other ldap packages, but any others in the <minimal> selection group _are_ still installed, and that almost certainly includes the yast2 packages (and possibly the others as well).
So, basically: my guess would be, without the <ldap> section, and given that none of the ???_ldap packages are being installed, you should be fine.
As always, YMMV :-)
- Ian
There were no *_ldap packages and I commented out the ldap section and still the same thing. Thanks anyway. Nick
participants (4)
-
Ian Marlier -
Jiří Suchomel -
Marlier, Ian
-
Nick Tzaperas