Well, I feel a little foolish. 

Simply doing    "yum install slf4j"  seems to have fixed the error.



[admin]#   VERBOSE=1  /usr/bin/389-console

Java virtual machine used: /usr/lib/jvm/jre/bin/java
classpath used:
/usr/share/java/apache-commons-codec.jar:/usr/share/java/apache-commons-lang.jar:/usr/share/java/slf4j/api.jar:/usr/share/java/slf4j/ext.jar:/usr/share/java/slf4j/jcl-over-slf4j.jar:/usr/share/java/slf4j/jcl.jar:/usr/share/java/slf4j/jdk14.jar:/usr/share/java/slf4j/jul-to-slf4j.jar:/usr/share/java/slf4j/log4j-over-slf4j.jar:/usr/share/java/slf4j/log4j12.jar:/usr/share/java/slf4j/migrator.jar:/usr/share/java/slf4j/nop.jar:/usr/share/java/slf4j/simple.jar:/usr/share/java/slf4j/site.jar:/usr/share/java/slf4j/slf4j-api.jar:/usr/share/java/slf4j/slf4j-ext.jar:/usr/share/java/slf4j/slf4j-jcl.jar:/usr/share/java/slf4j/slf4j-jdk14.jar:/usr/share/java/slf4j/slf4j-log4j12.jar:/usr/share/java/slf4j/slf4j-migrator.jar:/usr/share/java/slf4j/slf4j-nop.jar:/usr/share/java/slf4j/slf4j-simple.jar:/usr/share/java/slf4j/slf4j-site.jar:/usr/lib/java/jss4.jar:/usr/share/java/ldapjdk.jar:/usr/share/java/idm-console-base.jar:/usr/share/java/idm-console-mcc.jar:/usr/share/java/idm-console-mcc_en.jar:/usr/share/java/idm-console-nmclf.jar:/usr/share/java/idm-console-nmclf_en.jar:/usr/share/java/389-console_en.jar
main class used: com.netscape.management.client.console.Console
flags used:
options used:  -Djava.util.prefs.systemRoot=/root/.389-console   -Djava.util.prefs.userRoot=/root/.389-console
arguments used:


Thanks William....   Sorry for the dumb question.


On 8/26/19 5:12 PM, William Brown wrote:
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