RADIUS server is dumping core
Hi, I am using FreeRADIUS 2.2.0. Recently I have observed that RADIUS server is generating core frequently. I have tried debugging the core file using gdb. Please find the attached file for the gdb output for one of the core file generated. Please lemme know if you need any more information for tracing the core dump. Thanks, -- Best Regards, M.Rama Krishna Prasad,
ramakrishna wrote:
Hi,
I am using FreeRADIUS 2.2.0. Recently I have observed that RADIUS server is generating core frequently. I have tried debugging the core file using gdb.
Please find the attached file for the gdb output for one of the core file generated.
Hmm... I've never seen that before.
Please lemme know if you need any more information for tracing the core dump.
I suggest running it under valgrind. See doc/bugs Alan DeKok.
Hi Alan, I am using FreeRADIUS in solaris sever in which valgrind is not supported. Do you suspect access errors in RADIUS server for the dump based on the gdb log? In Solaris, we use dbx or bcheck to find access errors or memory leaks. Is it ok if i produce logs of those tools? Thanks, On Mon, Apr 22, 2013 at 7:05 PM, Alan DeKok <aland@deployingradius.com>wrote:
ramakrishna wrote:
Hi,
I am using FreeRADIUS 2.2.0. Recently I have observed that RADIUS server is generating core frequently. I have tried debugging the core file using gdb.
Please find the attached file for the gdb output for one of the core file generated.
Hmm... I've never seen that before.
Please lemme know if you need any more information for tracing the core dump.
I suggest running it under valgrind. See doc/bugs
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Best Regards, M.Rama Krishna Prasad,
ramakrishna wrote:
I am using FreeRADIUS in solaris sever in which valgrind is not supported.
Well... see if the same configuration fails on Linux, and run valgrind there.
Do you suspect access errors in RADIUS server for the dump based on the gdb log?
I don't know what to expect.
In Solaris, we use dbx or bcheck to find access errors or memory leaks. Is it ok if i produce logs of those tools?
Sure, so long as they're understandable by normal people. I've never used them, and know nothing about them. Alan DeKok.
Hi Alan, I have tried to find the access errors using dbx debugger in solaris. Please find the attached file for the access errors. We are facing dump quite frequently because of these access errors. Could you give us some idea where it might be going wrong? Thanks, On Fri, Apr 26, 2013 at 6:41 PM, Alan DeKok <aland@deployingradius.com>wrote:
ramakrishna wrote:
I am using FreeRADIUS in solaris sever in which valgrind is not supported.
Well... see if the same configuration fails on Linux, and run valgrind there.
Do you suspect access errors in RADIUS server for the dump based on the gdb log?
I don't know what to expect.
In Solaris, we use dbx or bcheck to find access errors or memory leaks. Is it ok if i produce logs of those tools?
Sure, so long as they're understandable by normal people. I've never used them, and know nothing about them.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Best Regards, M.Rama Krishna Prasad,
ramakrishna wrote:
I have tried to find the access errors using dbx debugger in solaris.
Please find the attached file for the access errors.
We are facing dump quite frequently because of these access errors.
Could you give us some idea where it might be going wrong?
Your system is completely broken. There seem to be tons of errors which should never occur. My guess is that you're using incompatible versions of software. i.e. FreeRADIUS 1.x with a library from 2.x, or something like that. Double-check that you have only ONE version of the server installed. Maybe try doing an install on a new Solaris machine. The server gets regular scans through valgrind && static analysis tools. There is *no way* that it could have a large number of errors, as shown by the Solaris dbx tool. There's something wrong with the binaries. Alan DeKok.
Hi Alan, Thanks for your suggestions. I have not used any of the 1.x versions of freeradius. However I have used 2.1.12 initially and finally migrated to 2.2. Could you please lemme know how to trace any incompatibilities if any between the two versions? Also please find the attached file which has only memory access errors which are leading to dump finally. Could you please suggest some way to get rid of those errors? Thanks a lot, On Sat, Apr 27, 2013 at 2:22 AM, Alan DeKok <aland@deployingradius.com>wrote:
ramakrishna wrote:
I have tried to find the access errors using dbx debugger in solaris.
Please find the attached file for the access errors.
We are facing dump quite frequently because of these access errors.
Could you give us some idea where it might be going wrong?
Your system is completely broken. There seem to be tons of errors which should never occur.
My guess is that you're using incompatible versions of software. i.e. FreeRADIUS 1.x with a library from 2.x, or something like that.
Double-check that you have only ONE version of the server installed. Maybe try doing an install on a new Solaris machine.
The server gets regular scans through valgrind && static analysis tools. There is *no way* that it could have a large number of errors, as shown by the Solaris dbx tool. There's something wrong with the binaries.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Best Regards, M.Rama Krishna Prasad,
On Mon, Apr 29, 2013 at 5:02 PM, ramakrishna <mramakrishnaprasad@gmail.com> wrote:
Also please find the attached file which has only memory access errors which are leading to dump finally. Could you please suggest some way to get rid of those errors?
Have you tried installing on a fresh solaris box, or using prebuilt packages, e.g. http://www.opencsw.org/package/freeradius/ , or even try the same setup on a linux box ? While it should be possible to find the problems in YOUR particular setup, doing so would require lots of effort. Remember, whatever help you might find on this list is provided for free, given as-is, by people willing to give up whatever small part of their own free time. Thus you shouldn't ask for something like "I don't really care whether it runs well on linux-or-whatever-platform-you-develop-on, I just want you to fix the problem on my system". -- Fajar
ramakrishna wrote:
I have not used any of the 1.x versions of freeradius. However I have used 2.1.12 initially and finally migrated to 2.2. Could you please lemme know how to trace any incompatibilities if any between the two versions?
My point was that's hard to do. Instead, ensure you have only ONE version installed.
Also please find the attached file which has only memory access errors which are leading to dump finally. Could you please suggest some way to get rid of those errors?
Do what I said: ensure you have only one version installed. There is no point trying to track down hundreds of errors. They all have the same root cause: incompatible binaries and libraries. Go fix that. Nothing else will solve it. Alan DeKok.
participants (3)
-
Alan DeKok -
Fajar A. Nugraha -
ramakrishna