Your message dated Fri, 01 Jun 2007 16:36:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380621: slapd upgrade produces no backup file
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: slapd
Version: 2.3.24-2
Severity: important
the recent upgrade from 2.3.24-1 produced _no_ backup file
ls /var/backups/slapd-2.3.24-1/
slapd.conf
ls /var/backups/slapd-2.2.26-5/
dc=itp,dc=tuwien,dc=ac,dc=at.ldif slapd.conf
could you _please_ be a lot more carefull about your upgrade
handling.
it might be possible that the dir is regenerated and that
due to the previous upgrade failure it was removed:
Do you want to continue [Y/n]?
Setting up slapd (2.3.24-2) ...
Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.3.24-1... done.
Starting OpenLDAP: slapd - failed.
The operation failed but no output was produced. For hints on what went
wrong please refer to the system's logfiles (e.g. /var/log/syslog) or
try running the daemon in Debug mode like via "slapd -d 16383" (warning:
this will create copious output).
Below, you can find the command line options used by this script to
run slapd and slurpd. Do not forget to specify those options if you
want to look to debugging output:
slapd -g openldap -u openldap
invoke-rc.d: initscript slapd, action "start" failed.
dpkg: error processing slapd (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
slapd
E: Sub-process /usr/bin/dpkg returned an error code (1)
--
maks
--- End Message ---
--- Begin Message ---
As near as I can tell, this request is now present in the package as a
debconf question. The relevant question is "Dump databases to file on
upgrade" with responses "always", "when needed", and "never". If you
select "always", every upgrade of slapd should generate a dump.
Please do report a bug if this is not happening for you. It seems to be
for me.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--- End Message ---
