Hi,
On Wed, Jan 09, 2008 at 09:41:57AM +0200, Fabian Fagerholm wrote:
> Something seems to go wrong with the debconf stuff. Did you get any
> debconf prompts when upgrading the package?
Yes, about where to back up sasldb.
> I can't seem to figure out why it would hang, though. Could you send the
> output of "sasldblistusers2 | wc -l".
0
> > Shell: /bin/sh linked to /bin/dash
>
> This is of course worth noting. Could you try running the postinst
> script by hand (/var/lib/dpkg/info/sasl2-bin.postinst) as root and see
> what happens? Better yet, set DEBCONF_DEBUG to "developer" before
> running the postinst script. Back up your /etc/sasldb2 first; other than
> that, it should be completely safe.
# /var/lib/dpkg/info/sasl2-bin.postinst configure
debconf (developer): frontend started
debconf (developer): frontend running, package name is sasl2-bin
debconf (developer): starting /var/lib/dpkg/info/sasl2-bin.config
configure
debconf (developer): <-- RESET cyrus-sasl2/backup-sasldb2
debconf (developer): --> 0
debconf (developer): <-- INPUT medium cyrus-sasl2/backup-sasldb2
debconf (developer): --> 0 question will be asked
debconf (developer): <-- GO
Configuring sasl2-bin
---------------------
Cyrus SASL has stored usernames and passwords in the /etc/sasldb2 database file.
That file has to be upgraded to a newer database format. First, a backup of the
current file will be
created. You can use that if you need to manually downgrade Cyrus SASL.
However, automatic downgrades are
not supported.
Please specify the backup file name. You should check the available disk space
in that location. If the
backup file already exists, it will be overwritten. Leaving this field empty
will select the default value
(/var/backups/sasldb2.bak).
Backup file name for /etc/sasldb2: /var/backups/sasldb2.bak
debconf (developer): --> 0 ok
debconf (developer): <-- GET cyrus-sasl2/backup-sasldb2
debconf (developer): --> 0 /var/backups/sasldb2.bak
debconf (developer): starting /var/lib/dpkg/info/sasl2-bin.postinst configure
Starting SASL Authentication Daemon: saslauthd.
[... hangs here ...]
>From lsof output it seems saslauthd inherits the debconf pipe and does
not close it, therefore the frontend does not notice that the postinst
script has finished.
This seems to help:
--- sasl2-bin.postinst.orig 2008-01-09 10:35:27.000000000 +0100
+++ sasl2-bin.postinst 2008-01-09 10:35:37.000000000 +0100
@@ -63,6 +63,8 @@
if ! dpkg-statoverride --list $SASLDB_FILE >/dev/null 2>&1; then
dpkg-statoverride --update --add root sasl 660
$SASLDB_FILE
fi
+
+ db_stop
;;
abort-upgrade|abort-remove|abort-deconfigure)
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
