asterisk users - Feb 2010 - asterisk sudden restart - 1.4.18.1 - Resolved after upgrade to 1.4.22.1

Hi Leif,

Thanks for the information. I checked the /tmp/ folder and there was core
#### files and I tried to back trace it but it was not showing the cause of
that crash, but anyhow, I upgraded our Asterisk system to 1.4.22.1 and from
past few days its going on fine. I have also researched and found that
version 1.4.17/18.1 had the issue of channel stuck up as well as random
asterisk crashes.

Regards
Sandesh



On Thu, Feb 11, 2010 at 6:29 AM, Leif Madsen
<leif.madsen at asteriskdocs.org>wrote:
> das sandesh wrote:
> > Hi,
> >
> > Asterisk got stopped this morning after 20 minutes and phones went to
> > 'No Service' and then got started automatically after 20 min,
as I could
> > see in the full log that asterisk got started at so and so time:
> > [Feb 10 08:29:31] VERBOSE[31013] logger.c: Asterisk Event Logger
Started
> > /var/log/asterisk/event_log
> > [Feb 10 08:29:31] VERBOSE[31013] logger.c: Asterisk Dynamic Loader
> Starting:
> >
> > But I am trying to find why did it stopped (and there was no record of
> > asterisk stopped?) and then get restarted.....In the log I could also
see
> :
> >
> > [Feb 10 08:02:05] VERBOSE[7027] logger.c:     -- Incoming call: Got
SIP
> > response 500 "CSeq Number Out of order" back from
192.168.10.16
> > [Feb 10 08:02:05] VERBOSE[7027] logger.c:     -- Incoming call: Got
SIP
> > response 500 "CSeq Number Out of order" back from
192.168.10.16
> > [Feb 10 08:02:05] VERBOSE[7027] logger.c:     -- Incoming call: Got
SIP
> > response 500 "CSeq Number Out of order" back from
192.168.10.16
> > [Feb 10 08:02:08] VERBOSE[7004] logger.c:     -- Remote UNIX
connection
> > [Feb 10 08:02:08] VERBOSE[28272] logger.c:     -- Remote UNIX
connection
> > disconnected
> >
> > During this period (from 8:02 till 8:29) all the phones went to
'No
> > Service'....I checked all the logs and could not find any reason
why it
> > was down or any log that shows asterisk was down at that
point......any
> > ideas are appreciated...
>
> Check /tmp/ as there may be a core.##### file there which you could
> generate a
> backtrace from to determine the issue (if you're able to understand
what is
> outputs :))
>
> At the least, if such a core file exists, then you could line it up with
> the
> time to see if that was indeed the case. If there is a core file, it means
> something caused Asterisk to crash.
>
> > Asterisk version: 1.4.18.1
>
> This version is quite old, and if the issue was a crash that brought the
> system
> down momentarily, it is possible this issue may already be resolved.
>
> Leif!
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100219/694fdb3e/attachment.htm