REG: difference in debug and normal mode

[8zero2 operations]

Hi,

Going further, did a backtrace.

Got this:

Thread 1 "radiusd" received signal SIGSEGV, Segmentation fault.

0x00000000004310e7 in coa_retransmit (request=0x7fff7000a7d0) at
src/main/process.c:4295

4295 request->delay = delay * request->home_server->coa_irt;



Regards,
Mail: 8zero2.in at gmail.com
Facebook: www.facebook.com/8zero2
Twitter: @8zero2_in
Blog: blog.8zero2.in



On Wed, Oct 10, 2018 at 10:52 AM 8zero2 operations <8zero2ops at gmail.com>
wrote:

> Thanks Mathew,
>
> Did what you suggested, there is an exec program(php code) running which
> generates coa attributes. The server dies with a segmentation fault on that
> program,
>
>         wait = yes
>
>         input_pairs = request
>
>         output_pairs = coa
>
>         program = "/usr/bin/php /path/to/program '%{User-Name}'
> '%{control:Plan-Id}' 'allcoa'
> '%{%{Acct-Multi-Session-Id}:-%{Acct-Session-ID}}' '%{NAS-IP-Address}'"
>
>         shell_escape = yes
>
>         timeout = 10
>
>
> Regards,
> Mail: 8zero2.in at gmail.com
> Facebook: www.facebook.com/8zero2
> Twitter: @8zero2_in
> Blog: blog.8zero2.in
>
>
>
> On Tue, Oct 9, 2018 at 3:41 PM Matthew Newton <mcn at freeradius.org> wrote:
>
>> On Tue, 2018-10-09 at 14:19 +0530, 8zero2 operations wrote:
>> > Is there a difference in terms of the way packets are accepted when
>> > running
>> > in debugging mode versus the normal mode.
>>
>> Threading is disabled.
>>
>> > I have a very strange scenario where radius crashes when put in
>> > normal mode
>> > but runs just fine in debugging mode.
>>
>> Try
>>
>>   radiusd -fxxl stdout
>>
>> instead of -X.
>>
>> --
>> Matthew
>>
>> -
>> List info/subscribe/unsubscribe? See
>> http://www.freeradius.org/list/users.html
>
>