Quanah Gibson-Mount wrote:
--On Wednesday, February 04, 2004 8:35 AM -0500 "Tibbetts, Ric" <ric.tibbetts@ngc.com> wrote:
What verion(s) did you upgrade from/to?
(On the server)
From OpenLDAP 2.1.22
To OpenLDAP 2.1.25 w/ Berkeley DB 4.2.52
I hope you got the patch for BDB 4.2.52
It should have been a relatively routine upgrade. It's important to note that my AIX, and Linux clients are still able to authenticate without problem. It's only the Solaris clients that this affected.
Hm, that is odd. Did you patch any of your solaris systems recently?
I've done several things. But nothing that would effect this. And I've tried several systems.
When I did the upgrade, because I was changing the database, I exported the whole thing first with "slapcat". Then after installing the new s/w, I ran slapadd to put it all back. It seems to have dropped something.
I've never had slapadd "drop" anything... It just loads what is in the LDIF output. Did you run slapadd with the '-c' option? If you did, and it had output, that would indicate you had errors in your LDIF as compared to your schema, which it would then skip past.
The logs haven't been much help.
Setting the loglevel to 128, shows the interaction with the ACLs, and I'm
not seeing where anything is being denied.
Below is an example run:
That log output isn't particularly useful. If possible, I suggest having an isolated machine you can query with a Solaris system, and run slapd with the '-d -1' flag, and dump that output to a file as a connection is made. It will give you all relevant information.
ldap_read: want=8 error=Resource temporarily unavailable conn=0 op=1 UNBIND ber_get_next on fd 12 failed errno=11 (Resource temporarily unavailable)
Any thoughts?
Thanks!!1
-Ric