[syslog-ng] trap divide error

[Dmitry Gilev]

It seems that the problems is here:

logsource.c (100): self->window_full_sleep_nsec = (diff / (cur_ack_count - self->last_ack_count));

I.e. cur_ack_count - self->last_ack_count is eq. 0 for some reason. I'll provide an update with backtrace shortly.

Thanks!
Dmitry

On Dec 21, 2011, at 10:00 AM, Gergely Nagy wrote:

> Dmitry Gilev <dmitry.gilev at me.com> writes:
> 
>> Hi,
>> 
>> I've started to get the following messages since upgrade to 3.3.3 (from 3.0.7:
>> 
>> From dmesg logs:
>> syslog-ng[30744] trap divide error ip:7fa0f8ed5a56 sp:7fa0f64423a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[30798] trap divide error ip:7fa0f8ed5a56 sp:7fa0df5fb3a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[31043] trap divide error ip:7fa0f8ed5a56 sp:7fa0d2bfa3a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[31059] trap divide error ip:7fa0f8ed5a56 sp:7fa0e6bfa3a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[31087] trap divide error ip:7fa0f8ed5a56 sp:7fa0de1f93a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[31145] trap divide error ip:7fa0f8ed5a56 sp:7fa0f64423a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[32733] trap divide error ip:7fa0f8ed5a56 sp:7fa0f64423a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[1404] trap divide error ip:7fa0f8ed5a56 sp:7fa0f6e433a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[1531] trap divide error ip:7fa0f8ed5a56 sp:7fa0f64423a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[1688] trap divide error ip:7fa0f8ed5a56 sp:7fa0e7ffc3a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[2013] trap divide error ip:7fa0f8ed5a56 sp:7fa0f4c2c3a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> syslog-ng[2019] trap divide error ip:7fa0f8ed5a56 sp:7fa0f6e433a0 error:0 in libsyslog-ng-3.3.3.so[7fa0f8ea3000+7b000]
>> 
>> Does anybody know what is wrong here? Is it known bug?
> 
> Could you perhaps get a backtrace from that?
> 
> The way to do that, is to run with --enable-debug, and it should drop a
> core file. Then you can use gdb to get a backtrace:
> 
> $ gdb -c /path/to/core /usr/local/sbin/syslog-ng
> (gdb) thread apply all bt full
> ...
> (gdb) quit
> 
> It would be best, if syslog-ng would be compiled with debugging symbols
> (-g), and not stripped. So that the backtrace would be actually useful
> :)
> 
> If this can't be done, then it would help if we'd know more about the
> stuation: were there any reloads around the time the crash occurred?
> What config do you use? How frequent does it crash?
> 
> Thanks!
> 
> -- 
> |8]
> 
> ______________________________________________________________________________
> 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
>