Description of problem:
can not start dirsrv-admin after upgrading from fedora 22 - 23 with dnf

# systemctl start dirsrv-admin
Job for dirsrv-admin.service failed because the control process exited with error code. See "systemctl status dirsrv-admin.service" and "journalctl -xe" for details.

# cat /var/log/dirsrv/admin-serv/error

SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
NSSSessionCacheTimeout is deprecated. Ignoring.
host_ip_init(): PSET failure: Failed to create PSET handle (pset error = )
AH00016: Configuration Failed

I have read that this points to permission errors with console.conf but changing permissions did nothing for me.

# ll /etc/dirsrv/admin-serv
total 172
-rw-------. 1 fedora-ds root   581 Dec  9 00:24 adm.conf
-rw-------. 1 fedora-ds root    40 May 12  2014 admpw
-rw-r--r--. 1 root      root  3936 Jun 16  2015 admserv.conf
drwxr-xr-x. 2 fedora-ds root  4096 May 12  2014 bakup
-rw-r--r--. 1 root      root 65536 Dec  9 00:24 cert8.db
-rw-r--r--. 1 fedora-ds root  4496 Jan  2 23:59 console.conf
-rw-r--r--. 1 root      root 26738 Jun 16  2015 httpd.conf
-rw-r--r--. 1 root      root 16384 Dec  9 00:24 key3.db
-rw-------. 1 fedora-ds root 13734 Dec  9 00:24 local.conf
-rw-r--r--. 1 root      root  4505 Jun 16  2015 nss.conf
-rw-r--r--. 1 root      root 16384 Dec  9 00:24 secmod.db

setenforce 0 still records the same error, and there are no selinux logs about anything with 389.

Version-Release number of selected component (if applicable):
# rpm -qa | grep 389
389-admin-console-1.1.10-2.fc23.noarch
389-ds-base-1.3.4.5-1.fc23.x86_64
389-ds-console-1.2.12-2.fc23.noarch
389-admin-console-doc-1.1.10-2.fc23.noarch
389-console-1.1.9-3.fc23.noarch
389-ds-1.2.2-7.fc23.noarch
389-adminutil-1.1.22-2.fc23.x86_64
389-admin-1.1.42-1.fc23.1.x86_64
389-dsgw-1.1.11-7.fc23.x86_64
389-ds-base-libs-1.3.4.5-1.fc23.x86_64
389-ds-console-doc-1.2.12-2.fc23.noarch

How reproducible:
I do remember i did a fresh install at fedora 20
fedup from 20 - 21. 389 still fully worked
fedup from 21 - 22. 389 still fully worked
dnf from 22 - 23. 389 still works but admin-serv will not start with the stated error.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: