[syslog-ng] syslog-ng-3.9.1-1 is crashing

Wed May 17 04:47:07 UTC 2017

hey

I am not using the rsyslog

Harish

On Wed, May 17, 2017 at 5:07 AM, vijay amruth <vijayamruth at gmail.com> wrote:

> Are you using rsyslog?
>
> Vijay Amrut.
>
> On Sun, May 14, 2017 at 10:36 PM, Harish Shetty <harish23shetty at gmail.com>
> wrote:
>
>> Hey
>>
>>
>> I am seeing following issue , when i try to increase the fd_limit
>>
>> [root at lor1-x3-log02 hshetty]# /usr/sbin/syslog-ng -F -p
>> /var/run/syslogd-ng.pid --fd-limit 50000
>> [2017-05-15T05:36:04.820856] Error binding socket;
>> addr='AF_INET(0.0.0.0:515)', error='Address already in use (98)'
>> [2017-05-15T05:36:04.820894] Error initializing message pipeline;
>> [root at lor1-x3-log02 hshetty]#
>>
>> Regards
>> Harish Shetty
>>
>> On Thu, May 11, 2017 at 11:12 PM, vijay amruth <vijayamruth at gmail.com>
>> wrote:
>>
>>> I have added this in my unit file to increase the limit. hopefully helps.
>>>
>>> ExecStart=/usr/sbin/syslog-ng -F -p /var/run/syslogd-ng.pid --fd-limit
>>> 50000
>>>
>>> Vijay Amrut.
>>>
>>> On Thu, May 11, 2017 at 8:10 AM, Balazs Scheidler <bazsi77 at gmail.com>
>>> wrote:
>>>
>>>> It seems to be out of fds, and not disk space.
>>>>
>>>> You can increase fd limits with a command line option or using ulimit.
>>>>
>>>> On May 11, 2017 3:30 PM, "Harish Shetty" <harish23shetty at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Peter
>>>>>
>>>>> I have deployed syslog-ng-3.9.1-1.el6.x86_64 , where I am seeing one
>>>>> issue.  Where there is disk usage in greater than 90%, It coredumps.
>>>>> Instead of that shouldnt it be handle the syslog-ng service gracefully?
>>>>>
>>>>> I have pasted part of core here  and attached the coredump full file
>>>>>
>>>>>
>>>>> gdb) bt full
>>>>>
>>>>> #0  0x0000003b52a325e5 in raise () from /lib64/libc.so.6
>>>>>
>>>>> No symbol table info available.
>>>>>
>>>>> #1  0x0000003b52a33dc5 in abort () from /lib64/libc.so.6
>>>>>
>>>>> No symbol table info available.
>>>>>
>>>>> #2  0x0000003206c7506b in iv_fatal (fmt=<value optimized out>) at
>>>>> iv_fatal.c:57
>>>>>
>>>>>         ap = {{gp_offset = 8, fp_offset = 48, overflow_arg_area =
>>>>> 0x7f35c5aadac0,
>>>>>
>>>>>             reg_save_area = 0x7f35c5aada00}}
>>>>>
>>>>>         msg = "iv_init: can't initialize event
>>>>> dispatcher\000\006\062\000\000\000\177\000\000\bZ\003\000\00
>>>>> 0\000\000`KL\234\065\177\000\000?M006\062\000\000\000@֪\177\000\000@֪
>>>>> \177\000\000\177\000\000\b\000\000\000\000\000\000\
>>>>> 000L\234\065\177\000\000L\234\065\177\000\000\000KL\234\065\
>>>>> 177\000\000Ye006\062\000\000\000\001\000\000\000\000\000\000\000ت
>>>>> \177\000\000ت\177\000\000\177\000\000ت\177", '\000' <repeats 46
>>>>> times>, "\004", '\000' <repeats 35 times>...
>>>>>
>>>>> #3  0x0000003206c76f2a in iv_fd_init (st=0x7f359c945850) at iv_fd.c:129
>>>>>
>>>>> No locals.
>>>>>
>>>>> #4  0x0000003206c77499 in iv_init () at iv_main_posix.c:74
>>>>>
>>>>>         st = 0x7f359c945850
>>>>>
>>>>> #5  0x0000003206c75b8e in iv_work_thread (_thr=0x996c540) at
>>>>> iv_work.c:177
>>>>>
>>>>>         thr = 0x996c540
>>>>>
>>>>>         pool = 0x1df6820
>>>>>
>>>>> #6  0x0000003206c77def in iv_thread_handler (_thr=0x52933d0) at
>>>>> iv_thread_posix.c:142
>>>>>
>>>>>         __clframe = {__cancel_routine = 0x3206c77e50
>>>>> <iv_thread_cleanup_handler>,
>>>>>
>>>>>           __cancel_arg = 0x52933d0, __do_it = 1, __cancel_type = 0}
>>>>>
>>>>>         thr = 0x52933d0
>>>>>
>>>>> #7  0x0000003b53207aa1 in start_thread () from /lib64/libpthread.so.0
>>>>>
>>>>> No symbol table info available.
>>>>>
>>>>> ---Type <return> to continue, or q <return> to quit---
>>>>>
>>>>> #8  0x0000003b52ae8aad in clone () from /lib64/libc.so.6
>>>>>
>>>>> No symbol table info available.
>>>>>
>>>>>
>>>>>
>>>>> Can you please check and let me know   how can we fix this issue?
>>>>>
>>>>>
>>>>> Regards
>>>>> Harish shetty
>>>>>
>>>>> ____________________________________________________________
>>>>> __________________
>>>>> 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.
>>>
>>> ____________________________________________________________
>>> __________________
>>> 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.
>
> ____________________________________________________________
> __________________
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20170517/a23b9bf1/attachment-0001.html>