Hey Chad! It may not be the most CLI friendly program -- however it
has worked for YEARS and is my best friend when it comes to emailing
logging and system stats. Because my stats are important for admin
purposes, I am of course open to other mutt alternatives, as I need
logs emailed to me (what ever it takes). MUTT in itself has proved to
us as lightweight and extremely responsive.
I am open to suggestions however with mutt alternatives.
Cheers!
--
*
*FOUNDER & SR. TELECOM ANALYST*
/VOIPERNETICS COMMUNICATIONS <http://www.voipernetics.com/>/*
NATION WIDE DIDS, SIP TRUNKS & VOIP 911.
PARTIAL / FULL VIRTUAL PRI - NO CONTRACTS!
HOSTED PBX & TERMINATION SERVICES.
TEL: 647-476-2067
Chad Osmond wrote the following on 9/26/2011 12:49 PM:
Run a strace on the mutt process from inside the shell script and see
what it says..
strace `which mutt`> /tmp/log_strace_mutt
That will probably shed some light on the issue.
Why are you calling mutt exactly? It's not the most cli friendly
program around :)
On Mon, Sep 26, 2011 at 12:47 PM, Reza - Voipernetics
<[email protected]> wrote:
Chad: An interesting observation here.
I've added and inserted new dial plans. My observation was limited to a
combination of commands of which, "mutt" was one of them. I removed mutt
and replaced it with output file redirection. ALL my logs are stored in the
text files. So now I know my shell script is working through SYSTEM()
Now -- the next line in my dialplan is the MUTT command. I think at this
stage because I've confirmed the "shell scripts" are working, contrary to my
initial findings... I have to further pin point that "mutt" is not working
when being called by SYSTEM() from any part of the dialplan.
MUTT in itself works. So now the culprit is the MUTT process - why this
fails to work (without spitting any errors) when called from SYSTEM() but
works perfectly fine when invoked DIRECTLY from the console. And yes, FULL
PATH NAME for MUTT is included.
Can you think of any theories to this?
/*
Thanks!
Reza.*/
--
*
*FOUNDER& SR. TELECOM ANALYST*
/VOIPERNETICS COMMUNICATIONS<http://www.voipernetics.com/>/*
NATION WIDE DIDS, SIP TRUNKS& VOIP 911.
PARTIAL / FULL VIRTUAL PRI - NO CONTRACTS!
HOSTED PBX& TERMINATION SERVICES.
TEL: 647-476-2067
Chad Osmond wrote the following on 9/26/2011 12:34 PM:
Hi.
It is always a possibility with non-ECC ram, it happens on occasion,
but not really something people think about. Stuff that WAS working
stops for no reason, with no changes.
Take a look at this:
http://it.slashdot.org/story/10/06/24/2210214/tracking-down-a-single-bit-ram-error
If it's not critical you can probably follow the steps posted there
and find the issue, but it's a lot of work. Odds are a asterisk
stop/start will resolve the issue.
Asterisk probably shares memory internally, so failures continue in
the dialplan, but a new process from a new shell would work fine.
Chad
On Mon, Sep 26, 2011 at 12:30 PM, Reza - Voipernetics
<[email protected]> wrote:
Hello Chad! Interesting! I have to check if it is ECC memory or not.
I
am using Ubutu 64 with 8 gigs ram.
Essentially what you are saying here is a **IF** this is a non ecc ram, a
reboot will solve it... perhaps even an asterisk restart ... if not, a
full
power cycle. I would HATE to do this - but if this is indeed the case
-
then adverse restart (Reboot and/or powercycle) would clear up the ram,
potentially fixing the problem.
FYI - Just tried the dialplan on a different context. Shell script did
not
execute. Ran it on an identical server - no problem!
--
*
*FOUNDER& SR. TELECOM ANALYST*
/VOIPERNETICS COMMUNICATIONS<http://www.voipernetics.com/>/*
NATION WIDE DIDS, SIP TRUNKS& VOIP 911.
PARTIAL / FULL VIRTUAL PRI - NO CONTRACTS!
HOSTED PBX& TERMINATION SERVICES.
TEL: 647-476-2067
Chad Osmond wrote the following on 9/26/2011 12:24 PM:
Ecc memory in the server? If not the in memory version may have a bit
flipped somewhere.
Happens on rare occssions with non ecc ram
On 2011-09-26 12:00 PM, "Reza - Voipernetics"<[email protected]
<mailto:[email protected]>> wrote:
Any idea why shell scripts called within the dialplan with the SYSTEM
command cease to function (without errors generated?).
My linux commands invoked via SYSTEM() is no longer working.
Thanks!
--
*
*FOUNDER& SR. TELECOM ANALYST*
/VOIPERNETICS COMMUNICATIONS<http://www.voipernetics.com/>/*
NATION WIDE DIDS, SIP TRUNKS& VOIP 911.
PARTIAL / FULL VIRTUAL PRI - NO CONTRACTS!
HOSTED PBX& TERMINATION SERVICES.
TEL: 647-476-2067
