[Asterisk-Users] Segfault on latest head 10/31

[Rich Adamson]

> 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 fault    

The 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.