[syslog-ng] syslog-ng wont start - please help

vijay amruth vijayamruth at gmail.com
Fri May 5 06:51:28 UTC 2017 

Awesome!!!!
Right on dot. I commented that entry, restarted the process and it started
working. Thank you so much!!!!!!!

On Thu, May 4, 2017 at 11:17 PM, Scheidler, Balázs <
balazs.scheidler at balabit.com> wrote:

> The unit file states type=notify whereas syslog-ng may be compiled without
> notify support.
>
> That may explain the situation that syslog-ng is running but systemd
> thinks it didnt start up.
>
> On May 5, 2017 1:25 AM, "vijay amruth" <vijayamruth at gmail.com> wrote:
>
>> Hello Peter/ team, I am stuck with issue since four days, spent hours and
>> hours,  I am unable find a cause, I compiled syslog-ng from source and
>> resolved all the dependencies, when I get to start it, it wont start.  here
>> is the out put, please have a look at it. Any help is appreciated.
>>
>>
>> OS version : CentOS Linux release 7.3.1611 (Core)
>>
>>
>>
>> [root at my-host ~]# systemctl start   syslog-ng.service
>>
>> Job for syslog-ng.service failed because a timeout was exceeded. See
>> "systemctl status syslog-ng.service" and "journalctl -xe" for details.
>>
>>
>>
>> [root at my-host ~]# systemctl status syslog-ng.service
>>
>> ● syslog-ng.service - System Logger Daemon
>>
>>    Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled;
>> vendor preset: enabled)
>>
>>    Active: activating (start) since Thu 2017-05-04 16:13:44 PDT; 29s ago
>>
>>      Docs: man:syslog-ng(8)
>>
>>  Main PID: 5089 (syslog-ng)
>>
>>    CGroup: /system.slice/syslog-ng.service
>>
>>            └─5089 /usr/sbin/syslog-ng -F -p /var/run/syslogd.pid
>>
>>
>>
>> May 04 16:13:44 my-host systemd[1]: Starting System Logger Daemon...
>>
>>
>>
>> [root at my-host ~]# journalctl -xe
>>
>> May 04 16:10:01 my-host systemd[1]: Starting Session 348 of user root.
>>
>> -- Subject: Unit session-348.scope has begun start-up
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- Unit session-348.scope has begun starting up.
>>
>> May 04 16:10:21 my-host nslcd[1289]: [18832f] <group/member="root">
>> failed to bind to LDAP server ldap://ldap.vip.slc.e
>>
>> May 04 16:10:21 my-host nslcd[1289]: [18832f] <group/member="root"> no
>> available LDAP server found: Can't contact LDAP
>>
>> May 04 16:10:21 my-host nslcd[1289]: [18832f] <group/member="root"> no
>> available LDAP server found: Server is unavailab
>>
>> May 04 16:10:21 my-host CROND[5035]: (root) CMD (/usr/lib64/sa/sa1 1 1)
>>
>> May 04 16:10:23 my-host polkitd[676]: Registered Authentication Agent for
>> unix-process:5039:17396299 <(1)%20739%206299> (system bus name :
>>
>> May 04 16:10:23 my-host systemd[1]: Stopping Flush Journal to Persistent
>> Storage...
>>
>> -- Subject: Unit systemd-journal-flush.service has begun shutting down
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- Unit systemd-journal-flush.service has begun shutting down.
>>
>> May 04 16:10:23 my-host systemd-journal[2711]: Journal stopped
>>
>> -- Subject: The journal has been stopped
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- The system journal process has shut down and closed all currently
>>
>> -- active journal files.
>>
>> May 04 16:10:23 my-host systemd-journal[5046]: Runtime journal is using
>> 16.0M (max allowed 391.1M, trying to leave 586.
>>
>> May 04 16:10:23 my-host systemd-journal[5046]: Runtime journal is using
>> 16.0M (max allowed 391.1M, trying to leave 586.
>>
>> May 04 16:10:23 my-host systemd-journald[2711]: Received SIGTERM from PID
>> 1 (systemd).
>>
>> May 04 16:10:23 my-host systemd-journal[5046]: Journal started
>>
>> -- Subject: The journal has been started
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- The system journal process has started up, opened the journal
>>
>> -- files for writing and is now ready to process requests.
>>
>> May 04 16:10:23 my-host polkitd[676]: Unregistered Authentication Agent
>> for unix-process:5039:17396299 <(1)%20739%206299> (system bus name
>>
>> May 04 16:10:23 my-host systemd[1]: Starting Flush Journal to Persistent
>> Storage...
>>
>> -- Subject: Unit systemd-journal-flush.service has begun start-up
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- Unit systemd-journal-flush.service has begun starting up.
>>
>> May 04 16:10:23 my-host systemd[1]: Started Flush Journal to Persistent
>> Storage.
>>
>> -- Subject: Unit systemd-journal-flush.service has finished start-up
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- Unit systemd-journal-flush.service has finished starting up.
>>
>> --
>>
>> -- The start-up result is done.
>>
>> May 04 16:12:14 my-host polkitd[676]: Registered Authentication Agent for
>> unix-process:5066:17407401 <(1)%20740%207401> (system bus name :
>>
>> May 04 16:12:14 my-host systemd[1]: Starting System Logger Daemon...
>>
>> -- Subject: Unit syslog-ng.service has begun start-up
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- Unit syslog-ng.service has begun starting up.
>>
>> May 04 16:13:08 my-host nslcd[1289]: [528108] <group/member="postfix">
>> failed to bind to LDAP server ldap://ldap.vip.sl
>>
>> May 04 16:13:08 my-host nslcd[1289]: [528108] <group/member="postfix"> no
>> available LDAP server found: Can't contact LD
>>
>> May 04 16:13:08 my-host nslcd[1289]: [528108] <group/member="postfix"> no
>> available LDAP server found: Server is unavai
>>
>> May 04 16:13:44 my-host systemd[1]: syslog-ng.service start operation
>> timed out. Terminating.
>>
>> May 04 16:13:44 my-host 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.
>>
>> May 04 16:13:44 my-host systemd[1]: Unit syslog-ng.service entered failed
>> state.
>>
>> May 04 16:13:44 my-host systemd[1]: syslog-ng.service failed.
>>
>> May 04 16:13:44 my-host polkitd[676]: Unregistered Authentication Agent
>> for unix-process:5066:17407401 <(1)%20740%207401> (system bus name
>>
>> May 04 16:13:44 my-host systemd[1]: syslog-ng.service holdoff time over,
>> scheduling restart.
>>
>> May 04 16:13:44 my-host systemd[1]: Starting System Logger Daemon...
>>
>> -- Subject: Unit syslog-ng.service has begun start-up
>>
>> -- Defined-By: systemd
>>
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>
>> --
>>
>> -- Unit syslog-ng.service has begun starting up.
>>
>>
>>
>> [root at my-host ~]# ps -ef | grep syslog-ng
>>
>> root      5089     1  0 16:13 ?        00:00:00 /usr/sbin/syslog-ng -F -p
>> /var/run/syslogd.pid
>>
>> root      5103 32598  0 16:14 pts/1    00:00:00 grep --color=auto
>> syslog-ng
>>
>> [root at my-host ~]# systemctl status syslog-ng.service
>>
>> ● syslog-ng.service - System Logger Daemon
>>
>>    Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled;
>> vendor preset: enabled)
>>
>>    Active: activating (start) since Thu 2017-05-04 16:13:44 PDT; 1min 6s
>> ago
>>
>>      Docs: man:syslog-ng(8)
>>
>>  Main PID: 5089 (syslog-ng)
>>
>>    CGroup: /system.slice/syslog-ng.service
>>
>>            └─5089 /usr/sbin/syslog-ng -F -p /var/run/syslogd.pid
>>
>>
>>
>> May 04 16:13:44 my-host systemd[1]: Starting System Logger Daemon...
>>
>> [root at my-host ~]#cat /usr/lib/systemd/system/syslog-ng.service
>>
>> [Unit]
>>
>> Description=System Logger Daemon
>>
>> Documentation=man:syslog-ng(8)
>>
>>
>> [Service]
>>
>> Type=notify
>>
>> ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS -p /var/run/syslogd.pid
>>
>> ExecReload=/bin/kill -HUP $MAINPID
>>
>> EnvironmentFile=-/etc/default/syslog-ng
>>
>> EnvironmentFile=-/etc/sysconfig/syslog-ng
>>
>> StandardOutput=journal
>>
>> StandardError=journal
>>
>> Restart=on-failure
>>
>> Environment=SYSTEMD_LOG_LEVEL=debug
>>
>>
>> [Install]
>>
>> WantedBy=multi-user.target
>>
>>
>>
>>
>> --
>> Thanks,
>> Vijay Amrut.
>>
>> ____________________________________________________________
>> __________________
>> 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
>
>
>


-- 
Thanks,
Vijay Amrut.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20170504/27976174/attachment.html>

More information about the syslog-ng mailing list