FreeRadius 2.1.8 works fine in DEBUG mode

[Amal Janardhanan]

If I don't include in import statement from python it works well.

Just any import like import socket, it fails...

A plain Python code works.

Here is the thread sample.

Sampling process 88764 for 3 seconds with 1 millisecond of run time  
between samples
Sampling completed, processing symbols...
Analysis of sampling radiusd (pid 88764) every 1 millisecond
Call graph:
     2378 Thread_2507
       2378 start
         2378 main
           2378 radius_event_process
             2378 select$DARWIN_EXTSN
               2378 select$DARWIN_EXTSN
     2378 Thread_2603
       2378 thread_start
         2378 _pthread_start
           2378 request_handler_thread
             2378 radius_handle_request
               2378 rad_authenticate
                 2378 module_authorize
                   2378 indexed_modcall
                     2378 modcall
                       2378 python_function
                         2378 PyGILState_Ensure
                           2378 PyEval_RestoreThread
                             2378 PyThread_acquire_lock
                               2378 pthread_cond_wait$UNIX2003
                                 2378 __semwait_signal
                                   2378 __semwait_signal

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
         __semwait_signal        2378
         select$DARWIN_EXTSN        2378
Sample analysis of process 88764 written to file /dev/stdout



On Feb 11, 2010, at 1:04 AM, Alan DeKok wrote:

> Amal Janardhanan wrote:
>>    I tried debugging by radiusd -fxx -l stdout.
>>
>> But no information is printed in the window nor in any of the file.
>>
>> I tried various radius version from 2.1.1 to 2.1.8. Same result  
>> everywhere.
>
>  Those command line options should cause it to print it's starting
> messages to the terminal.  Since nothing is being printed, it's not  
> even
> starting.
>
>  My *guess* is that either you do not have permission to run the
> radiusd binary, *or* there is some "security" policy on your system  
> that
> prevents it from running a newer version of FreeRADIUS.
>
>  i.e. go find out why your system won't let you run executables.  This
> isn't a freeradius problem.
>
>  Alan DeKok.
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html