No, again same:

un 01 04:03:53 syslogserver systemd[1]: Failed to start System Logger Daemon.
-- Subject: Unit syslog-ng.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit syslog-ng.service has failed.
--
-- The result is failed.
Jun 01 04:03:53 syslogserver systemd[1]: Unit syslog-ng.service entered failed state.
Jun 01 04:03:53 syslogserver systemd[1]: syslog-ng.service failed.
Jun 01 04:03:59 syslogserver dhclient[634]: DHCPREQUEST on eth0 to 192.168.111.3 port 67 (xid=0x5bedf46c)
Jun 01 04:03:59 syslogserver dhclient[634]: DHCPACK from 192.168.111.3 (xid=0x5bedf46c)
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    address 192.168.111.233
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    plen 24 (255.255.255.0)
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    gateway 192.168.111.1
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    server identifier 192.168.111.3
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    lease time 120
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    hostname 'host-192-168-111-233'
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    nameserver '8.8.4.4'
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    nameserver '8.8.8.8'
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>    domain name 'openstacklocal'
Jun 01 04:03:59 syslogserver NetworkManager[608]: <info>  (eth0): DHCPv4 state changed bound -> bound
Jun 01 04:03:59 syslogserver dbus[607]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun 01 04:03:59 syslogserver dbus-daemon[607]: dbus[607]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun 01 04:03:59 syslogserver dhclient[634]: bound to 192.168.111.233 -- renewal in 54 seconds.
Jun 01 04:03:59 syslogserver systemd[1]: Starting Network Manager Script Dispatcher Service...
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-dispatcher.service has begun starting up.
Jun 01 04:03:59 syslogserver dbus[607]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 01 04:03:59 syslogserver dbus-daemon[607]: dbus[607]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 01 04:03:59 syslogserver nm-dispatcher[31487]: Dispatching action 'dhcp4-change' for eth0
Jun 01 04:03:59 syslogserver systemd[1]: Started Network Manager Script Dispatcher Service.
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-dispatcher.service has finished starting up.
--
-- The start-up result is done.


On 06/01/2016 10:02 AM, Czanik, Péter wrote:
Just the path name on a new line:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.el7_2.x86_64/jre/lib/amd64/server

Peter Czanik (CzP) <peter.czanik@balabit.com>
Balabit / syslog-ng upstream
http://czanik.blogs.balabit.com/
https://twitter.com/PCzanik

On Wed, Jun 1, 2016 at 10:00 AM, Ivan Adji - Krstev <akivanradix@gmail.com> wrote:
Hi,
Iv add this in the /etc/ld.so.conf file
include ld.so.conf.d/*.conf
export LD_LIBRARY_PATH=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.el7_2.x86_64/jre/lib/amd64/server:$LD_LIBRARY_PATH
But still nothing

Ivan

On 06/01/2016 09:48 AM, Czanik, Péter wrote:
Hi,

That only works for interactive sessions, systemctl does not take environment variables from the shell. If you are sure, that only a single Java version is used on your machine, I'd recommend adding the path to /etc/ld.so.conf or into a separate file under /etc/ld.so.conf.d/

Bye,


On Wed, Jun 1, 2016 at 9:37 AM, Ivan Adji - Krstev <akivanradix@gmail.com> wrote:
I have done that ...
export LD_LIBRARY_PATH=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.el7_2.x86_64/jre/lib/amd64/server:$LD_LIBRARY_PATH
And i put this in ~/.bashrc and bash_profile file.
and still can't start syslog-ng from systemctl

Ivan
On 06/01/2016 06:43 AM, Fabien Wernli wrote:
On Wed, Jun 01, 2016 at 12:29:49AM +0200, Ivan Adji - Krstev wrote:

And why when i execute like Syslog-NG -Fevd command works and i can see
the logs but when i try to execute like "systemctl start syslog-ng" it
Failed ?

LD_LIBRARY path most likely. read Peter's blog about that again

______________________________________________________________________________
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





______________________________________________________________________________
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





______________________________________________________________________________
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