Thanks all, I just needed to run ldconfig in the end! cheers On Tue, Sep 12, 2017 at 5:42 PM, Czanik, Péter <peter.czanik@balabit.com> wrote:
Hi,
And to make your setting update proof, I'd like to emphasize the following paragraph from my blog: "
Hint: while the exact path changes with the update of Java, there are often some simplified links available. For example on Fedora Linux: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.51-4.b16.fc22.x86_64/jre/lib/amd64/server/ is also available as /usr/lib/jvm/java/jre/lib/amd64/server The first link changes with each Java update, the second one stays stable between updates.
"
This, or a similar link exists also on CentOS.
Bye,
Peter Czanik (CzP) <peter.czanik@balabit.com> Balabit / syslog-ng upstream https://www.balabit.com/blog/author/peterczanik/ https://twitter.com/PCzanik
On Tue, Sep 12, 2017 at 9:22 AM, Fabien Wernli <wernli@in2p3.fr> wrote:
Hi,
I believe Péter's diagnostic is correct. Another Péter's blog summarizes the "problem" on this blog post:
https://www.balabit.com/blog/troubleshooting-java-support-syslog-ng/
I for one chose the method of adding a file into ld's config file directory:
$ cat /etc/ld.so.conf.d/java.conf /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.141-1.b16.el7_3.x86_ 64/jre/lib/amd64/server
Of course your path will most probably be different. Also don't forget to run `ldconfig` afterwards.
Cheers
____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product= syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/? product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq