(Fwd) Re: Seg Fault - radius 3.0 Debug

@lists.freeradius.org Subject:Re: Seg Fault - radius 3.0 Debug Hi,  Here is my debug file with gbd on the seg fault  [Thread debugging using libthread_db enabled] [New Thread 0x7600b700 (LWP 23433)] [Thread 0x7600b700 (LWP 23433) exited] Program received signal

Re: (Fwd) Re: Seg Fault - radius 3.0 Debug

Breuer Nicolas wrote: but.. Maybe variables have changed but since 3.0 version the variable %{Huntgroup-Name} is no more recognized. It should work. The git master branch hasn't changed any of that functionality. And (as always) what does debug mode say? Alan DeKok. - List

(Fwd) (Fwd) Re: Seg Fault - radius 3.0 Debug

: Breuer Nicolas nicolas.bre...@belcenter.biz To: freeradius-users@lists.freeradius.org Subject:(Fwd) Re: Seg Fault - radius 3.0 Debug Date sent: Fri, 18 Mar 2011 12:45:23 +0100 Hello, I finally solved my issue. It was a problem of linking mysql libs. I'm sorry . Apologies to all

Re: (Fwd) (Fwd) Re: Seg Fault - radius 3.0 Debug

Breuer Nicolas wrote: The debug mode said anything - No errors. Then I guess there are no problems. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Seg Fault - radius 3.0 Debug

Dear all, Here is my debug file with gbd on the seg fault [Thread debugging using libthread_db enabled] [New Thread 0x7600b700 (LWP 23433)] [Thread 0x7600b700 (LWP 23433) exited] Program received signal SIGSEGV, Segmentation fault. 0x76032890 in mysql_field_count () from

Re : Seg Fault - radius 3.0 Debug

More messages --- Forwarded message follows --- From: root r...@mail-mx-out.belcenter.com Date sent: Thu, 17 Mar 2011 18:43:14 +0100 To: nicolas.bre...@belcenter.be Program received signal SIGSEGV, Segmentation fault.

Re: Re : Seg Fault - radius 3.0 Debug

Breuer Nicolas wrote: Thread 1 (Thread 0x77bba720 (LWP 23430)): #0 0x76032890 in mysql_field_count () from /usr/lib64/mysql/libmysqlclient_r.so.16 No symbol table info available. #1 0x76391dee in sql_num_fields (sqlsocket=value optimized out, config=value optimized out)

Re: Seg Fault - radius 3.0 Debug

Hi,  Here is my debug file with gbd on the seg fault  [Thread debugging using libthread_db enabled] [New Thread 0x7600b700 (LWP 23433)] [Thread 0x7600b700 (LWP 23433) exited] Program received signal SIGSEGV, Segmentation fault. 0x76032890

(Fwd) Seg Fault - 3.0

--- Forwarded message follows --- From: Breuer Nicolas nicolas.bre...@belcenter.biz To: freeradius-de...@lists.freeradius.org Subject:Seg Fault - 3.0 Date sent: Wed, 16 Mar 2011 15:23:22 +0100 Hello I discovered a Seg Fault on the release 3.0 on the GIT server

Re: (Fwd) Seg Fault - 3.0

Breuer Nicolas wrote: ... Segmentation fault See doc/bugs I see the expand of variable HuntGroup-Name didn't get any values... Maybe the reason of Seg fault ? We don't know. You need to supply more information for us to know. Alan DeKok. - List info/subscribe/unsubscribe? See

Seg Fault - 3.0 - More Info needed

Hello Alan, Could you precise wich infos you need to go further ? Thanks --- End of forwarded message --- Hello I discovered a Seg Fault on the release 3.0 on the GIT server. Seems happening on the first auth. (30) Login OK: [XXX] (from client XXX) (30) # Executing section post

Re: Seg Fault - 3.0 - More Info needed

Breuer Nicolas wrote: Hello Alan, Could you precise wich infos you need to go further ? Yes. I was precise. Read the file doc/bugs. This is documented. Follow the instructions there. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: Seg Fault in 2.0.3

Garber, Neal wrote: I have a FR 2.0.3 server running under FreeBSD 6.3 which intermittently exits with a segmentation fault. Upgrade. I tried searching the list for known seg fault issues with 2.0.3 and only found one which sounded like it only happens when running under gdb. Do you

RE: Seg Fault in 2.0.3

Upgrade. That's what I was hoping you would say. Thanks Alan. Should I run FR under gdb to get more information about the seg fault? You could, but unless you're going to debug the source code yourself, I wouldn't suggest it. I would, but there's no need if upgrading to 2.1.3

Seg Fault in 2.0.3

I have a FR 2.0.3 server running under FreeBSD 6.3 which intermittently exits with a segmentation fault. I tried searching the list for known seg fault issues with 2.0.3 and only found one which sounded like it only happens when running under gdb. Do you think upgrading to 2.1.3 (it's the latest

Seg Fault - Not much info..

Hi, I'm running Freeradius 2.1.3 on my Ubuntu 8.04 machine. Basically, my setup is a VPN system linked to freeradius via a specialized plugin. Before I updated my freeradius (from the old 1.x), everything was working fine. Now that I have updated to 2.1.3, I can't seem to get it working

Re: Seg Fault - Not much info..

I'm running Freeradius 2.1.3 on my Ubuntu 8.04 machine. Basically, my setup is a VPN system linked to freeradius via a specialized plugin. Before I updated my freeradius (from the old 1.x), everything was working fine. Now that I have updated to 2.1.3, I can't seem to get it working again.

Re: Non capturing parenthesis in regexp causes seg fault.

Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1213196608

Re: Non capturing parenthesis in regexp causes seg fault.

Alan DeKok wrote: Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... It is... It allows you to create backreferences but not

Re: Non capturing parenthesis in regexp causes seg fault.

Arran Cudbard-Bell wrote: Alan DeKok wrote: Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... It is... It allows you to create

Non capturing parenthesis in regexp causes seg fault.

Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ } --- ++? if (%{User-Name} =~ /(?:.*)/) expand: %{User-Name} - anonymous Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1213196608 (LWP 6433)] 0xb7bc9492 in regexec () from

Re: Non capturing parenthesis in regexp causes seg fault.

Arran Cudbard-Bell wrote: Arran Cudbard-Bell wrote: Alan DeKok wrote: Arran Cudbard-Bell wrote: Hi, Got this on my 32bit intel box running Ubuntu Linux 6.10 if(%{User-Name} =~ /(?:.*)/){ I'm not sure that's a valid regular expression... '?' is usually a modifier... It is...

RE: seg fault

Since we have no idea what the problem is, the answer is likely no. totally fair =) If malloc() is core dumping, then something else is going wrong. i.e. some other part of the server is over-writing memory. when you say the server i assume you mean freeradius not another app.?? I

seg fault

I've been trying to pin down a rather elusive segfault for over 2 months now. and i finally got it to happen inside of gdb. this is freeradius 1.1.6, on rhel5 x86-64 if this problem is fixed in 2.0 or 1.1.7 please let me know. Starting program: /usr/sbin/radiusd -X [Thread debugging using

RE: seg fault

no - i'd read that as some other part of your 64bit x86 box is trashing the memory. hmm, the box itself is totally stable, nothing else has been an issue... hyperthreading on? no they are true dualcore Xeon's w/ no hyperthreading. Joe - List info/subscribe/unsubscribe? See

Re: seg fault

Hi, If malloc() is core dumping, then something else is going wrong. i.e. some other part of the server is over-writing memory. when you say the server i assume you mean freeradius not another app.?? no - i'd read that as some other part of your 64bit x86 box is trashing the memory.

Re: seg fault

Joe Vieira wrote: Hi, i've got freeradius 1.1.6 running on rhel5. when i goto do an ldap auth. i get this ... Segmentation fault See doc/bugs Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List

RE: seg fault

attached is my gdb log, looks like something happens with the ldap_set_option() function. thanks for having a lot Joe -Original Message- From: [EMAIL PROTECTED] on behalf of Alan Dekok Sent: Wed 6/13/2007 3:33 AM To: FreeRadius users mailing list Subject: Re: seg fault Joe Vieira

RE: seg fault

Found the issue, i added -DLDAP_DEPRECATED to the CFLAGS. Joe Joe Vieira wrote: Hi, i've got freeradius 1.1.6 running on rhel5. when i goto do an ldap auth. i get this ... Segmentation fault See doc/bugs Alan DeKok. -- http://deployingradius.com - The web site of the

seg fault

Hi, i've got freeradius 1.1.6 running on rhel5. when i goto do an ldap auth. i get this Listening on authentication 10.5.5.11:1812 Ready to process requests. rad_recv: Access-Request packet from host 10.5.5.11:32769, id=76, length=59 User-Name = jvieira User-Password = test

Re: EAP-TLS/seg fault with 4096 bit keys

James Lever wrote: As soon as I migrate back to 2k keys it again works as expected. Can anybody make any suggestions on how to debug this? doc/bugs Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List

EAP-TLS/seg fault with 4096 bit keys

Hi again list, Another issue I have had in setting up a WPA2 Enterprise environment is that I can get it to work as expected with 2k keys, however, if I go to 4k keys, freeradius 1.1.4 loads properly but seg faults when handling a 4k key request. The environment is Apple Airport Extreme

Problem Seg Fault

Hello I've just installed Fedora 4 with MYSQL 4.1.18 I tried to install the last version of freeradius and i 've a big error at the startup Mysql is correctly installed into the system.. startup with -X Module: Loaded SQL sql: driver = rlm_sql_mysql sql: server = xxx.yyy.be sql:

Re: Problem Seg Fault

] Organization: BELCENTER ISPPORTALS To: freeradius-users@lists.freeradius.org Date sent: Thu, 09 Feb 2006 21:30:38 +0100 Priority: normal Subject:Problem Seg Fault Send reply to: [EMAIL PROTECTED], FreeRadius

seg. fault with eap/tls and wrong certificate

hi all! i am trying to set up eap/tls using freeradius (1.0.4, on debian sarge, built package with option -disable-shared) and ran in the following problem: if i am using the wrong certificate (both client and server certs were build like the ones in the freeradius package using adapted CA.certs)

Re: mysql seg fault

Am Mi, den 22.12.2004 schrieb Mathias Röhl um 14:51: Hi Hi after rebuilding openssl and fr from the sources now the radiusd -X has no error, I don't know exactly why but it works have a few fine days and all the best for 2005... regards [EMAIL PROTECTED] -- TANK!!! I need an

mysql seg fault

Hi I installed fr from the source, also openssl, and tested with EAP/TLS and it works fine. So far...Now I want to do it with LDAP and MYSQL, LDAP for users and MYSQL for storing accounting informations. I configured in rlm_ldap and rlm_sql and after doing this I started radius -X -A, but nwo I

Re: mysql seg fault

Am Mi, den 22.12.2004 schrieb Mathias Röhl um 13:28: Am Mi, den 22.12.2004 schrieb Mathias Röhl um 11:47: Seems so I forgot to read the Documentation In order to build the drivers, you MUST ALSO install the development versions of the database. Hm'kay, I'll try it again Hi I did

RE: Seg fault in rlm_ldap on Redhat Enterprise Linux 3 - solved

://rhn.redhat.com/errata/RHBA-2004-224.html. Regards Tarun -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tarun Bhushan Sent: Tuesday, 17 August 2004 6:08 PM To: [EMAIL PROTECTED] Subject: RE: Seg fault in rlm_ldap on Redhat Enterprise Linux 3 - solved, sort

RE: Seg fault in rlm_ldap on Redhat Enterprise Linux 3 - solved, sort of

a match */ ret = LDAP_SUCCESS; } Regards Tarun -Original Message- From: Tarun Bhushan Sent: Tuesday, 17 August 2004 12:42 PM To: [EMAIL PROTECTED] Subject: Seg fault in rlm_ldap on Redhat Enterprise Linux 3 On Redhat Enterprise Linux 3, when I try to use LDAP (Port

Seg fault in rlm_ldap on Redhat Enterprise Linux 3

. Without TLS, it works fine, but as soon as the port is changed to 636 (or even another high port with tls_mode=yes), the seg fault happens. I am using FR version 1.0.0 on RHEL3 ES [OpenLDAP v2.0.27 (RH update 2.0.27-11), OpenSSL v0.9.7a (RH update 0.9.7a-33.4)]. I have previously tried

EAP/TLS - seg fault with bad certificate

Hi to all, I have configured freeradius with EAP/TLS on debian for testing. I have also create a CA and all necessary certificates. The system works well in normal condition but when I try to use on the supplicant a fake certificate (signed by another CA) freeradius get segmentation fault. I

Re: EAP/TLS - seg fault with bad certificate

Antonio Tamborino [EMAIL PROTECTED] wrote: Any idea? doc/bugs the report above is with FR 1.0.0pre2 compiled with Openssl 0.9.7d and 0.9.6m Uh.. both? That's bad. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: EAP/TLS - seg fault with bad certificate

First thank Antonio Tamborino [EMAIL PROTECTED] wrote: Any idea? doc/bugs I've forgotten to write that the problem exist also with a good certificate and the  check_cert_cn = %{User-Name} option in tls section. IT seems there is a problem analizing the certificate. the report above is

Re: EAP/TLS - seg fault with bad certificate

Antonio Tamborino [EMAIL PROTECTED] wrote: doc/bugs I've forgotten to write that the problem exist also with a good certificate ... Please READ doc/bugs, and FOLLOW IT'S SUGGESTIONS. There's no point in posting many messages saying it doesn't work, if you're not going to say what is

Re: Seg fault on Ascend-Data-Filter

Chris Chapman [EMAIL PROTECTED] wrote: When returning an Ascend-Data-Filter of ip in forward tcp est as the first data filter radiusd core dumps. When returning another data filter first such as ip in drop tcp dstport = 135 all data filters except the tcp est are returned with no errors.

Re: Seg fault on Ascend-Data-Filter

Alan DeKok wrote: Chris Chapman [EMAIL PROTECTED] wrote: When returning an Ascend-Data-Filter of ip in forward tcp est as the first data filter radiusd core dumps. When returning another data filter first such as ip in drop tcp dstport = 135 all data filters except the tcp est are returned

Re: Seg fault on Ascend-Data-Filter

Chris Chapman [EMAIL PROTECTED] wrote: When returning an Ascend-Data-Filter of ip in forward tcp est as the first data filter radiusd core dumps. When returning another data filter first such as ip in drop tcp dstport = 135 all data filters except the tcp est are returned with no errors.