asterisk users - Jun 2005 - Inactivity restart segmentation fault

Hi all,

for an unknown reason, I find my asterisk server down every morning as
a result of failing to restart during the night because of a
segmentation fault. The error message is as follows:

Waiting for inactivity to perform restart...
Executing last minute cleanups
  == Destroying any remaining musiconhold processes
Asterisk cleanly ending (0).
     -- Remote UNIX connection
Waiting for inactivity to perform restart...
Segmentation fault

Any idea what causes the segmentation fault? Why does * have to
restart after a prolonged period of inactivity and how can I stop
this?

I'm running * version 1.0.7 on Debian Woody with Digium TDM11B
hardware installed. I will appreciate whatever help I'll get on
resolving the problem.

-- 
Thanks and regards,
Alphonse Ogulla
Nairobi, Kenya

On 6/3/05, Alphonse Ogulla <aogulla@gmail.com>
wrote:
> Hi all,
> 
> for an unknown reason, I find my asterisk server down every morning as
> a result of failing to restart during the night because of a
> segmentation fault. The error message is as follows:
> 
> Waiting for inactivity to perform restart...
> Executing last minute cleanups
>  == Destroying any remaining musiconhold processes
> Asterisk cleanly ending (0).
>     -- Remote UNIX connection
> Waiting for inactivity to perform restart...
> Segmentation fault
> 
> Any idea what causes the segmentation fault? Why does * have to
> restart after a prolonged period of inactivity and how can I stop
> this?
> 
> I'm running * version 1.0.7 on Debian Woody with Digium TDM11B
> hardware installed. I will appreciate whatever help I'll get on
> resolving the problem.
> 
When I start asterisk with # asterisk -vvvc all works well. But when *
attempts to restart on its own after waiting for inactivity, then I
get the error above. Is the problem to do with /etc/init.d/asterisk
start script?

-- 
Regards,
Alphonse Ogulla
Nairobi, Kenya

On 6/14/05, Tzafrir Cohen <tzafrir@cohens.org.il>
wrote:
> Hi
> 
> Has this been resolved?
> 
Not as such but I noticed I get the error only when I run asterisk in
the foreground with the arguments -vvvc.

However I get no segfault error when asterisk restarts when running in
the background.

So in short, I do asterisk & then asterisk -vvvr to connect to the
running server. This way there is no segfault.

--
Rgds,
Alphonse Ogulla
Nairobi, Kenya