On Thu, 2004-04-15 at 18:53, Federico Alves wrote:
My single client is in production and every few minutes Asterisk dies, and somebody has to restart it manually. I tried to use DJB's Daemontools to start and run asterisk, but it does not work for Red Hat 9.0. The “safe_asterisk” fails to work either because the “daemon” command is unrecognized. The question is: is there any way to see what module is the culprit for the instability? How do I make it stable? Sorry for being new to Linux.
Well first you MUST get a core, or at the minimal read the error message.
Once you have a core file, you can do a backtrace and find out where it crashed.
It is always useful to audit your needs and turn off anything you are not using. Remember things like the SIP bug about 9 months ago, I didn't have to worry about it as I wasn't running SIP and had it in the noload list.
My guess is that if you didn't know any of the things I said and/or
didn't know how to do preliminary debugging on your own, you had no
business being in business yet. Do your client a favor and refer them
off to someone who knows what they are doing. When you learn enough,
re-enter the marketplace and watch your clients be much happier with
you.
It is my experience that core files are next to useless for debugging multi threaded applications like *
_______________________________________________ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
