Backtrace found in debug: FreeRadius 2.0.5 version
Dear Alan,Ivan and all, I have updated my FreeRadius version 2.0.5 Installed on SLES 10 SP2 through CVS. Now when I authenticate with a User i didn' get a BackTrace. But when I try to Authenticate against Openldap I see this Trace with Memory Map after Server returns back the result. Do I need to Install latest version of FreeRadius to be compatible with the CVS update for my current version. Regards, SYED sending Access-Reject of id 187 to 192.168.1.131 port 1047 *** glibc detected *** radiusd: double free or corruption (!prev): 0x0817dd80 *** ======= Backtrace: ========= /lib/libc.so.6[0xb7ddf961] /lib/libc.so.6(__libc_free+0x84)[0xb7de1404] /usr/local/lib/libfreeradius-radius-2.0.5.so(pairbasicfree+0x3a)[0xb7f36d6a] /usr/local/lib/libfreeradius-radius-2.0.5.so(pairfree+0x2c)[0xb7f3707c] radiusd[0x8061b73] radiusd(radius_handle_request+0x5b)[0x806249b] radiusd(thread_pool_addrequest+0x3c)[0x805bbec] radiusd[0x8060232] /usr/local/lib/libfreeradius-radius-2.0.5.so (fr_event_loop+0x236)[0xb7f3a8c6] radiusd(radius_event_process+0x30)[0x8060b70] radiusd(main+0x5dc)[0x805acac] /lib/libc.so.6(__libc_start_main+0xdc)[0xb7d918ac] radiusd[0x804d221] ======= Memory map: ======== 08048000-08076000 r-xp 00000000 08:06 259362 /usr/local/sbin/radiusd 08076000-08078000 rw-p 0002e000 08:06 259362 /usr/local/sbin/radiusd 08078000-0818b000 rw-p 08078000 00:00 0 [heap] b7800000-b7821000 rw-p b7800000 00:00 0 b7821000-b7900000 ---p b7821000 00:00 0 b79b9000-b79c3000 r-xp 00000000 08:03 340094 /lib/libgcc_s.so.1 b79c3000-b79c4000 rw-p 00009000 08:03 340094 /lib/libgcc_s.so.1 b79dd000-b7a12000 r--s 00000000 08:05 77489 /var/run/nscd/passwd b7a12000-b7a47000 r--s 00000000 08:05 77526 /var/run/nscd/dbbLcLLP (deleted) b7a47000-b7a49000 r-xp 00000000 08:06 893319 /usr/lib/libkrb5support.so.0.0 b7a49000-b7a4a000 rw-p 00002000 08:06 893319 /usr/lib/libkrb5support.so.0.0 b7a4a000-b7a6c000 r-xp 00000000 08:06 893307 /usr/lib/libk5crypto.so.3.0 b7a6c000-b7a6d000 rw-p 00022000 08:06 893307 /usr/lib/libk5crypto.so.3.0 b7a6d000-b7a83000 r-xp 00000000 08:06 893303 /usr/lib/libgssapi_krb5.so.2.2 b7a83000-b7a84000 rw-p 00015000 08:06 893303 /usr/lib/libgssapi_krb5.so.2.2 b7a84000-b7aec000 r-xp 00000000 08:06 893317 /usr/lib/libkrb5.so.3.2 b7aec000-b7aee000 rw-p 00068000 08:06 893317 /usr/lib/libkrb5.so.3.2 b7aee000-b7b24000 r-xp 00000000 08:06 893641 /usr/lib/libldap-2.3.so.0.2.20 b7b24000-b7b25000 rw-p 00036000 08:06 893641 /usr/lib/libldap-2.3.so.0.2.20 b7b25000-b7b38000 r-xp 00000000 08:03 340335 /lib/libnss_ldap.so.2 b7b38000-b7b39000 rw-p 00012000 08:03 340335 /lib/libnss_ldap.so.2 b7b39000-b7b44000 rw-p b7b39000 00:00 0 b7b5d000-b7c6d000 r-xp 00000000 08:06 893546 /usr/lib/libcrypto.so.0.9.8 b7c6d000-b7c81000 rw-p 0010f000 08:06 893546 /usr/lib/libcrypto.so.0.9.8 b7c81000-b7c85000 rw-p b7c81000 00:00 0 b7c85000-b7cbe000 r-xp 00000000 08:06 893547 /usr/lib/libssl.so.0.9.8 b7cbe000-b7cc2000 rw-p 00038000 08:06 893547 /usr/lib/libssl.so.0.9.8 b7cc2000-b7cd7000 r-xp 00000000 08:06 893294 /usr/lib/libsasl2.so.2.0.21 b7cd7000-b7cd8000 rw-p 00014000 08:06 893294 /usr/lib/libsasl2.so.2.0.21 b7cd8000-b7ce4000 r-xp 00000000 08:06 893639 /usr/lib/liblber-2.3.so.0.2.20 b7ce4000-b7ce5000 rw-p 0000b000 08:06 893639 /usr/lib/liblber-2.3.so.0.2.20 b7ce5000-b7d1f000 r-xp 00000000 08:06 893643 /usr/lib/libldap_r-2.3.so.0.2.20 b7d1f000-b7d21000 rw-p 00039000 08:06 893643 /usr/lib/libldap_r-2.3.so.0.2.20 b7d21000-b7d26000 rw-p b7d21000 00:00 0 b7d28000-b7d2a000 r-xp 00000000 08:03 340122 /lib/libcom_err.so.2.1 b7d2a000-b7d2b000 rw-p 00001000 08:03 340122 /lib/libcom_err.so.2.1 b7d2b000-b7d33000 r-xp 00000000 08:03 340069 /lib/libnss_files-2.4.so b7d33000-b7d35000 rw-p 00007000 08:03 340069 /lib/libnss_files-2.4.so b7d35000-b7d38000 r-xp 00000000 08:06 259212 /usr/local/lib/ rlm_detail-2.0.5.so b7d38000-b7d39000 rw-p 00002000 08:06 259212 /usr/local/lib/ rlm_detail-2.0.5.so b7d39000-b7d3b000 r-xp 00000000 08:06 259165 /usr/local/lib/ rlm_acct_unique-2.0.5.so b7d3b000-b7d3c000 rw-p 00001000 08:06 259165 /usr/local/lib/ rlm_acct_unique-2.0.5.so b7d3c000-b7d3e000 r-xp 00000000 08:06 259317 /usr/local/lib/ rlm_preprocess-2.0.5.so b7d3e000-b7d3f000 rw-p 00001000 08:06 259317 /usr/local/lib/ rlm_preprocess-2.0.5.so b7d3f000-b7d4b000 r-xp 00000000 08:06 1036627 /usr/lib/freeradius/ rlm_ldap-2.0.5.so b7d4b000-b7d4c000 rw-p 0000b000 08:06 1036627 /usr/lib/freeradius/rlm_ldap-2.0. Aborted
Syed Anwarul Hasan wrote:
I have updated my FreeRadius version 2.0.5 Installed on SLES 10 SP2 through CVS.
Huh?
Do I need to Install latest version of FreeRadius to be compatible with the CVS update for my current version.
Do not mix and match versions. If you install a version from git.freeradius.org, then the binaries will NOT be compatible with 2.0.5. Alan DeKok.
Thanks Alan for your reply, I got CVS update by means of Anonymous CVS source login from cvs.freeradius.org. I did it do overcome LDAP Caching Problem to avoid conflict between FreeRadius and Openldap server on same machine. I had a backup copy of /etc/raddb dir. So now I am not having a problem of backtrace. Regards, SYED On Fri, Sep 19, 2008 at 2:39 PM, Alan DeKok <aland@deployingradius.com>wrote:
Syed Anwarul Hasan wrote:
I have updated my FreeRadius version 2.0.5 Installed on SLES 10 SP2 through CVS.
Huh?
Do I need to Install latest version of FreeRadius to be compatible with the CVS update for my current version.
Do not mix and match versions. If you install a version from git.freeradius.org, then the binaries will NOT be compatible with 2.0.5.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Yes Alan I have done a big mistake, I have updated to 2.0.6 with the same binaries of 2.0.5. And now again I am getting backtraces. Anow in /etc/raddb dir I have another module radiusd which was not present in 2.0.5.and version file shows 2.0.6 using CVS , I have done source checkout radiusd module . I have not Installed Updated version from git.freeradius.org. How can I able to revert back to my earlier FreeRadius Version 2.0.5 to come out of this backtrace problem ? Please help me in this regard. SYED This is another backtrace I got today. *** glibc detected *** radiusd: double free or corruption (!prev): 0x0817e3e0 *** ======= Backtrace: ========= /lib/libc.so.6[0xb7d81961] /lib/libc.so.6(__libc_free+0x84)[0xb7d83404] /usr/local/lib/libfreeradius-radius-2.0.5.so(pairbasicfree+0x3a)[0xb7ed8d6a] /usr/local/lib/libfreeradius-radius-2.0.5.so(pairfree+0x2c)[0xb7ed907c] radiusd[0x8061b73] radiusd(radius_handle_request+0x5b)[0x806249b] radiusd(thread_pool_addrequest+0x3c)[0x805bbec] radiusd[0x8060232] /usr/local/lib/libfreeradius-radius-2.0.5.so (fr_event_loop+0x236)[0xb7edc8c6] radiusd(radius_event_process+0x30)[0x8060b70] radiusd(main+0x5dc)[0x805acac] /lib/libc.so.6(__libc_start_main+0xdc)[0xb7d338ac] radiusd[0x804d221] ======= Memory map: ======== 08048000-08076000 r-xp 00000000 08:06 259362 /usr/local/sbin/radiusd 08076000-08078000 rw-p 0002e000 08:06 259362 /usr/local/sbin/radiusd 08078000-0818b000 rw-p 08078000 00:00 0 [heap] b7800000-b7821000 rw-p b7800000 00:00 0 b7821000-b7900000 ---p b7821000 00:00 0 b7927000-b7931000 r-xp 00000000 08:03 340094 /lib/libgcc_s.so.1 b7931000-b7932000 rw-p 00009000 08:03 340094 /lib/libgcc_s.so.1 b794c000-b794d000 rw-p b794c000 00:00 0 b794d000-b7982000 r--s 00000000 08:05 77490 /var/run/nscd/dbRVYXV9 (deleted) b7982000-b79a4000 r-xp 00000000 08:06 893307 /usr/lib/libk5crypto.so.3.0 b79a4000-b79a5000 rw-p 00022000 08:06 893307 /usr/lib/libk5crypto.so.3.0 b79a5000-b79bb000 r-xp 00000000 08:06 893303 /usr/lib/libgssapi_krb5.so.2.2 b79bb000-b79bc000 rw-p 00015000 08:06 893303 /usr/lib/libgssapi_krb5.so.2.2 b79bc000-b7a24000 r-xp 00000000 08:06 893317 /usr/lib/libkrb5.so.3.2 b7a24000-b7a26000 rw-p 00068000 08:06 893317 /usr/lib/libkrb5.so.3.2 b7a26000-b7a5c000 r-xp 00000000 08:06 893641 /usr/lib/libldap-2.3.so.0.2.20 b7a5c000-b7a5d000 rw-p 00036000 08:06 893641 /usr/lib/libldap-2.3.so.0.2.20 b7a5d000-b7a70000 r-xp 00000000 08:03 340335 /lib/libnss_ldap.so.2 b7a70000-b7a71000 rw-p 00012000 08:03 340335 /lib/libnss_ldap.so.2 b7a71000-b7a7c000 rw-p b7a71000 00:00 0 b7a96000-b7ba6000 r-xp 00000000 08:06 893546 /usr/lib/libcrypto.so.0.9.8 b7ba6000-b7bba000 rw-p 0010f000 08:06 893546 /usr/lib/libcrypto.so.0.9.8 b7bba000-b7bbe000 rw-p b7bba000 00:00 0 b7bbe000-b7bf7000 r-xp 00000000 08:06 893547 /usr/lib/libssl.so.0.9.8 b7bf7000-b7bfb000 rw-p 00038000 08:06 893547 /usr/lib/libssl.so.0.9.8 b7bfb000-b7c10000 r-xp 00000000 08:06 893294 /usr/lib/libsasl2.so.2.0.21 On Fri, Sep 19, 2008 at 2:39 PM, Alan DeKok <aland@deployingradius.com>wrote:
Syed Anwarul Hasan wrote:
I have updated my FreeRadius version 2.0.5 Installed on SLES 10 SP2 through CVS.
Huh?
Do I need to Install latest version of FreeRadius to be compatible with the CVS update for my current version.
Do not mix and match versions. If you install a version from git.freeradius.org, then the binaries will NOT be compatible with 2.0.5.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Syed Anwarul Hasan wrote:
Yes Alan I have done a big mistake, I have updated to 2.0.6 with the same binaries of 2.0.5. And now again I am getting backtraces. Anow in /etc/raddb dir I have another module radiusd which was not present in 2.0.5. and version file shows 2.0.6
There is no version 2.0.6. Try deleting ALL of the various builds you've done, and starting again with 2.1.1.
How can I able to revert back to my earlier FreeRadius Version 2.0.5 to come out of this backtrace problem ?
Delete all of the builds, including all files that were installed, and start over. Alan DeKok.
Thanks Alan, I will delete all files and Install 2.1.1. SYED On Thu, Sep 25, 2008 at 3:01 PM, Alan DeKok <aland@deployingradius.com>wrote:
Syed Anwarul Hasan wrote:
Yes Alan I have done a big mistake, I have updated to 2.0.6 with the same binaries of 2.0.5. And now again I am getting backtraces. Anow in /etc/raddb dir I have another module radiusd which was not present in 2.0.5. and version file shows 2.0.6
There is no version 2.0.6. Try deleting ALL of the various builds you've done, and starting again with 2.1.1.
How can I able to revert back to my earlier FreeRadius Version 2.0.5 to come out of this backtrace problem ?
Delete all of the builds, including all files that were installed, and start over.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
A.L.M.Buxey@lboro.ac.uk -
Alan DeKok -
Syed Anwarul Hasan