Murray,
While they both do involve a failure of the configuration process for the slapd
package during an upgrade, I think the original bug report and your problem
have separate root causes.
In particular, the problem discussed in the original bug report relates
to problems caused by invalid re
** Attachment added: "Murray's slapd.conf (no passwords)"
http://launchpadlibrarian.net/39441242/slapd.conf
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Can I join this problem?
I've upgraded from Edgy to Karmic - this is a development machine so I'm
not too worried failure, however everything seemed to work okay which
was pretty amazing as I came through a number of EOL supported releases.
Anyways, the point of doing this upgrade was to test my
** Changed in: openldap (Ubuntu)
Status: Incomplete => Confirmed
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
slave install:
apt-get install slapd
/etc/init.d/slapd stop
pushd /etc/ldap/
rm -rf schema/ slap.d/*
rsync -avP server:/etc/ldap/{schema,slave-slapd.conf} .
slaptest -f slave-slapd.conf -F slapd.d
chown -R openldap:openldap slapd.d
/etc/init.d/slapd start
Now,
Hello,
Sorry for not responding quickly!
I no longer use the directory server with OpenLDAP or slapd or ldap.
If later, I take this program, I will come to you to report any problems.
In case it is absolutely necessary to test this program for its operation, asks
me;
I take the time needed for tes
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification becau
How did you create the initial configuration?
If there are nodomain entries, it means that the domainame of the system
wasn't setup correclty when slapd was *first* installed.
How did you add the dc=company,dc=com sub-tree? Is it a different
database definition?
Could you attach the content of /
What information is it that you want?
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
** Changed in: openldap (Ubuntu)
Importance: Undecided => Low
--
[apport] package slapd failed to install/upgrade:
https://bugs.
I've also hit this on upgrade. It seems like the situation might be slightly
complex.
My ldap config does not use the slapd.conf method, but cn=config.
/etc/ldap/ldap.conf contains:
BASE dc=company, dc=com
URL ldap://localhost/
Running dpkg --configure gives:
sudo dpkg --configure
Removing the two stray dc=nodomain entries from the .ldif, and rerunning
dpkg --configure slapd, everything now completes. I'll sacrifice another
machine to see if I can catch where the nodomain entries are coming from
in the first place.
--
[apport] package slapd failed to install/upgrade:
http
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it without more information.
Could you attach the content of the file /etc/ldap/slapd.conf (with
relevant private information such as passwords and rootdn obfuscated)?
** Changed in: op
** Changed in: openldap (Ubuntu)
Sourcepackagename: openldap2.3 => openldap
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
While updating from Gutsy Gibbon 7.10 to Hardy Heron 8.04
I got a number of error messages saying that it could not update/install slapd.
Could not install /var/cache/apt/archives/slapd_2.4.7-6ubuntu3_i386.deb
The upgrade will continue but the
'/var/cache/apt/archives/slapd_2.4.7-6ubuntu
Preparation of replacing slapd 2.3.35-1ubuntu0.2 (using
.../slapd_2.4.7-6ubuntu3_i386.deb) ...
Stopping OpenLDAP: slapd.
Dumping to / var/backups/slapd-2.3.35-1ubuntu0.2:
-- Directory dc = example, dc = com ... bdb_db_open: only one allowed suffix
backend_startup_one: bi_db_open failed! (-1)
Hello,
I justed tested upgrading from Dapper to Hardy once with slapd installed
but not configured, and once with the LDAP db populated and the system
configured to use it for authentication. Both upgrades worked without
issue.
I didn't test from Feisty to Gutsy, just FYI :-).
--
[apport] pack
** Changed in: openldap2.3 (Ubuntu)
Sourcepackagename: update-manager => openldap2.3
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
As the upgrade to the new slapd version went through, I can no longer
log in when ldap is enabled in nsswitch.conf, but this would be a
problem with libnss-ldap. Concerning this bug here, the postinst script
should somehow remove the invalid entries from the ldap database before
reinsertion, or (I
Hi! I have the same problem here while trying to release-upgrade to
hardy from dapper (see also Bug #218311). I just found out what the
problem is:
There were two entries in my LDAP database related to a dc=nodomain. I
do not know where they came from. These entries keep slapadd from re-
inserting
Complete set of logs supplied, setting status to confimed.
** Changed in: update-manager (Ubuntu)
Status: Needs Info => Confirmed
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubu
thanks Francisco
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
I have attached all files in the directory /var/log/dist-upgrade
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
** Attachment added: "term.log"
http://librarian.launchpad.net/7577812/term.log
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
** Attachment added: "main.log"
http://librarian.launchpad.net/7577811/main.log
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
** Attachment added: "apt.log"
http://librarian.launchpad.net/7577810/apt.log
--
[apport] package slapd failed to install/upgrade:
https://bugs.launchpad.net/bugs/112631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
Francisco,
thanks for taking the time to report this. To help track down the source
of the problem it will help if you can attach the logs from your
upgrade. These can be found in /var/log/dist-upgrade.
thanks,
Richard
** Changed in: update-manager (Ubuntu)
Sourcepackagename: openldap2.3 => upda
27 matches
Mail list logo
