[asterisk-users] Asterisk stopped after Internet connection dropped ?! Asterisk 1.4.26.1

[Lyle Giese]

Lyle Giese wrote:
> bruce bruce wrote:
>> I am not sure why it would be sleeping. I have never dealt with
>> putting a linux server to sleep. It is connected to a UPS, but I
>> don't think it has been put to sleep by the UPS as the USB cable from
>> UPS is not connected to it.
>>
>> Can you please elaborate on what you mean by AMI:Ping? Is there a
>> service that you recommand that does this or are there any opensource
>> monitoring tools out there that I can use?
>>
>> But my main question remains why there are no activities on 24th and
>> 25th?
>>
>>
>> This is what I see in the /var/log/messages.1:
>>
>> Jul 23 17:11:55 elastix last message repeated 20 times
>> Jul 23 17:22:51 elastix last message repeated 38 times
>> Jul 23 17:30:39 elastix last message repeated 26 times
>> Jul 23 17:30:39 elastix last message repeated 45 times
>> Jul 23 19:09:42 elastix ntpd[3113]: synchronized to 216.216.216.216,
>> stratum 2
>> Jul 23 20:17:44 elastix ntpd[3113]: synchronized to 216.216.216.216,
>> stratum 2
>> Jul 23 21:29:16 elastix dhclient: DHCPREQUEST on eth0 to
>> 192.168.1.254 port 67
>> Jul 23 21:29:16 elastix dhclient: DHCPACK from 192.168.1.254
>> Jul 23 21:29:16 elastix dhclient: bound to 192.168.1.100 -- renewal
>> in 37640 seconds.
>> Jul 26 09:22:37 elastix syslogd 1.4.1: restart.
>> Jul 26 09:22:37 elastix kernel: klogd 1.4.1, log source = /proc/kmsg
>> started.
>> Jul 26 09:22:37 elastix kernel: Linux version 2.6.18-164.el5
>> (mockbuild at builder16.centos.org
>> <mailto:mockbuild at builder16.centos.org>) (gcc version 4.1.2 20080704
>> (Red Hat 4.1.2-46)) #1 SMP Thu Se$
>> Jul 26 09:22:37 elastix kernel: BIOS-provided physical RAM map:
>>
>> Morning of the 26th at 9:22 the server was restarted because it was
>> un-reachable from outside and hence the restart log but where is the
>> 24th, and 25th?
>>
>> Thanks,
>> Bruce
>>
>> On Thu, Jul 29, 2010 at 9:10 AM, Paul Belanger
>> <paul.belanger at polybeacon.com <mailto:paul.belanger at polybeacon.com>>
>> wrote:
>>
>>     On Wed, Jul 28, 2010 at 9:06 PM, bruce bruce <bruceb444 at gmail.com
>>     <mailto:bruceb444 at gmail.com>> wrote:
>>     > See the jump from Jul 23rd to Jul 26th. Is this an indication
>>     of Asterisk
>>     > being down?
>>     >
>>     No, it just means there was no logger activity for those days.  You
>>     need to add a monitoring solution to your Asterisk box (IE: AMI:
>>     Ping).
>>
>>     --
>>     Paul Belanger | dCAP
>>     Polybeacon | Consultant
>>     Jabber: paul.belanger at polybeacon.com
>>     <mailto:paul.belanger at polybeacon.com> | IRC: pabelanger (Freenode)
>>     blog.polybeacon.com <http://blog.polybeacon.com>
>>
>>     --
>>
> It's 'well known' that Asterisk gets confused and runs around in a
> very tight loop when DNS resolution is failing.  Asterisk does a lot
> of DNS queries and when the Internet goes down, that puts Asterisk
> into a loop. 
>
> Depending on your machine, I am guessing that Asterisk locked up or
> dropped out on the 23rd and the restart on the 26th brought it back to
> life.
>
> Nagios is a good choice for monitoring servers and services.  I use it
> here to monitor all the servers and SIP on my Asterisk box.
>
> Lyle Giese
> LCR Computer Services, Inc.
>
While the above comment about DNS holds, I also realized that most
likely your Asterisk machine lost it's only ip address when the DSL went
down.  That may also have caused Asterisk to exit.  I think most(if not
all) admins here would never have a dynamic ip address on an Asterisk
server.

Lyle Giese
LCR Computer Services, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100729/00924b56/attachment.htm