Hi Arjan, On Tue, Apr 05, 2005 at 11:37:08PM +0200, Arjan Oosting wrote: > > Erm, it should use /var/backups/slapd-2.1.30-3 under the assumption that > > you were upgrading from the last version in sid. Is it in fact using > > slapd-VERSION as the directory name unchanged? > > No it did use /var/backups/slapd-2.1.30-3, so that went alright :)
Okay *phew*
> > Hmm. I wonder how that can happen. The merge_logical_lines shell
> > function is used to merge any lines which start with a space to the
> > preceding line. Can you try to reproduce this and give me the relevant
> > section of the config file?
>
> How can i reproduce this? Can I call some program the convert my
> slapd.conf the way the maintainer script does? I will attach my
> slapd.conf file
I am using the simple trick of sourcing my script library. Still working
on getting a better debugging interface. Anyway, using
$ source debian/slapd.scripts-common
$ merge_logical_lines < your_slapd.conf
I can see that it indeed messes up the configuration. The reason is
quite simple: You wrote the file in DOS mode and the maintainer script
does not cope with that. I assumed that merging lines can be done by
removing combinations of line feed followed by a line which is prefixed
with white space. That's almost what slapd does - well, almost :)
I'll go and fix the script to understand ^M in slapd.conf.
> Well you can say it isn't true but it still tried to write something in
> or create the /var/backups/slapd-2.1.30-3 directory. I don't know
Hrm. I can't see how that can happen. When I get arround to implement
putting only the used functions into the maintainer scripts the code
should even get excluded from the postinst which should proof that it
isn't called. But maybe I am wrong, which would mean that I am entirely
stupid.
Anyway, what I'd expect is that it tries to move /var/lib/ldap to
/var/backups/dc=arriesoft,dc=nl.ldabdb which will fail. Can you by
chance reproduce this failure and send me the output?
> whether it tried to dump the database again but i couldn't complete the
> installation without moving the /var/backups/slapd-2.1.30-3 directory
> out of the way. And after the installation was complete I did a manual
> slapadd.
Maybe it was trying to slapadd data from there as intended.
> > Is this the exact indentation? This works just fine here...
> This is supposed to work (and works), but the maintainer script changes
> it to one single line.
Which is also okay apart from merging the comment into it.
> > I don't think the breakage in your Samba installation is related. Samba
> > is using the libldap2 libraries which should still be from 2.1.x on any
> > Debian system. So nothing has changed on that front. Not sure if that is
> > a good thing... :(
>
> I think it is. The breakage occured right after upgrading slapd and in
> the trace I get from smbd i seel some calls to SSL related functions. So
> it seems the change from gnutls to openssl triggers a bug in Samba (see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=303272 ).
Looks interesting. Maybe it is in fact related but in the way that
OpenSSL and GnuTLS do not really like each other.
Your slapd.conf has
TLSCipherSuite HIGH
I am not sure if the TLS patch will use this setting in any way. Maybe
the algorithm used by samba does not suffice for this setting and now
OpenLDAP is rejecting the connection, triggering a bug in libldap2
or GnuTLS, more likely the first :(
Debugging output from slapd about that connection could be helpful.
Greetings
Torsten
signature.asc
Description: Digital signature
