On 1 May 2018 at 17:40, SOLER SANGUESA Miguel via FreeIPA-users <
freeipa-users(a)lists.fedorahosted.org> wrote:
hello,
I have an IPA master that updated from 4.5.0 (RHEL 7.4) to 4.5.4 (RHEL
7.5). An hour later I tried to do the same with the unique replica I have,
but after update dirsrv is not starting.
It says it is needed run "ipa-server-upgrade", but it also fails:
*# ipactl start*
*Upgrade required: please run ipa-server-upgrade command*
*Aborting ipactl*
*# ipa-server-upgrade*
*Upgrading IPA:. Estimated time: 1 minute 30 seconds*
* [1/8]: saving configuration*
* [2/8]: disabling listeners*
* [3/8]: enabling DS global lock*
* [4/8]: starting directory server*
* [error] CalledProcessError: Command '/bin/systemctl start
dirsrv(a)IPA-EXAMOLE-ORG.service' returned non-zero exit status 1*
* [cleanup]: stopping directory server*
* [cleanup]: restoring configuration*
*IPA server upgrade failed: Inspect /var/log/ipaupgrade.log and run
command ipa-server-upgrade manually.*
*Unexpected error - see /var/log/ipaupgrade.log for details:*
*CalledProcessError: Command '/bin/systemctl start
dirsrv(a)IPA-EXAMPLE-ORG.service' returned non-zero exit status 1*
*The ipa-server-upgrade command failed. See /var/log/ipaupgrade.log for
more information*
On the log I can see:
2018-04-30T14:36:15Z DEBUG Starting external process
2018-04-30T14:36:15Z DEBUG args=/bin/systemctl is-active
dirsrv(a)IPA-EXAMPLE-ORG.service
2018-04-30T14:36:15Z DEBUG Process finished, return code=3
2018-04-30T14:36:15Z DEBUG stdout=failed
...
2018-04-30T14:36:15Z DEBUG [4/8]: starting directory server
2018-04-30T14:36:15Z DEBUG Starting external process
2018-04-30T14:36:15Z DEBUG args=/bin/systemctl start
dirsrv(a)IPA-EXAMPLE-ORG.service
2018-04-30T14:36:15Z DEBUG Process finished, return code=1
2018-04-30T14:36:15Z DEBUG stdout=
2018-04-30T14:36:15Z DEBUG stderr=Job for dirsrv(a)IPA-EXAMPLE-ORG.service
failed because the control process exited with error code. See "systemctl
status dirsrv(a)IPA-EXAMPLE-ORG.service" and "journalctl -xe" for details.
2018-04-30T14:36:15Z DEBUG Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py",
line 504, in start_creation
run_step(full_msg, method)
File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py",
line 494, in run_step
method()
File
"/usr/lib/python2.7/site-packages/ipaserver/install/upgradeinstance.py",
line 95, in __start
srv.start(self.serverid, ldapi=True)
File "/usr/lib/python2.7/site-packages/ipaplatform/redhat/services.py",
line 161, in start
instance_name, capture_output=capture_output, wait=wait)
File "/usr/lib/python2.7/site-packages/ipaplatform/base/services.py",
line 294, in start
skip_output=not capture_output)
File "/usr/lib/python2.7/site-packages/ipapython/ipautil.py", line 542,
in run
raise CalledProcessError(p.returncode, arg_string, str(output))
CalledProcessError: Command '/bin/systemctl start
dirsrv(a)IPA-EXAMPLE-ORG.service' returned non-zero exit status 1
2018-04-30T14:36:15Z DEBUG [error] CalledProcessError: Command
'/bin/systemctl start dirsrv(a)IPA-EXAMPLE-ORG.service' returned non-zero
exit status 1
Checking /var/log/dirsrv/slapd-IPA-EXAMPLE-ORG/errors I show:
[30/Apr/2018:16:04:52.584220922 +0200] - ERR - slapd_bootstrap_config -
The default password storage scheme could not be read or was not found in
the file /etc/dirsrv/slapd-IPA-EXAMPLE-ORG/dse.ldif. It is mandatory.
Checking on internet I show that "dse.ldif" could be corrupted, so I
changed with "dse.ldif.startOK" without any change and then I changed with
"dse.ldif.bak". The problem persist but the error has changed:
[30/Apr/2018:16:32:13.435210918 +0200] - NOTICE - config_set_port -
Non-Secure Port Disabled
[30/Apr/2018:16:32:13.556581301 +0200] - ERR - symload_report_error -
Netscape Portable Runtime error -5975:
/usr/lib64/dirsrv/plugins/libreplication-plugin.so:
undefined symbol: replication_legacy_plugin_init
[30/Apr/2018:16:32:13.561590553 +0200] - ERR - symload_report_error -
Could not load symbol "replication_legacy_plugin_init" from
"/usr/lib64/dirsrv/plugins/libreplication-plugin.so" for plugin Legacy
Replication Plugin
[30/Apr/2018:16:32:13.564590264 +0200] - ERR - load_plugin_entry - Unable
to load plugin "cn=Legacy Replication Plugin,cn=plugins,cn=config"
I saw a bug about this problem, but it is still opened:
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1529442
Any idea how to fix the issue?
If it is not possible to fix it, can I remove the replica from IPA and
install it again with the same name?
I think I've just bumped into this same problem while updating my dev-ipa
instance.
Once IT have restored the VM from backup, I'll check to see if it's the
same error when I upgrade again, and follow these steps
Is there anything I can do to help diagnose?
Cheers
L.