<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Lyle Giese wrote:
<blockquote cite="mid:4C52313C.9060908@lcrcomputer.net" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
bruce bruce wrote:
<blockquote
cite="mid:AANLkTime+T5TTorg+qzjjOWedoNAMwv7Qu0yK69Y5SzR@mail.gmail.com"
type="cite">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.
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>But my main question remains why there are no activities on
24th
and 25th?</div>
<div><br>
</div>
<div><br>
</div>
<div>This is what I see in the /var/log/messages.1:</div>
<div><br>
</div>
<div>
<div>Jul 23 17:11:55 elastix last message repeated 20 times</div>
<div>Jul 23 17:22:51 elastix last message repeated 38 times</div>
<div>Jul 23 17:30:39 elastix last message repeated 26 times</div>
<div>Jul 23 17:30:39 elastix last message repeated 45 times</div>
<div>Jul 23 19:09:42 elastix ntpd[3113]: synchronized to
216.216.216.216, stratum 2</div>
<div>Jul 23 20:17:44 elastix ntpd[3113]: synchronized to
216.216.216.216, stratum 2</div>
<div>Jul 23 21:29:16 elastix dhclient: DHCPREQUEST on eth0 to
192.168.1.254 port 67</div>
<div>Jul 23 21:29:16 elastix dhclient: DHCPACK from 192.168.1.254</div>
<div>Jul 23 21:29:16 elastix dhclient: bound to 192.168.1.100 --
renewal in 37640 seconds.</div>
<div>Jul 26 09:22:37 elastix syslogd 1.4.1: restart.</div>
<div>Jul 26 09:22:37 elastix kernel: klogd 1.4.1, log source =
/proc/kmsg started.</div>
<div>Jul 26 09:22:37 elastix kernel: Linux version 2.6.18-164.el5 (<a
moz-do-not-send="true" href="mailto:mockbuild@builder16.centos.org"
target="_blank">mockbuild@builder16.centos.org</a>) (gcc version 4.1.2
20080704 (Red Hat 4.1.2-46)) #1 SMP Thu Se$</div>
<div>Jul 26 09:22:37 elastix kernel: BIOS-provided physical RAM map:</div>
</div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Bruce<br>
<br>
<div class="gmail_quote">On Thu, Jul 29, 2010 at 9:10 AM, Paul
Belanger <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:paul.belanger@polybeacon.com" target="_blank">paul.belanger@polybeacon.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Wed, Jul 28, 2010 at 9:06 PM, bruce bruce <<a
moz-do-not-send="true" href="mailto:bruceb444@gmail.com"
target="_blank">bruceb444@gmail.com</a>> wrote:<br>
</div>
<div>> See the jump from Jul 23rd to Jul 26th. Is this an
indication of Asterisk<br>
> being down?<br>
><br>
</div>
No, it just means there was no logger activity for those days. You<br>
need to add a monitoring solution to your Asterisk box (IE: AMI:<br>
Ping).<br>
<br>
--<br>
Paul Belanger | dCAP<br>
Polybeacon | Consultant<br>
Jabber: <a moz-do-not-send="true"
href="mailto:paul.belanger@polybeacon.com" target="_blank">paul.belanger@polybeacon.com</a>
| IRC: pabelanger (Freenode)<br>
<a moz-do-not-send="true" href="http://blog.polybeacon.com"
target="_blank">blog.polybeacon.com</a><br>
<font color="#888888"><br>
--<br>
</font></blockquote>
</div>
</div>
</blockquote>
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. <br>
<br>
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.<br>
<br>
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.<br>
<br>
Lyle Giese<br>
LCR Computer Services, Inc.<br>
<br>
</blockquote>
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.<br>
<br>
Lyle Giese<br>
LCR Computer Services, Inc.<br>
<br>
</body>
</html>