<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1476" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=638013521-10012006><FONT face=Arial color=#0000ff size=2>from
the command line, run asterisk -v. You will either get "Asterisk Ready" (good)
or "Ouch...Broken Pipe" (bad). If it breaks, note the name of the last .so
file it referenced before you got the "Ouch" and remove that file from
/var/lib/asterisk/modules. Rinse and repeat until you get an "Asterisk Ready"
prompt. Once you do, Ctrl-C (kill) it, then run ampportal start. Asterisk should
run OK. </FONT></SPAN></DIV>
<DIV><SPAN class=638013521-10012006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=638013521-10012006><FONT face=Arial color=#0000ff size=2>Now
you have to figure out why the .so modules you removed won't run. However, a lot
of times they aren't important for you to use, so you can ignore them. For
example, app_adsiprog.so is only relevant if you are running ADSI phones. If you
aren't, and it's causing Asterisk to die, leave it out. </FONT></SPAN></DIV>
<DIV><SPAN class=638013521-10012006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=638013521-10012006><FONT face=Arial color=#0000ff size=2>One
other thing comes to mind and that is you might be running safe_asterisk
*already* from ampportal start which is invoked by default in
/etc/rc.d/rc.local. Comment out the /usr/sbin/ampportal start in rc.local,
reboot, THEN try the above stuff. If Asterisk runs right away, then it is a
conflict with the entry in rc.local. You can comment it back in, reboot, then
type in asterisk -r at the command line to get an Asterisk console. If not, you
have to follow the troubleshooting procedure above in order to get it running.
</FONT></SPAN></DIV>
<DIV><SPAN class=638013521-10012006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=638013521-10012006><FONT face=Arial color=#0000ff
size=2>hth</DIV>
<DIV><BR></DIV></FONT></SPAN>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Ben Ferguson
[mailto:ben@circlepix.com]<BR><B>Sent:</B> Tuesday, January 10, 2006 1:48
PM<BR><B>To:</B> 'Asterisk Users Mailing List - Non-Commercial
Discussion'<BR><B>Subject:</B> [Asterisk-Users] Help with amportal: asterisk
ended with exit status 127<BR><BR></FONT></DIV>
<DIV>
<P><FONT size=2>Greetings. I am trying to get AMP up and going on my Asterisk
server. I can access the admin pages on my asterisk server via a web browser.
I can add and edit things via the web browser and it edits the database
accordingly. Everything seems fine except when I try to run 'amportal start'.
Below is what I get (Plus tail /var/log/asterisk/full, but the tail of the
'full' log doesn't seem to list anything from trying to run amportal. It seems
to me that the last lines from the 'full' log are related to me stopping my
currently up and running asterisk so that I can try to run the amportal
command. Make sense?). Please help.</FONT></P>
<P><FONT size=2>Thanks,</FONT></P>
<P><FONT size=2>Ben F</FONT></P>
<P><FONT size=2>CirclePix</FONT></P>
<P><SPAN class=375354620-10012006><FONT
size=2>************************************************************************</FONT></SPAN></P>
<P><FONT size=2>[root@blah]# /usr/sbin/amportal start</FONT></P>
<P><FONT size=2>SETTING FILE PERMISSIONS</FONT></P>
<P><FONT size=2>Permissions OK</FONT></P>
<P><FONT size=2>STARTING ASTERISK</FONT></P>
<P><FONT size=2>Asterisk ended with exit status 127</FONT></P>
<P><FONT size=2>Asterisk died with code 127.</FONT></P>
<P><FONT size=2>Automatically restarting Asterisk.</FONT></P>
<P><FONT size=2>Asterisk ended with exit status 127</FONT></P>
<P><FONT size=2>Asterisk died with code 127.</FONT></P>
<P><FONT size=2>Automatically restarting Asterisk.</FONT></P>
<P><FONT size=2>mpg123: no process killed</FONT></P>
<P><FONT
size=2>-----------------------------------------------------</FONT></P>
<P><FONT size=2>Asterisk could not start!</FONT></P>
<P><FONT size=2>Use 'tail /var/log/asterisk/full' to find out why.</FONT></P>
<P><FONT
size=2>-----------------------------------------------------</FONT></P>
<P><FONT size=2>[root@blah]#</FONT></P>
<P><FONT size=2>[root@blah]# tail /var/log/asterisk/full</FONT></P>
<P><FONT size=2>Jan 10 09:47:01 VERBOSE[12657] logger.c: == Registered file
format pcm, extension(s) pcm|ulaw|ul|mu</FONT></P>
<P><FONT size=2>Jan 10 09:47:01 VERBOSE[12657] logger.c: == Manager registered
action DBGet</FONT></P>
<P><FONT size=2>Jan 10 09:47:01 VERBOSE[12657] logger.c: == Manager registered
action DBPut</FONT></P>
<P><FONT size=2>Jan 10 09:47:01 VERBOSE[12657] logger.c: == Parsing
'/etc/asterisk/enum.conf': Jan 10 09:47:01 VERBOSE[12657] logger.c: == Parsing
'/etc/asterisk/enum.conf': Found</FONT></P>
<P><FONT size=2>Jan 10 09:47:01 VERBOSE[12657] logger.c: Asterisk
Ready.</FONT></P>
<P><FONT size=2>Jan 10 09:47:09 VERBOSE[12657] logger.c: Asterisk Ready.
Beginning asterisk shutdown.... Jan 10 09:47:09 VERBOSE[12657] logger.c:
Executing last minute cleanups</FONT></P>
<P><FONT size=2>Jan 10 09:47:09 VERBOSE[12657] logger.c: == Destroying
musiconhold processes</FONT></P>
<P><FONT size=2>Jan 10 09:47:09 VERBOSE[12657] logger.c: Asterisk cleanly
ending (0). [root@blah]#</FONT></P></DIV></BLOCKQUOTE></BODY></HTML>