|Summary:||ASTERISK-13020: CLI non-responsive|
|Reporter:||George Qualley IV (qualleyiv)||Labels:|
|Date Opened:||2008-11-06 00:04:17.000-0600||Date Closed:||2008-11-18 16:12:54.000-0600|
|Description:||I just moved from the latest 1.4 build to 22.214.171.124. For some reason, the command line interface doesn't seem to respond to any commands other than quit. For example if I type: "Core set verbose 20" all I get is: |
|Comments:||By: Leif Madsen (lmadsen) 2008-11-12 15:10:19.000-0600|
hrmmmmmmmm.... I have not seen this on my system. What kind of system are you running on? What distribution?
We'll need more information to try and reproduce this because I have not run into this issue on any of the systems I've installed 1.6 on...
By: George Qualley IV (qualleyiv) 2008-11-13 10:03:23.000-0600
Sure, I'm on Mac OS X Server 10.5.5, PowerPC. Sorry for not responding sooner, I wanted to check a couple of things first, but now I'm pretty sure I've ironed out all of the stuff that I thought might be a problem. Just FYI, one thing I tried was this: previously, I was launching Asterisk with Launchd using the -pg option. I noticed that this threw this error: "Mac OS X detected. Use '/sbin/launchd -d' to launch with the nofork option."
I'm certainly no expert on Launchd (who is, after all) but as far as I can gather, that command won't actually work, instead, I tried changing my Launchd Plist file to use the -fp option (not sure that the -p option really does anything on my system, but from what I gather the -f option would be equivalent to nofork). I really don't know. If I'm wrong please correct me.
By: Jason Parker (jparker) 2008-11-18 16:12:53.000-0600
This is a duplicate of ASTERISK-12666. Please add any additional comments there.