- Freeradius-Devel - lists.freeradius.org

Inconsistent behaviour with duplicate dictionary entries
by Brian Candler 02 Aug '12

02 Aug '12

(freeradius 2.1.12) I have noticed an inconsistency when there are duplicate dictionary entries for the same attribute, in particular this one from dictionary.redback: ATTRIBUTE Qos-Policy-Metering 88 string ATTRIBUTE Qos-Metering-Profile-Name 88 string When radtest/radclient is decoding response packets it uses the second entry (this makes sense, it's the last entry read which takes precedence). However the debug output from freeradius -X displays the first entry instead. Example: $ echo -e 'User-Name = "foo(a)example.com"\nCalling-Station-Id="12345678"\nNAS-IP-Address=255.255.255.244\n' | radclient localhost auth testing123 Received response ID 166, code 2, length = 68 Qos-Metering-Profile-Name = "24M_P" Double-Authentication = 1 but freeradius -X shows: ... Sending Access-Accept of id 67 to 127.0.0.1 port 42234 Qos-Policy-Metering := "24M_P" Double-Authentication := 1 Finished request 0. Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 67 with timestamp +2 This is only significant because I have a GUI wrapper with a radtest function which displays the debug output. This uses the control socket to inject the packet, so I get slightly different output from freeradius -X, but it also shows the first dictionary entry: ... Injected Access-Accept packet to host 127.0.0.1 port 0 code=2, id=3 Qos-Policy-Metering := "24M_P" Double-Authentication := 1 Finished request 3. Going to the next request Thread 44 waiting to be assigned a request Anyway, this suggests to me that there may be two different code paths for looking up attribute numbers to names; maybe they could be unified? Regards, Brian.

2 2

Re: Freeradius-Devel Digest, Vol 88, Issue 1
by karthik kumar 02 Aug '12

02 Aug '12

Hi Fajar, First of all thanks for fast reply . I have used following config changes in users and clients.conf , do ppoe session requires any special changes. Please suggest me inline questions. http://www.iana.org/assignments/radius-types/radius-types.xml#radius-types-3 Attribute value 61 ---> Nas-port-type 32PPPoEoE - PPP over Ethernet over Ethernet Should this be configured for users.conf or client.conf file ? [root@PC4-Abhi raddb]# more users cisco Auth-Type := Local, User-Password = "cisco" cisco-avpair = "shell:Admin=Admin default-domain karthik karthik1" DEFAULT Framed-Protocol == PPP Framed-Protocol = PPP, Framed-Compression = Van-Jacobson-TCP-IP [root@PC4-Abhi raddb]# more clients.conf .. client 78.0.0.0/16 { secret = cisco shortname = cisco nastype = cisco >>>>>>>>>>>>>>>>>> should it be other ? do we have to configure NAS-ip and attribute value and type ? } Thanks, K. Karthik Kumar On Wed, Aug 1, 2012 at 3:30 PM, < freeradius-devel-request(a)lists.freeradius.org> wrote: > Send Freeradius-Devel mailing list submissions to > freeradius-devel(a)lists.freeradius.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freeradius.org/mailman/listinfo/freeradius-devel > or, via email, send a message with subject or body 'help' to > freeradius-devel-request(a)lists.freeradius.org > > You can reach the person managing the list at > freeradius-devel-owner(a)lists.freeradius.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Freeradius-Devel digest..." > > > Today's Topics: > > 1. BNG(BRAS) + free radius (karthik kumar) > 2. Re: BNG(BRAS) + free radius (Fajar A. Nugraha) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 1 Aug 2012 13:04:57 +0530 > From: karthik kumar <mail2karthek(a)gmail.com> > To: freeradius-devel(a)lists.freeradius.org > Subject: BNG(BRAS) + free radius > Message-ID: > < > CANHveityOa4QmOe2EX6K4CsX8zdATxPqEBUD-muaFbRb3PCLLw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Team, > > > > I have used free radius for authentication purpose but I never tried for > BNG. > > > > > > MY requirement is as follows: > > > > > > > > PPOE client (router) -----------------------? PPOE > server(router) -------------? Free > radius > > > > > > > When many internet users try to connect to isp router the free radius > connected to the ppoe server should authenticate all the users in the > client. What are the configuration changes need to be applied in the free > radius. > > > > > > > > > > https://supportforums.cisco.com/docs/DOC-19726 >>>>>>>>>>>>. > Configuration explaination > > > > > > Thanks, > > K. Karthik Kumar >

1 0

BNG(BRAS) + free radius
by karthik kumar 01 Aug '12

01 Aug '12

Hi Team, I have used free radius for authentication purpose but I never tried for BNG. MY requirement is as follows: PPOE client (router) ----------------------- PPOE server(router) ------------- Free radius When many internet users try to connect to isp router the free radius connected to the ppoe server should authenticate all the users in the client. What are the configuration changes need to be applied in the free radius. https://supportforums.cisco.com/docs/DOC-19726 >>>>>>>>>>>>. Configuration explaination Thanks, K. Karthik Kumar

2 1

Source Code Modification Help - No Clear Text User-Password logging
by Mark Selby 30 Jul '12

30 Jul '12

I am send this to the freeradius-devel list as I am asking for help on source code modification and felt this was more appropriate than freeradius-users list. If it is felt by many that I should re-submit under the users list I will be happy to do so. I do not have any C programming experience but have made small modifications and compiled tens of open source software programs. I am using freeradius for my company as 802.1x wireless authentication backend for our internal wifi network. We extensively use Kerberos (MIT) as an authentication mechanism and have configured TTLS/PAP on the client and rlm_krb5 to allow users to authenticate using their Kerberos principals and passwords. As a general practice we never ask what other users passwords are, never transmit passwords over the wire in clear text, and never log passwords on disk. I have found there are 2 ways to get the freeradius server to log clear text passwords and would like to ask for source code modification examples or at least pointers the right place to make them such that I can compile a custom version of the software that does not do this. We do want to be able ever to see our users passwords (1) log_auth_badpass|log_auth_goodpass I see there are 4 source files (radiusd.h auth.c mainconfig.c radiusd.c) that include references to log_auth_badpass and log_auth_goodpass. I figure that I can read the code and make any minor modifications that make sure these options can not be turned on. (2) radiusd -X When running in debug mode I can often see on the screen output like the below: [ttls] Got tunneled request User-Name = "gonzo" User-Password = "a_password" FreeRADIUS-Proxied-To = 127.0.0.1 [ttls] Sending tunneled request User-Name = "gonzo" User-Password = "a_password" FreeRADIUS-Proxied-To = 127.0.0.1 NAS-IP-Address = 10.0.1.218 NAS-Identifier = "AP-7eff00" NAS-Port = 0 Called-Station-Id = "AA-1E-72-7A-AA-00:radius" Calling-Station-Id = "A4-5A-AE-54-04-48" Framed-MTU = 1500 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" I can not seem to figure out in the code how to make sure that the User-Password is never printed in the clear like it is above. Any pointers to where in the code I can turn this off would be greatly appreciated. Thanks!

4 3

Tabs in SQL queries...
by Arran Cudbard-Bell 23 Jul '12

23 Jul '12

What do people think to stripping out tabs in xlated SQL queries so that the debug output is actually readable? Is it likely to cause problems for different SQL dialects? -Arran

5 6

Issue with rlm_replicate and retransmissions
by Brian Candler 14 Jul '12

14 Jul '12

I have found some odd behaviour to do with proxying and retransmissions with rlm_replicate (specifically accounting packets) I set up a proxy config, where I also happen to modify the packet. preacct { ... Proxy-To-Realm := "handover" ... update request { Reply-Message += "foo" } } As well as proxying, rlm_replicate is used to feed the accounting packets elsewhere: accounting { sql_log ... replicate # using rlm_replicate and Replicate-To-Realm } Now, if the "handover" home servers are down, and I send a test packet with retransmissions using echo -e 'User-Name="briantest"\nEvent-Timestamp=1342099825\nFramed-IP-Address=1.2.3.4\nAcct-Status-Type=Interim-Update' | radclient -r3 -t3 -x localhost:1813 acct testing123 what I find is: * just the first packet is written to the sql_log (that's fine) * For the second and third packets, freeradius -X just shows "Discarding duplicate request from client localhost port 36957 - ID: 146" After that, freeradius says "Rejecting request 0 (proxy Id 181) due to lack of any response from home server 192.0.2.1 port 1813" * all three packets are replicated. The second and third replica packets are missing the Reply-Message attribute It's this last bit which I think is odd. Shouldn't the replicate also be suppressed for retransmissions? Or if not, shouldn't it at least process the packet in the same way? Regards, Brian.

2 1

Query regarding running radexample to connect to radiusd server over ipv6
by Harshit Shah 03 Jul '12

03 Jul '12

Hello, I have configured my server to run radius on ipv6 and I was also able to successfully connect to radius server using radclient binary on my client machine. I installed radiusclient as well my machine and I am trying to run radexample to login to radius server over ipv6, however I am not able to connect to it over ipv6. I was able to connect to radiusserver using ipv4 through radexample. Can anyone help me out with this? What all options shall I check to proceed further with this? Regards, Harshit

3 5

CUI Postgres Patch
by Scott Armitage 28 Jun '12

28 Jun '12

Hi, a patch for adding postgres support to CUI: diff --git a/raddb/mods-available/cui b/raddb/mods-available/cui index 2464613..b1ba225 100644 --- a/raddb/mods-available/cui +++ b/raddb/mods-available/cui @@ -5,10 +5,15 @@ # # Write Chargeable-User-Identity to the database. # -# Schema raddb/sql/mysql/cui.sql -# Queries raddb/sql/mysql/cui.conf +# Schema raddb/sql/DB/cui.sql +# Queries raddb/sql/DB/cui.conf # sql cui { + # + # Set the database to one of: + # + # mysql, postgresql + # database = "mysql" driver = "rlm_sql_${database}" server = "localhost" diff --git a/raddb/sql/postgresql/cui.conf b/raddb/sql/postgresql/cui.conf new file mode 100644 index 0000000..d90eccc --- /dev/null +++ b/raddb/sql/postgresql/cui.conf @@ -0,0 +1,31 @@ +# -*- text -*- + +## +## Queries to update the CUI table. +## +postauth_query = "INSERT INTO ${cui_table} \ + (clientipaddress, callingstationid, username, cui) \ + VALUES \ + ('%{Client-IP-Address}', '%{Calling-Station-Id}', '%{User-Name}', '%{reply:Chargeable-User-Identity}')"; + +accounting_start_query = "UPDATE ${cui_table} \ + SET \ + lastaccounting = now() \ + WHERE clientipaddress = '%{Client-IP-Address}' \ + AND callingstationid = '%{Calling-Station-Id}' \ + AND username = '%{User-Name}' \ + AND cui = '%{Chargeable-User-Identity}'"; + +accounting_update_query = "UPDATE ${cui_table} \ + SET \ + lastaccounting = now() \ + WHERE clientipaddress = '%{Client-IP-Address}' \ + AND callingstationid = '%{Calling-Station-Id}' \ + AND username = '%{User-Name}' \ + AND cui = '%{Chargeable-User-Identity}'"; + +accounting_stop_query = "DELETE FROM ${cui_table} WHERE \ + clientipaddress = '%{Client-IP-Address}' \ + AND callingstationid = '%{Calling-Station-Id}' \ + AND username = '%{User-Name}' \ + AND cui = '%{Chargeable-User-Identity}'"; diff --git a/raddb/sql/postgresql/cui.sql b/raddb/sql/postgresql/cui.sql new file mode 100644 index 0000000..34346da --- /dev/null +++ b/raddb/sql/postgresql/cui.sql @@ -0,0 +1,14 @@ +CREATE TABLE cui ( + clientipaddress INET NOT NULL DEFAULT '0.0.0.0', + callingstationid varchar(50) NOT NULL DEFAULT '', + username varchar(64) NOT NULL DEFAULT '', + cui varchar(32) NOT NULL DEFAULT '', + creationdate TIMESTAMP with time zone NOT NULL default 'now()', + lastaccounting TIMESTAMP with time zone NOT NULL default '-infinity'::timestamp, + PRIMARY KEY (username, clientipaddress, callingstationid) +); + +CREATE RULE postauth_query AS ON INSERT TO cui + WHERE EXISTS(SELECT 1 FROM cui WHERE (username, clientipaddress, callingstationid)=(NEW.username, NEW.clientipaddress, NEW.callingstationid)) + DO INSTEAD UPDATE cui SET lastaccounting ='-infinity'::timestamp with time zone, cui=NEW.cui WHERE (username, clientipaddress, callingstationid)=(NEW.username, NEW.clientipaddress, NEW.callingstationid); +

2 1

GIT HEAD policy.conf
by alan buxey 27 Jun '12

27 Jun '12

hi, minor patch applied: --- policy.conf 2012-06-14 12:21:44.431408916 +0100 +++ /tmp/policy.conf 2012-06-27 11:53:09.170949750 +0100 @@ -268,9 +268,9 @@ # Realm begins with a dot # e.g. "user@.site.com" # - if (User-Name !~ /(a)\\./) { + if (User-Name =~ /(a)\\./) { update reply { - Reply-Message+ = "Rejected: Realm begins with a dot" + Reply-Message += "Rejected: Realm begins with a dot" } reject } @@ -326,7 +326,7 @@ # if (!Chargeable-User-Identity) { update control { - Chargable-User-Identity := "%{cui: SELECT cui FROM cui WHERE clientipaddress = '%{Client-IP-Address}' AND callingstationid = '%{Calling-Station-Id}' AND username = '%{User-Name}'}" + Chargeable-User-Identity := "%{cui: SELECT cui FROM cui WHERE clientipaddress = '%{Client-IP-Address}' AND callingstationid = '%{Calling-Station-Id}' AND username = '%{User-Name}'}" } } 1) fixes wrong check 2) fixes wrong operator (typo/space) 3) fixes speeling mistak in Chargeable-User-Identity server now runs again alan

1 0

FR 3.0.0 Seg Fault when Proxying to Dead server
by Scott Armitage 27 Jun '12

27 Jun '12

All, I got a FR3 to Seg Fault today when it tried to proxy an authentication attempt to another RADIUS server. The conditions were/are: * proxying over IPv6 * using RADSEC * Other server is Dead I have reproduced the Seg Fault by blocking outgoing communication (using ip6tables) to a working server. Wed Jun 27 11:25:26 2012 : Info: (2) files : preproxy_users: Matched entry DEFAULT at line 33 Wed Jun 27 11:25:26 2012 : Info: (2) [files] = ok Wed Jun 27 11:25:26 2012 : Info: (2) policy cui.pre-proxy { Wed Jun 27 11:25:26 2012 : Info: (2) - entering policy cui.pre-proxy {...} Wed Jun 27 11:25:26 2012 : Info: (2) update proxy-request { Wed Jun 27 11:25:26 2012 : Info: (2) } # update proxy-request = ok Wed Jun 27 11:25:26 2012 : Info: (2) - policy cui.pre-proxy returns ok Wed Jun 27 11:25:26 2012 : Info: (2) pre_proxy_log : expand: /var/log/radius/radacct/%{Client-IP-Address}/pre-proxy-detail-%Y%m%d -> /var/log/radius/radacct/131.231.190.6/pre-proxy-detail-20120627 Wed Jun 27 11:25:26 2012 : Info: (2) pre_proxy_log : /var/log/radius/radacct/%{Client-IP-Address}/pre-proxy-detail-%Y%m%d expands to /var/log/radius/radacct/131.231.190.6/pre-proxy-detail-20120627 Wed Jun 27 11:25:26 2012 : Info: (2) pre_proxy_log : expand: %t -> Wed Jun 27 11:25:26 2012 Wed Jun 27 11:25:26 2012 : Info: (2) [pre_proxy_log] = ok Wed Jun 27 11:25:26 2012 : Debug: Opening new proxy (::, 0) -> home_server (2001:630:1:129::249, 2083) Wed Jun 27 11:25:26 2012 : Debug: Waking up in 0.1 seconds. Wed Jun 27 11:25:26 2012 : Debug: Waking up in 0.4 seconds. Segmentation fault Starting program: /usr/sbin/radiusd -f [Thread debugging using libthread_db enabled] [New Thread 0x7fffe8208700 (LWP 1321)] [New Thread 0x7fffe7807700 (LWP 1322)] [New Thread 0x7fffe6e06700 (LWP 1323)] [New Thread 0x7fffe6405700 (LWP 1324)] [New Thread 0x7fffe5a04700 (LWP 1325)] [New Thread 0x7fffe5003700 (LWP 1326)] [New Thread 0x7fffe4602700 (LWP 1327)] [New Thread 0x7fffe3c01700 (LWP 1329)] [New Thread 0x7fffe3200700 (LWP 1330)] [New Thread 0x7fffe27ff700 (LWP 1332)] [New Thread 0x7fffe1dfe700 (LWP 1333)] [New Thread 0x7fffe13fd700 (LWP 1336)] [New Thread 0x7fffe09fc700 (LWP 1337)] [New Thread 0x7fffdfffb700 (LWP 1338)] [New Thread 0x7fffdf5fa700 (LWP 1339)] [New Thread 0x7fffdebf9700 (LWP 1340)] [New Thread 0x7fffde1f8700 (LWP 1341)] [New Thread 0x7fffdd7f7700 (LWP 1342)] [New Thread 0x7fffdcdf6700 (LWP 1343)] [New Thread 0x7fffdc3f5700 (LWP 1344)] [New Thread 0x7fffdb9f4700 (LWP 1345)] [New Thread 0x7fffdaff3700 (LWP 1346)] [New Thread 0x7fffda5f2700 (LWP 1347)] [New Thread 0x7fffd9bf1700 (LWP 1348)] [New Thread 0x7fffd91f0700 (LWP 1349)] [New Thread 0x7fffd87ef700 (LWP 1350)] [New Thread 0x7fffd7dee700 (LWP 1352)] [New Thread 0x7fffd73ed700 (LWP 1353)] [New Thread 0x7fffd69ec700 (LWP 1355)] [New Thread 0x7fffd5feb700 (LWP 1356)] [New Thread 0x7fffd55ea700 (LWP 1357)] [New Thread 0x7fffd4be9700 (LWP 1358)] [New Thread 0x7fffd41e8700 (LWP 1359)] [New Thread 0x7fffd37e7700 (LWP 1360)] [New Thread 0x7fffd2de6700 (LWP 1361)] [New Thread 0x7fffd23e5700 (LWP 1362)] [New Thread 0x7fffd19e4700 (LWP 1363)] [New Thread 0x7fffd0fe3700 (LWP 1364)] [New Thread 0x7fffd05e2700 (LWP 1365)] [New Thread 0x7fffcfbe1700 (LWP 1366)] [New Thread 0x7fffcf1e0700 (LWP 1367)] [New Thread 0x7fffce7df700 (LWP 1368)] [New Thread 0x7fffcddde700 (LWP 1370)] [New Thread 0x7fffcd3dd700 (LWP 1371)] [New Thread 0x7fffcc9dc700 (LWP 1372)] [New Thread 0x7fffcbfdb700 (LWP 1373)] [New Thread 0x7fffcb5da700 (LWP 1374)] [New Thread 0x7fffcabd9700 (LWP 1375)] [New Thread 0x7fffca1d8700 (LWP 1376)] [New Thread 0x7fffc97d7700 (LWP 1378)] [New Thread 0x7fffc8dd6700 (LWP 1381)] [New Thread 0x7fffc83d5700 (LWP 1383)] [New Thread 0x7fffc79d4700 (LWP 1384)] [New Thread 0x7fffc6fd3700 (LWP 1385)] [New Thread 0x7fffc65d2700 (LWP 1386)] [New Thread 0x7fffc5bd1700 (LWP 1387)] [New Thread 0x7fffc51d0700 (LWP 1388)] [New Thread 0x7fffc47cf700 (LWP 1389)] [New Thread 0x7fffc3dce700 (LWP 1390)] [New Thread 0x7fffc33cd700 (LWP 1391)] [New Thread 0x7fffc29cc700 (LWP 1393)] [New Thread 0x7fffc1fcb700 (LWP 1394)] [New Thread 0x7fffc15ca700 (LWP 1395)] [New Thread 0x7fffc0bc9700 (LWP 1396)] Program received signal SIGSEGV, Segmentation fault. 0x000000000042d9e7 in proxy_wait_for_reply (request=0x3ab0880, action=<value optimized out>) at process.c:2830 2830 FR_STATS_TYPE_INC(request->proxy_listener->stats.total_timeouts); Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-13.el6.x86_64 db4-4.7.25-16.el6.x86_64 glibc-2.12-1.47.el6_2.12.x86_64 keyutils-libs-1.4-3.el6.x86_64 krb5-libs-1.9-22.el6_2.1.x86_64 libcom_err-1.41.12-11.el6.x86_64 libselinux-2.0.94-5.2.el6.x86_64 nspr-4.8.9-3.el6_2.x86_64 nss-3.13.1-7.el6_2.x86_64 nss-softokn-freebl-3.12.9-11.el6.x86_64 nss-util-3.13.1-3.el6_2.x86_64 openldap-2.4.23-20.el6.x86_64 openssl-1.0.0-20.el6_2.5.x86_64 perl-5.10.1-119.el6_1.1.x86_64 perl-DBI-1.609-4.el6.x86_64 perl-libs-5.10.1-119.el6_1.1.x86_64 postgresql-libs-8.4.11-1.el6_2.x86_64 zlib-1.2.3-27.el6.x86_64 65 Thread 0x7fffc0bc9700 (LWP 1396) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 64 Thread 0x7fffc15ca700 (LWP 1395) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 63 Thread 0x7fffc1fcb700 (LWP 1394) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 62 Thread 0x7fffc29cc700 (LWP 1393) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 61 Thread 0x7fffc33cd700 (LWP 1391) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 60 Thread 0x7fffc3dce700 (LWP 1390) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 59 Thread 0x7fffc47cf700 (LWP 1389) 0x00007ffff757184d in connect () from /lib64/libpthread.so.0 58 Thread 0x7fffc51d0700 (LWP 1388) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 57 Thread 0x7fffc5bd1700 (LWP 1387) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 56 Thread 0x7fffc65d2700 (LWP 1386) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 55 Thread 0x7fffc6fd3700 (LWP 1385) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 54 Thread 0x7fffc79d4700 (LWP 1384) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 53 Thread 0x7fffc83d5700 (LWP 1383) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 52 Thread 0x7fffc8dd6700 (LWP 1381) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 51 Thread 0x7fffc97d7700 (LWP 1378) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 50 Thread 0x7fffca1d8700 (LWP 1376) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 49 Thread 0x7fffcabd9700 (LWP 1375) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 48 Thread 0x7fffcb5da700 (LWP 1374) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 47 Thread 0x7fffcbfdb700 (LWP 1373) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 46 Thread 0x7fffcc9dc700 (LWP 1372) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 45 Thread 0x7fffcd3dd700 (LWP 1371) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 44 Thread 0x7fffcddde700 (LWP 1370) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 43 Thread 0x7fffce7df700 (LWP 1368) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 42 Thread 0x7fffcf1e0700 (LWP 1367) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 41 Thread 0x7fffcfbe1700 (LWP 1366) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 40 Thread 0x7fffd05e2700 (LWP 1365) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 39 Thread 0x7fffd0fe3700 (LWP 1364) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 38 Thread 0x7fffd19e4700 (LWP 1363) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 37 Thread 0x7fffd23e5700 (LWP 1362) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 36 Thread 0x7fffd2de6700 (LWP 1361) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 35 Thread 0x7fffd37e7700 (LWP 1360) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 34 Thread 0x7fffd41e8700 (LWP 1359) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 33 Thread 0x7fffd4be9700 (LWP 1358) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 32 Thread 0x7fffd55ea700 (LWP 1357) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 31 Thread 0x7fffd5feb700 (LWP 1356) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 30 Thread 0x7fffd69ec700 (LWP 1355) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 29 Thread 0x7fffd73ed700 (LWP 1353) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 28 Thread 0x7fffd7dee700 (LWP 1352) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 27 Thread 0x7fffd87ef700 (LWP 1350) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 26 Thread 0x7fffd91f0700 (LWP 1349) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 25 Thread 0x7fffd9bf1700 (LWP 1348) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 24 Thread 0x7fffda5f2700 (LWP 1347) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 23 Thread 0x7fffdaff3700 (LWP 1346) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 22 Thread 0x7fffdb9f4700 (LWP 1345) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 21 Thread 0x7fffdc3f5700 (LWP 1344) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 20 Thread 0x7fffdcdf6700 (LWP 1343) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 19 Thread 0x7fffdd7f7700 (LWP 1342) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 18 Thread 0x7fffde1f8700 (LWP 1341) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 17 Thread 0x7fffdebf9700 (LWP 1340) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 16 Thread 0x7fffdf5fa700 (LWP 1339) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 15 Thread 0x7fffdfffb700 (LWP 1338) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 14 Thread 0x7fffe09fc700 (LWP 1337) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 13 Thread 0x7fffe13fd700 (LWP 1336) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 12 Thread 0x7fffe1dfe700 (LWP 1333) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 11 Thread 0x7fffe27ff700 (LWP 1332) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 10 Thread 0x7fffe3200700 (LWP 1330) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 9 Thread 0x7fffe3c01700 (LWP 1329) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 8 Thread 0x7fffe4602700 (LWP 1327) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 7 Thread 0x7fffe5003700 (LWP 1326) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 6 Thread 0x7fffe5a04700 (LWP 1325) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 5 Thread 0x7fffe6405700 (LWP 1324) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 4 Thread 0x7fffe6e06700 (LWP 1323) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 3 Thread 0x7fffe7807700 (LWP 1322) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 2 Thread 0x7fffe8208700 (LWP 1321) 0x00007ffff75706c0 in sem_wait () from /lib64/libpthread.so.0 * 1 Thread 0x7ffff7fea7c0 (LWP 1317) 0x000000000042d9e7 in proxy_wait_for_reply (request=0x3ab0880, action=<value optimized out>) at process.c:2830 Thanks Scott Armitage

1 0