Hi, I have a problem stopping a openser daemon (1.1.0)
Does this gdb connected to the remaining child say anything?
(gdb) bt #0 0x0000000000456743 in fm_status (qm=0x5eca60) at mem/f_malloc.c:515 #1 0x000000000041f172 in sig_usr (signo=Variable "signo" is not available. ) at main.c:571 #2 <signal handler called> #3 0x0000003fbf5c72ee in __recvfrom_nocancel () from /lib64/tls/libc.so.6 #4 0x000000000044f286 in udp_rcv_loop () at udp_server.c:415 #5 0x000000000041f7f4 in main_loop () at main.c:925 #6 0x0000000000420446 in main (argc=Variable "argc" is not available. ) at main.c:1477
br hw
Hi Helge,
could you check with top the cpu usage? it looks like the main process is stuck into generating the memory status.
regards, bogdan
Helge Waastad wrote:
Hi, I have a problem stopping a openser daemon (1.1.0)
Does this gdb connected to the remaining child say anything?
(gdb) bt #0 0x0000000000456743 in fm_status (qm=0x5eca60) at mem/f_malloc.c:515 #1 0x000000000041f172 in sig_usr (signo=Variable "signo" is not available. ) at main.c:571 #2 <signal handler called> #3 0x0000003fbf5c72ee in __recvfrom_nocancel () from /lib64/tls/libc.so.6 #4 0x000000000044f286 in udp_rcv_loop () at udp_server.c:415 #5 0x000000000041f7f4 in main_loop () at main.c:925 #6 0x0000000000420446 in main (argc=Variable "argc" is not available. ) at main.c:1477
br hw
Hi, You're correct.
The main process is running 100% CPU...
The outcome of this is that I've disabled memlog in my configuration.
Do you have a clue why this happens?
br hw
tor, 14,.09.2006 kl. 12.50 +0300, skrev Bogdan-Andrei Iancu:
Hi Helge,
could you check with top the cpu usage? it looks like the main process is stuck into generating the memory status.
regards, bogdan
Helge Waastad wrote:
Hi, I have a problem stopping a openser daemon (1.1.0)
Does this gdb connected to the remaining child say anything?
(gdb) bt #0 0x0000000000456743 in fm_status (qm=0x5eca60) at mem/f_malloc.c:515 #1 0x000000000041f172 in sig_usr (signo=Variable "signo" is not available. ) at main.c:571 #2 <signal handler called> #3 0x0000003fbf5c72ee in __recvfrom_nocancel () from /lib64/tls/libc.so.6 #4 0x000000000044f286 in udp_rcv_loop () at udp_server.c:415 #5 0x000000000041f7f4 in main_loop () at main.c:925 #6 0x0000000000420446 in main (argc=Variable "argc" is not available. ) at main.c:1477
br hw
for sure the problem is related to a bogus mem operation; so you need to enable the memory debug support and run the proxy to try to catch the bug.
regards, bogdan
Helge Waastad wrote:
Hi, You're correct.
The main process is running 100% CPU...
The outcome of this is that I've disabled memlog in my configuration.
Do you have a clue why this happens?
br hw
tor, 14,.09.2006 kl. 12.50 +0300, skrev Bogdan-Andrei Iancu:
Hi Helge,
could you check with top the cpu usage? it looks like the main process is stuck into generating the memory status.
regards, bogdan
Helge Waastad wrote:
Hi, I have a problem stopping a openser daemon (1.1.0)
Does this gdb connected to the remaining child say anything?
(gdb) bt #0 0x0000000000456743 in fm_status (qm=0x5eca60) at mem/f_malloc.c:515 #1 0x000000000041f172 in sig_usr (signo=Variable "signo" is not available. ) at main.c:571 #2 <signal handler called> #3 0x0000003fbf5c72ee in __recvfrom_nocancel ()
from /lib64/tls/libc.so.6
#4 0x000000000044f286 in udp_rcv_loop () at udp_server.c:415 #5 0x000000000041f7f4 in main_loop () at main.c:925 #6 0x0000000000420446 in main (argc=Variable "argc" is not available. ) at main.c:1477
br hw