Hi
I'm not used to work to work with gdb. I've installed it to my host.
From this point I don't understand how to do what you're recommending because as I said when I start my openser with the auth.so module loaded, there is no running process. So I can't attach gdb to anything...
Could you be more precise in how I should A) ?
Regards,
Pascal
Hi Pascal,
This is strange as it looks like your openser blocks in rand() function......AFAIK this function should not block at all....
To clarify this a bit, you can do 2 things:
A) once blocked, attach with gdb and get a trace of the process
B) run openser in strace (with fork support) and watch the output....
Regards,
Bogdan
Pascal Maugeri wrote:
Hi,
I have a fresh checkout of openser 1.3.0. <http://1.3.0.> I believe it gave the same problem using 1.3.1. <http://1.3.1.>Apr 2 16:10:36 vpngw openser: Iniciación de openser succeeded
I don't see any core file in my working directory.
These are the last lines of my log file:
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] DBG:uri_db:mod_init: uri_db - initializing
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] DBG:core:init_mod: initializing module xlog
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:xlog:mod_init: initializing...
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] DBG:core:init_mod: initializing module acc
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:acc:mod_init: initializing...
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] DBG:core:find_cmd_export_t: found <load_tm>(0) in module tm [/usr/local/lib/openser/modules/]
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] DBG:core:init_mod: initializing module auth
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:auth:mod_init: initializing...
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] DBG:core:find_cmd_export_t: found <load_sl>(0) in module sl [/usr/local/lib/openser/modules/]
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:auth:mod_init: SL API loaded
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:auth:generate_random_secret: (1)
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:auth:generate_random_secret: (2)
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:auth:generate_random_secret: (3)
Apr 2 16:10:36 vpngw openser: Apr 2 16:10:34 [16079] INFO:auth:generate_random_secret: (3a)
Remember that the last lines "generate_random_secret" ( (1)...(3a) ) are the ones that I have added to spot where the problem.
Also it ends with a "... openser succeeded" there is no running openser processus ?!
Thanks for your help.
Pascal
------------------------------------------------------------------------On Wed, Apr 2, 2008 at 2:50 PM, Henning Westerholt <henning.westerholt@1und1.de <mailto:henning.westerholt@1und1.de>> wrote:
On Wednesday 02 April 2008, Pascal Maugeri wrote:
> [..]
> 2) when I remove the configuration parameter "secret", the
auth_mod.c calls
> the method generate_random_secret() as stated in the
documentation. It
> enters in the loop
>
> for(i = 0; i < RAND_SECRET_LEN; i++) {
> LM_INFO("(3a)\n");
> sec_rand[i] = 32 + (int)(95.0 * rand() /
(RAND_MAX + 1.0));
> }
> LM_INFO("(4)\n");
>
> but never exit ! This is the reason why my server does not start
and keeps
> blocked there. I modified the code above to print more logs, I
can see in
> the logs the string (3a) once but I never (4): IMHO it is
blocked somewhere
> in the first random computation.
>
> I'm running openser on Redhat Enterprise v4.
>
> Is there anything else I should configure in my environment ? Or
I found a
> bug ?
Hi Pascal,
i just tested it, it works fine on my system. Without a secret
parameter
(which probably most people uses), its autogenerated. What version
of openser
do you use? Do you get a core file (in the working directory)/
observed a
crash on startup? Could you please post the last lines debug log
of the
startup?
Cheers,
Henning
_______________________________________________
Users mailing list
Users@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users