ubuntu-389-directory-server team mailing list archive
-
ubuntu-389-directory-server team
-
Mailing list archive
-
Message #00319
[Bug 1816326] [NEW] package 389-ds-base 1.3.7.10-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported:
Similar to https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/1437709
I tried to upgrade Kolab on Ubuntu 18.04/bionic (but on armhf platform) and post-install for 389-ds-base fails.
ProblemType: Package
Architecture: armhf
Date: Sun Feb 17 23:11:26 2019
Package: 389-ds-base 1.3.7.10-1ubuntu1
SourcePackage: 389-ds-base
ErrorMessage:
installed 389-ds-base package post-installation script subprocess returned error exit status 1
Having a closer look at /var/lib/dpkg/info/389-ds-base.postinst it's clear (after adding some echo debug statements) that the line
setup-ds -l $OUT -u -s General.UpdateMode=offline > $OUT 2>&1
fails and invoking it manually produces same errors as shown here:
https://bugzilla.redhat.com/show_bug.cgi?id=1529442
---
setup-ds -u -s General.UpdateMode=offline
Updating instance (slapd-myInstance)...
Error: could not parse nsstate 803cc52fd21db201bc6e35613330ab060100000000000000 - tsdiff is 910277990972.671 seconds or 10535624.895517 days
Error: could not parse nsState from cn=uniqueid generator,cn=config. Value: 803cc52fd21db201bc6e35613330ab060100000000000000
Error: could not update the directory server.
Exiting . . .
---
It also shows in /var/log/dirsrv/slapd-myInstance/errors - not sure if
relevant, bug report above says it's from trying to start up the
instance:
---
[17/Feb/2019:20:15:51.331105158 +0100] - ERR - symload_report_error - Could not load symbol "replication_legacy_plugin_init" from "/usr/lib/arm-linux-gnueabihf/dirsrv/plugins/libreplication-plugin.so" for plugin Legacy Replication Plugin
[17/Feb/2019:20:15:51.421086549 +0100] - ERR - load_plugin_entry - Unable to load plugin "cn=Legacy Replication Plugin,cn=plugins,cn=config
---
Since this should be fixed some time ago I was wondering if the fix is
already included in this version.
** Affects: 389-ds-base (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-ds-base in Ubuntu.
https://bugs.launchpad.net/bugs/1816326
Title:
package 389-ds-base 1.3.7.10-1ubuntu1 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 1
Status in 389-ds-base package in Ubuntu:
New
Bug description:
Similar to https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/1437709
I tried to upgrade Kolab on Ubuntu 18.04/bionic (but on armhf platform) and post-install for 389-ds-base fails.
ProblemType: Package
Architecture: armhf
Date: Sun Feb 17 23:11:26 2019
Package: 389-ds-base 1.3.7.10-1ubuntu1
SourcePackage: 389-ds-base
ErrorMessage:
installed 389-ds-base package post-installation script subprocess returned error exit status 1
Having a closer look at /var/lib/dpkg/info/389-ds-base.postinst it's clear (after adding some echo debug statements) that the line
setup-ds -l $OUT -u -s General.UpdateMode=offline > $OUT 2>&1
fails and invoking it manually produces same errors as shown here:
https://bugzilla.redhat.com/show_bug.cgi?id=1529442
---
setup-ds -u -s General.UpdateMode=offline
Updating instance (slapd-myInstance)...
Error: could not parse nsstate 803cc52fd21db201bc6e35613330ab060100000000000000 - tsdiff is 910277990972.671 seconds or 10535624.895517 days
Error: could not parse nsState from cn=uniqueid generator,cn=config. Value: 803cc52fd21db201bc6e35613330ab060100000000000000
Error: could not update the directory server.
Exiting . . .
---
It also shows in /var/log/dirsrv/slapd-myInstance/errors - not sure if
relevant, bug report above says it's from trying to start up the
instance:
---
[17/Feb/2019:20:15:51.331105158 +0100] - ERR - symload_report_error - Could not load symbol "replication_legacy_plugin_init" from "/usr/lib/arm-linux-gnueabihf/dirsrv/plugins/libreplication-plugin.so" for plugin Legacy Replication Plugin
[17/Feb/2019:20:15:51.421086549 +0100] - ERR - load_plugin_entry - Unable to load plugin "cn=Legacy Replication Plugin,cn=plugins,cn=config
---
Since this should be fixed some time ago I was wondering if the fix is
already included in this version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/1816326/+subscriptions
Follow ups