> On 27 Aug 2019, at 23:36, Janet Houser wrote:
>
> Well, I feel a little foolish.
>
> Simply doing"yum install slf4j" seems to have fixed the error.
I wonder if a package has a missing dependency in that case? You could raise an
issue on RH BZ, and provide the details of your yum
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:
Hi William,
Thanks! I'll work the issue from the OS side and post the solution here
when I find it.
Cheers,
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
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
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 --
