Hi Jeff,
the LO interface issue is really strange - I cannot imagine a relation
between the LO interface and the shutdown interfaceattaching with
gdb to a running process is as simple as accessing a core file gdb
bin_file pid
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
Hi Bogdan,
You're right, localhost doesn't seem to have anything to do with it. In
fact, I can't reproduce this problem anymore. One difference is now I'm
using DBG_QM_MALLOC instead of F_MALLOC to troubleshoot the other memory
issue.
Now, instead of leaving processes running after shutdown,
Hi Jeff,
Have you tried to attach with gdb to the remaining process and to get a
backtrace ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 11/12/2013 06:03 AM, Jeff Pyle wrote:
Hello,
In one particular configuration on 1.10 a standard
Hi Bogdan,
I had not, that's a new concept for me. I'll see what I can do. Changing
from localhost to LAN IPs did solve the problem of processes not shutting
down properly, however. Just the already freed memory
crashhttps://github.com/OpenSIPS/opensips/issues/126remains.
- Jeff
On Thu,
I think I've made some progress. It has something to do with using
127.0.0.1 as an interface. This instance talked only to other OS instances
on the same machine, so localhost seemed like a natural and portable
choice. Unfortunately it causes some problems possibly with the
check_ip_address
Enable core dumps on the machine and get a backtrace:
http://www.opensips.org/Documentation/TroubleShooting-Crash
Regards,
Ovidiu Sas
On Tue, Nov 12, 2013 at 7:07 PM, Jeff Pyle jp...@fidelityvoice.com wrote:
I think I've made some progress. It has something to do with using
127.0.0.1 as an
Hello,
In one particular configuration on 1.10 a standard Opensips shutdown isn't
ending all the processes...if calls have passed through the system. If no
calls have passed, everything shuts down fine.
At one particular moment in time with everything running I have:
Process:: ID=0 PID=26283
