Hi Kanakatti.
do you have the "time_to_kill" parameter set to a non-null value into
"exec" module? if so, can you retry your tests with this parameter set
to zero?
Just to reduce the search zone......
regards,
bogdan
Daniel-Constantin Mierla wrote:
Could you give the list with loaded modules? It seems that it blocks
in one of the used modules. Also, please keep the coredump and the
sources, they may be usefully if we cannot target quickly the issue.
Daniel
On 08/19/05 20:58, Kanakatti Mahesh Subramanya wrote:
Trying openser-head, and have noticed that after an hour or so of
heavy usage, it just stops responding to incoming requests. The only
way out is to kill it, and restart
a backtrace on the resulting core shows
#0 destroy_kill () at fastlock.h:76
76 fastlock.h: No such file or directory.
in fastlock.h
(gdb) bt
#0 destroy_kill () at fastlock.h:76
#1 0xb7d1dc7a in exec_shutdown () at exec_mod.c:92
#2 0x08078502 in destroy_modules () at sr_module.c:355
#3 0x0805fb5d in cleanup (show_status=0) at main.c:351
#4 0x080614ea in main (argc=0, argv=0xb7fb9800) at main.c:1580
Something obvious out of whack?
cheers
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
