That was the entire output of the freeradius -X command. All it gave me in
the radiusd log was Logon failed.
However, I just finished rebuilding the server from scratch, and it is
working fine now. Still not sure what happened. Thank you for your help!
On Thu, Jun 27, 2013 at 8:43 AM, Francois Gaudreault <
[email protected]> wrote:
> On 2013-06-27 10:57 AM, Fletcher Haynes wrote:
> > Francois: There is nothing in packetfence.log, nor any other log file
> > I can find. It never seems to make it past FreeRadius.
> Nothing in the radius logs either?
>
> There are two ways to see the 'fail' message:
> - Trigger the invalid_answer_handler sub
> - Trigger the server_error_handler sub
>
> In both cases, there should be some bits in the radiusd log.
>
> --
> Francois Gaudreault
> Architecte de Solution Cloud | Cloud Solutions Architect
> [email protected]
> 514-629-6775
> - - -
> CloudOps
> 420 rue Guy
> Montréal QC H3J 1S6
> www.cloudops.com
> @CloudOps_
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
--
Fletcher Haynes <[email protected]>
Systems Administrator/Network Services Consultant
Willamette Integrated Technology Services
Willamette University, Salem, OR
Phone: 503.370.6016
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
