On Thu, Aug 03, 2006 at 11:26:04AM -0400, Xavier Douville wrote: > Package: asterisk > Version: 1:1.2.7.1.dfsg-3 > Severity: important > > If asterisk is configured to use a zap channel, and the zaptel module is > not loaded (with udev it also means that /dev/zap doesn't exist) my whole > system crashes about 3 seconds later. I can still ping it but I can't > ssh to it, and the local console is frozen too. > This occurs each time I upgrade the kernel and reboot.
Can you connect with the manager interface? port 5038 (make sure it's set to listen on all interfaces first). If so: asterisk is still running. See below. If not: probably some sort of kernel panic that somehow left the networking stack in tact. Assuming the former: What you describe seems to be asterisk using 100% CPU. In the default configuration of the package asterisk runs with -p for "real-time" scheduling priority. Edit /etc/asterisk/default and set there 'AST_REALTIME=no' . This should allow you to at least get a system that is functioning. -- Tzafrir Cohen sip:[EMAIL PROTECTED] icq#16849755 iax:[EMAIL PROTECTED] +972-50-7952406 jabber:[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.xorcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
