Hello Wulf,

Oh yes, in your case, the slapd directory server is started but seems not listening on 389/636, according to the log file. On another further look, yes, you are right, the stack trace looks different from the one in Pagure.
As a side node, I had tried to install the jss rpm from updates-testing channel (according to Bugzilla #1766451). One of the replica server can complete the ipa-server-upgrade but the pki-tomcat failed to function properly. I had mentioned it in another mail: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org/thread/4HJSWIJQQYZQXUCEDUNZGPEKMOE7Z3MD/
Best regards,
Patrick

On Sun, Nov 3, 2019 at 6:16 PM Wulf C. Krueger <wk@mailstation.de> wrote:
Hello Patrick,

On 2019-11-02 20:54, Patrick Dung via FreeIPA-users wrote:
> I am having the same problem about three days ago.
> Related thread in:
> https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org/thread/WLBFHI266KKHLF6G2UC4MHR4OLCLR45S/

Thanks, I saw that thread while searching but (possibly wrongly) thought
it was a similar but ultimately different problem because as you write
there "I am able to connect to my ldap server port 636 with TLS without
problem." - which I most certainly am not. There's not even anything
listening on 636.

And the stack traces seem different as well.

A rather huge difference as well: In the pagure issue, the PKI server is
running whereas mine at least consistently refuses to start.

Best regards, Wulf