It could be worth checking the rpm versions of the 389-ds-console between your test system and your new system? 

It could also be good to check `yum whatprovides "*/slf4j-api.jar" ` in case there is a missing dependency? 

I'm not an expert on the console, so I hope that Mark can answer soon as he's our remaining console master. 

On 27 Aug 2019, at 04:19, Janet H <houser@nso.edu> wrote:

Additional info...   I just did a yum update on one of my 389-DS centos 7 boxes and I'm seeing the same error.   So it must be something about the new java files that the 389-console binary doesn't like.
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org