ok so i found that the system did rebooted without notification. Any ideas what could be causing this issue?
Please see attached at my messages log. Also note the date. I think the issue might be that my Alix might be at its last stand. :( On Thu, Sep 29, 2011 at 1:11 PM, Fernando Fuentes <digitaldis...@gmail.com>wrote: > Ok so far 2+ days of uptime and all calls are there. Looks like I had a > time issue. > > Thank you guys for the help. > > > On Tue, Sep 27, 2011 at 12:55 PM, Fernando Fuentes < > digitaldis...@gmail.com> wrote: > >> Michael, >> >> Thanks for the tip. Ok so the kill process caused the email to trigger and >> for the service "asterisk" to re spawn. so that is working just fine. what I >> am wondering now is... what would be causing my call processed to clear..... >> I did notice a lot of issues with ntpd drifting and unable to sync. Could >> this be causing some sore of issue where the ami is not seen the correct >> time sync causing to calls to be cleared? I even saw that at some point my >> system date was Dec 31.... >> >> >> On Tue, Sep 27, 2011 at 12:42 PM, Michael Keuter >> <li...@mksolutions.info>wrote: >> >>> Am 27.09.2011 um 19:21 schrieb Michael Keuter: >>> > Am 27.09.2011 um 19:05 schrieb Fernando Fuentes: >>> >> >>> >> Michael, >>> >> >>> >> astlinux-0.7.9 - Asterisk 1.8.4.4 >>> >> I have it set to restart in case of a crash but is not emailing me. >>> This is why I didnt caught it. I am wondering why is not emailing me. The >>> logs do not show any signs of a crash or any signs of an attempt to email me >>> due to a crash. >>> >> Though my uptime does not match and this is been occurring since day >>> one so something is crashing asterisk on an everyday basis. I can get emails >>> from my fax just fine so the email settings are right. >>> > >>> > Are your email settings in Network/Outbound SMTP... correct, and have >>> you tested that? >>> > Normally you see when Safe-Asterisk restarted Asterisk in the log >>> (/var/log/messages) independent of the email stuff.. >>> > >>> > Michael >>> >>> >>> You can try to manually kill Asterisk with >>> >>> "cat /var/run/asterisk/asterisk.pid" >>> "kill -9 <PID>" in the console, and then see what's in the log. >>> >>> Normally Safe_Asterisk catches that, restarts it, and makes a log entry. >>> Like this: >>> >>> Sep 27 19:38:05 alix user.info safe_asterisk: Asterisk exited on signal >>> 9. >>> Sep 27 19:38:05 alix user.info safe_asterisk: Automatically restarting >>> Asterisk. >>> >>> Then at least you know that Safe_Asterisk works. >>> >>> Michael >>> >>> http://www.mksolutions.info >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2dcopy1 >>> _______________________________________________ >>> Astlinux-users mailing list >>> Astlinux-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to >>> pay...@krisk.org. >>> >> >> >
messages
Description: Binary data
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
