On Wed, Jul 28, 2010 at 9:06 PM, bruce bruce bruceb...@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:
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
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
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
This was a static IP. Further checks into the server prevails that there are
no logs of what happened on the 24th and 25th even in /var/log/messages.
This makes me believe that a hardware lockup has happened and according to
people on CentOS forum this is VERY HARD to diagnose as there will be no
Hi Everyone,
This is probably more related to Linux than to Asterisk. Analogue channels
on a system were un-responsive on Monday morning. Apparently something
happened over the weekend and the router went off or it lost it's DSL
connection.
[Jul 23 22:50:01] VERBOSE[12437] logger.c: --
On Wed, Jul 28, 2010 at 6:06 PM, bruce bruce bruceb...@gmail.com wrote:
Hi Everyone,
This is probably more related to Linux than to Asterisk. Analogue channels on
a system were un-responsive on Monday morning. Apparently something happened
over the weekend and the router went off or it lost
