Hi Folks, I just created a Centos 7 VM (CentOS release 7.6.1810) and did a yum install of the epel directory: yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm and an install of 389-DS: yum install 389* I ran setup-ds-admin.pl as a stand alone system (this is a test machine). After the installation, I ran the following VERBOSE=1 /usr/bin/389-console which yielded an unfamiliar error: /usr/bin/build-classpath: Could not find slf4j-api.jar Java extension for this JVM I've built two test systems in the past, the most recent being in March of this year, and I've never seen this error before. My other two systems don't show the apache-sommons-codex.jar and the apache-commons-lang.jar file in the classpath and one of the systems is at the same CentOS release as this new server. I'm searching info about java and 389-DS to see if I need to add something to the system but I haven't had any luck yet. I'm sure there is a simple fix and I'm overlooking the obvious. The java packages between the systems look the same so I'm not quite sure why the clean build is looking for this jar file. Any suggestions would be appreciated. Thanks, janet |
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx