Rich, > Far too many variables for anyone to even guess at the root cause. Problem > could be related to slight differences in o/s libraries between systems, > coding problems within asterisk, etc. You 're right, it could be every thing....
> There were some issues reported with cvs head in January relative to hangs, > etc. Are they reported in the bugtracker, or in the mailing list? > Might consider changing /etc/asterisk/logger.conf and add debug to the list. > Then after a failure, at least look at /var/log/asterisk/debug messages. Yes, this was the first thing, I did after the crash showed up. I simply forgot to enable it, since this production server ran long time without problems. But now, following murphy's law, the next crash will never happen ;-) > For additional info, I'd suggest compiling the code on one of thse machines > to see if it complains about missing/inappropriate items. After these machines were setup, we compiled new code on every machine, since we started with an older version of Asterisk in November 2004. The compiling of asterisk did not show me any relevant (?) errors. But I remember there were some statements (Warnings) in the console output of the make process, I didn't understand. Is this output logged in addition to the console in a logfile somewhere? If so, one could examine this output and hopefully get some hints... Thanks for your help Guido Hecken _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
