Anyone seen this one so far? Seems to happen in or outgoing, and even if I just pick up the channel. 09/15 revision works fine, but the 10/31 checkout is doing this instantly. All with HEAD zaptel and libpri Oh and another off topic thing. Sometimes I have a way of forgetting I have asterisk running, and do a module unload. As you can expect, this causes an EIP and kills the server. The server will then stay stuck at the EIP, but does anyone know of a way to do an auto-reboot? Or shouldn't the zaptel channel module not be unloadable while asterisk is running? Sure I know it's my fault if I do this by accident, but fortunately the server is only 45 mins away. Would be rough in another state to make that mistake :) Asterisk Ready. *CLI> -- Starting simple switch on 'Zap/28-1' Ouch ... error while writing audio data: : Broken pipe Warning, flexibel rate not heavily tested! Segmentation fault Greg
> Anyone seen this one so far? Seems to happen in or outgoing, and even > if I just pick up the channel.Nope. cvs-head from yesterday and the last several days are working just fine on fc3. What distro are you using?> 09/15 revision works fine, but the 10/31 checkout is doing this > instantly. All with HEAD zaptel and libpri > > Oh and another off topic thing. > > Sometimes I have a way of forgetting I have asterisk running, and do a > module unload. As you can expect, this causes an EIP and kills the > server. The server will then stay stuck at the EIP, but does anyone > know of a way to do an auto-reboot? Or shouldn't the zaptel channel > module not be unloadable while asterisk is running? Sure I know it's my > fault if I do this by accident, but fortunately the server is only 45 > mins away. Would be rough in another state to make that mistake :)kernel modules should not be unloaded. The fix for that is remedial training on behalf of the sys admin (you).> Asterisk Ready. > *CLI> -- Starting simple switch on 'Zap/28-1' > Ouch ... error while writing audio data: : Broken pipe > Warning, flexibel rate not heavily tested! > Segmentation faultThe above generally means you've got something very wrong in your /etc/zaptel.conf or /etc/asterisk/zapata.conf definitions. Best guess is the zap channels defined in zaptel.conf don't match those defined in zapata.conf.
On Monday 31 October 2005 05:11, gw@adcomcorp.com wrote:> Sometimes I have a way of forgetting I have asterisk running, and do a > module unload. As you can expect, this causes an EIP and kills the > server. The server will then stay stuck at the EIP, but does anyone > know of a way to do an auto-reboot? Or shouldn't the zaptel channel > module not be unloadable while asterisk is running? Sure I know it's my > fault if I do this by accident, but fortunately the server is only 45 > mins away. Would be rough in another state to make that mistake :)...?? root@ben-ast:~# rmmod wct4xxp ERROR: Module wct4xxp is in use root@ben-ast:~# rmmod zaptel ERROR: Module zaptel is in use by wct4xxp I can't remove them when Asterisk is running. What distro? lsmod should show a nonzero "use" count for your zaptel and lowlevel hardware driver. -A.
Hello Rich, I will work with this a bit more, however it only seems to happen on the newer code. Went up to 10/25 with no problems. Yes I know about module unloading, :). Greg -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Rich Adamson Sent: Monday, October 31, 2005 8:31 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Segfault on latest head 10/31> Anyone seen this one so far? Seems to happen in or outgoing, and even> if I just pick up the channel.Nope. cvs-head from yesterday and the last several days are working just fine on fc3. What distro are you using?> 09/15 revision works fine, but the 10/31 checkout is doing this > instantly. All with HEAD zaptel and libpri > > Oh and another off topic thing. > > Sometimes I have a way of forgetting I have asterisk running, and do a> module unload. As you can expect, this causes an EIP and kills the > server. The server will then stay stuck at the EIP, but does anyone > know of a way to do an auto-reboot? Or shouldn't the zaptel channel > module not be unloadable while asterisk is running? Sure I know it's > my fault if I do this by accident, but fortunately the server is only > 45 mins away. Would be rough in another state to make that mistake :)kernel modules should not be unloaded. The fix for that is remedial training on behalf of the sys admin (you).> Asterisk Ready. > *CLI> -- Starting simple switch on 'Zap/28-1' > Ouch ... error while writing audio data: : Broken pipe Warning, > flexibel rate not heavily tested! > Segmentation faultThe above generally means you've got something very wrong in your /etc/zaptel.conf or /etc/asterisk/zapata.conf definitions. Best guess is the zap channels defined in zaptel.conf don't match those defined in zapata.conf. _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
I am on Debian testing. Using this script: rmmod wctdm rmmod wcfxo rmmod wct4xxp rmmod zaptel modprobe zaptel modprobe wct4xxp modprobe wcfxo modprobe wctdm wctdm 41536 0 wcfxo 13344 0 wct4xxp 104128 30 zaptel 163844 73 wctdm,wcfxo,wct4xxp Greg -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Andrew Kohlsmith Sent: Monday, October 31, 2005 9:10 AM To: asterisk-users@lists.digium.com Subject: Re: [Asterisk-Users] Segfault on latest head 10/31 On Monday 31 October 2005 05:11, gw@adcomcorp.com wrote:> Sometimes I have a way of forgetting I have asterisk running, and do a> module unload. As you can expect, this causes an EIP and kills the > server. The server will then stay stuck at the EIP, but does anyone > know of a way to do an auto-reboot? Or shouldn't the zaptel channel > module not be unloadable while asterisk is running? Sure I know it's > my fault if I do this by accident, but fortunately the server is only > 45 mins away. Would be rough in another state to make that mistake :)...?? root@ben-ast:~# rmmod wct4xxp ERROR: Module wct4xxp is in use root@ben-ast:~# rmmod zaptel ERROR: Module zaptel is in use by wct4xxp I can't remove them when Asterisk is running. What distro? lsmod should show a nonzero "use" count for your zaptel and lowlevel hardware driver. -A. _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users