seg fault FR 3.0.2

[Łukasz Serwatka]

after trying to upgrade to FR3.0.3 seg fault when i try to start server (so
its probably worst case )

i upgraded talloc 2.08--> 2.1 it did not help



Reading symbols from /opt/sbin/radiusd...done.
(gdb) run -xl stdout
Starting program: /opt/sbin/radiusd -xl stdout
[Thread debugging using libthread_db enabled]
radiusd: FreeRADIUS Version 3.0.3, for host x86_64-unknown-linux-gnu, built
on May 13 2014 at 15:04:15
Copyright (C) 1999-2014 The FreeRADIUS server project and contributors
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE
You may redistribute copies of FreeRADIUS under the terms of the
GNU General Public License
For more information about these matters, see the file named COPYRIGHT
Starting - reading configuration files ...

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6f2820d in talloc_chunk_from_ptr () from /usr/lib/libtalloc.so.2
Missing separate debuginfos, use: debuginfo-install
glibc-2.12-1.132.el6_5.1.x86_64 keyutils-libs-1.4-4.el6.x86_64
krb5-libs-1.10.3-15.el6_5.1.x86_64 libcom_err-1.41.12-18.el6.x86_64
libpcap-1.4.0-1.20130826git2dbcaa1.el6.x86_64
libselinux-2.0.94-5.3.el6_4.1.x86_64 ncurses-libs-5.7-3.20090208.el6.x86_64
nss-softokn-freebl-3.14.3-10.el6_5.x86_64 openssl-1.0.1e-16.el6_5.7.x86_64
readline-6.0-4.el6.x86_64 zlib-1.2.3-29.el6.x86_64



2014-05-13 9:16 GMT+02:00 Arran Cudbard-Bell <a.cudbardb at freeradius.org>:

>
> On 13 May 2014, at 07:20, Łukasz Serwatka <selupl85 at gmail.com> wrote:
>
> > Hi,
> > i need help with FR 3.0.2 i use only dhcp i on my production server i
> have seg fault in message log
> >  kernel: radiusd[10692] general protection ip:7fa642360ba1
> sp:7fff2057e760 error:0 in libfreeradius-radius.so[7fa642342000+2f000]
> > when i use ps i see memory leak every few sec VSZ is inc +4
> >                        VSZ
> >  11442  0.0  0.1 432332  7404 ?        Ssl  08:14   0:00
> /usr/local/sbin/radiusd
> > could you give me some tips how to bug this issue ??
> >
>
> Upgrade to 3.0.3 and see if the problem still exists.
>
> If it does, set panic_action in radiusd.conf and provide the backtrace.
>
> -Arran
>
> Arran Cudbard-Bell <a.cudbardb at freeradius.org>
> FreeRADIUS Development Team
>
> FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20140513/69b61fd6/attachment-0001.html>