Around this time, I was also seeing a lot of these errors in radius.log:
Error: rlm_sql (sql): There are no DB handles to use! skipped 0, tried to
connect 0
Is it possible this is related (it was unable to load a switch config from
the radius_nas table or something)? I had left the default num_sql_socks
set to 5 in /usr/local/raddb/sql.conf, and we are servicing several
thousand wireless clients for both authorization and authentication. I have
increased it to 30 and put PF back into production, waiting to see if it
fails again...
On Mon, Aug 26, 2013 at 12:02 PM, Fletcher Haynes <fhay...@willamette.edu>wrote:
> I think this might have something to do with it..I am receiving this error
> in the webservices_error_log within 1 second of the syntax errors in
> radius.log:
> [Mon Aug 26 10:59:23 2013] [error] [client 127.0.0.1] failed to resolve
> handler `pf::WebAPI': Can't use an undefined value as a HASH reference at
> /usr/local/pf/lib/pf/SwitchFactory.pm line 73.\nCompilation failed in
> require at /usr/local/pf/lib/pf/enforcement.pm line 43.\nBEGIN
> failed--compilation aborted at /usr/local/pf/lib/pf/enforcement.pm line
> 43.\nCompilation failed in require at /usr/local/pf/lib/pf/violation.pmline
> 73.\nBEGIN failed--compilation aborted at /usr/local/pf/lib/pf/
> violation.pm line 73.\nCompilation failed in require at
> /usr/local/pf/lib/pf/scan.pm line 39.\nBEGIN failed--compilation aborted
> at /usr/local/pf/lib/pf/scan.pm line 39.\nCompilation failed in require
> at /usr/local/pf/lib/pf/node.pm line 80.\nBEGIN failed--compilation
> aborted at /usr/local/pf/lib/pf/node.pm line 80.\nCompilation failed in
> require at /usr/local/pf/lib/pf/iplog.pm line 54.\nBEGIN
> failed--compilation aborted at /usr/local/pf/lib/pf/iplog.pm line
> 54.\nCompilation failed in require at /usr/local/pf/lib/pf/WebAPI.pm line
> 58.\nBEGIN failed--compilation aborted at /usr/local/pf/lib/pf/WebAPI.pm
> line 58.\nCompilation failed in require at (eval 294) line 2.\n
>
>
> On Mon, Aug 26, 2013 at 11:30 AM, Fletcher Haynes
> <fhay...@willamette.edu>wrote:
>
>> Slight update...
>>
>> This seems to be a fairly intermittent problem. I left PF out of
>> production for about 30 minutes, then put it back in to test, and now it is
>> handling requests fine. I am doing a packet capture to try to grab one of
>> the XML requests that causes it to die.
>>
>>
>> On Mon, Aug 26, 2013 at 10:16 AM, Fletcher Haynes <fhay...@willamette.edu
>> > wrote:
>>
>>> Hello again,
>>>
>>> I upgraded to 4.0.5-2 running on Ubuntu 12.04 in hopes of fixing the bug
>>> where the freeradius process dies randomly (I believe we were suffering
>>> from this bug:
>>> http://www.packetfence.org/bugs//bug_view_page.php?bug_id=1675&history=1).
>>> Unfortunately, the freeradius process still appears to be dying at random.
>>>
>>> I am receiving this error in the radius.log file:
>>>
>>> rlm_perl: perl_embed:: module = /usr/local/pf/raddb/packetfence.pm ,
>>> func = post_auth exit status= syntax error at line 1, column 49, byte 49
>>> at /usr/lib/perl5/XML/Parser.pm line 187.
>>>
>>> Here is the output from the FreeRADIUS debug:
>>>
>>> # Executing section authorize from file
>>> /usr/local/pf/raddb/sites-enabled/packetfence
>>> +- entering group authorize {...}
>>> [suffix] No '@' in User-Name = "84383551d8ae", looking up realm NULL
>>> [suffix] No such realm "NULL"
>>> ++[suffix] returns noop
>>> ++[preprocess] returns ok
>>> [eap] No EAP-Message, not doing EAP
>>> ++[eap] returns noop
>>> [files] users: Matched entry DEFAULT at line 1
>>> ++[files] returns ok
>>> ++[expiration] returns noop
>>> ++[logintime] returns noop
>>> rlm_perl: Added pair NAS-Port-Type = Wireless-802.11
>>> rlm_perl: Added pair Service-Type = Call-Check
>>> rlm_perl: Added pair Tunnel-Medium-Type = IEEE-802
>>> rlm_perl: Added pair Tunnel-Type = VLAN
>>> rlm_perl: Added pair Calling-Station-Id = 84:38:35:51:d8:ae
>>> rlm_perl: Added pair Called-Station-Id = 04:c5:a4:c3:bf:b0:BlitzNet
>>> rlm_perl: Added pair Airespace-Wlan-Id = 2
>>> rlm_perl: Added pair User-Name = 84383551d8ae
>>> rlm_perl: Added pair NAS-Identifier = WISM2_SDC
>>> rlm_perl: Added pair User-Password = 84383551d8ae
>>> rlm_perl: Added pair NAS-Port = 13
>>> rlm_perl: Added pair NAS-IP-Address = 158.104.249.7
>>> rlm_perl: Added pair Tunnel-Private-Group-Id = 260
>>> rlm_perl: Added pair Framed-MTU = 1300
>>> rlm_perl: Added pair Auth-Type = Accept
>>> ++[packetfence] returns noop
>>> Found Auth-Type = Accept
>>> Auth-Type = Accept, accepting the user
>>> Login OK: [84383551d8ae] (from client 158.104.249.7 port 13 cli
>>> 84:38:35:51:d8:ae)
>>> # Executing section post-auth from file
>>> /usr/local/pf/raddb/sites-enabled/packetfence
>>> +- entering group post-auth {...}
>>> ++[exec] returns noop
>>> ++? if (!EAP-Type || (EAP-Type != 21 && EAP-Type != 25))
>>> ? Evaluating !(EAP-Type ) -> TRUE
>>> ?? Skipping (EAP-Type != 21 )
>>> ?? Skipping (EAP-Type != 25)
>>> ++? if (!EAP-Type || (EAP-Type != 21 && EAP-Type != 25)) -> TRUE
>>> ++- entering if (!EAP-Type || (EAP-Type != 21 && EAP-Type != 25)) {...}
>>> rlm_perl: perl_embed:: module = /usr/local/pf/raddb/packetfence.pm ,
>>> func = post_auth exit status= syntax error at line 1, column 49, byte 49
>>> at /usr/lib/perl5/XML/Parser.pm line 187.
>>> Segmentation fault (core dumped)
>>>
>>> The packetfence.pm does contain the proper XML header that was the
>>> cause of this in the bug report. Here is the relevant part of
>>> packetfence.pm:
>>>
>>> my $response_body;
>>> $curl->setopt(CURLOPT_HEADER, 0);
>>> $curl->setopt(CURLOPT_URL, 'http://127.0.0.1:' . SOAP_PORT); #
>>> TODO: See note1
>>> # $curl->setopt(CURLOPT_URL, 'http://127.0.0.1:' .
>>> $Config{'ports'}{'soap'}); # TODO: See note1
>>> $curl->setopt(CURLOPT_HTTPHEADER, ['Content-Type: text/xml;
>>> charset=UTF-8']);
>>> $curl->setopt(CURLOPT_POSTFIELDS, $request);
>>> $curl->setopt(CURLOPT_WRITEDATA, \$response_body);
>>>
>>> libsoap-lite-perl version is: ii libsoap-lite-perl
>>> 1.0 Perl implementation of a SOAP client
>>> and server
>>>
>>> At this point, I have had to remove our PF install from production, as
>>> the radiusd process will not stay running.
>>>
>>> I would greatly appreciate any help on this!
>>>
>>> Thanks,
>>> --
>>> Fletcher Haynes <fhay...@willamette.edu>
>>> Systems Administrator/Network Services Consultant
>>> Willamette Integrated Technology Services
>>> Willamette University, Salem, OR
>>> Phone: 503.370.6016
>>>
>>
>>
>>
>> --
>> Fletcher Haynes <fhay...@willamette.edu>
>> Systems Administrator/Network Services Consultant
>> Willamette Integrated Technology Services
>> Willamette University, Salem, OR
>> Phone: 503.370.6016
>>
>
>
>
> --
> Fletcher Haynes <fhay...@willamette.edu>
> Systems Administrator/Network Services Consultant
> Willamette Integrated Technology Services
> Willamette University, Salem, OR
> Phone: 503.370.6016
>
--
Fletcher Haynes <fhay...@willamette.edu>
Systems Administrator/Network Services Consultant
Willamette Integrated Technology Services
Willamette University, Salem, OR
Phone: 503.370.6016
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
