ok, i commited/pushed couple fixes to fix a few issues.  yum update is
all that's needed. (probably yum clean all before too)

note: i'm noticing some caching from apache, this this doesn't work
 http://hostname
try any of these just to get browser to flush cache
 https://hostname
 https://hostname/sipxconfig/app
 http://hostname:12000/sipxconfig/app

There are still some issues we're looking into, but i believe this
addresses the blockers.

On Mon, Mar 26, 2012 at 4:44 AM, Kumaran
<[email protected]> wrote:
>  Thanks for the update Douglas...I can't access the sipXconfig....Either by
> "https://sipx-test.ttplservices.com"; or
> https://sipx-test.ttplservices.com:8443/sipxconfig/app"...So going to
> re-install from scratch....
>
> Regards,
> Kumaran T
>
>
>
>
> On 3/26/2012 1:42 PM, Douglas Hubler wrote:
>>
>> I'll try to reproduce this.
>>
>> BTW: to get to user interface now, just enter  http://hostname.  You
>> no longer should go to port 8443
>>
>> On Mon, Mar 26, 2012 at 2:57 AM, Kumaran
>> <[email protected]>  wrote:
>>>
>>>    Today morning I removed all the logs and done  yum update...All the
>>> logs
>>> are generated except agent.logs...I restarted supervisor service and run
>>> sipxecs-setup but the agent.logs is not present....Is there anyway to
>>> service should be restarted or anyways to generate agent.log....I can't
>>> do
>>> it in sipXconfig because it will not open until sipxecs-setup is
>>> configured
>>> properly....
>>>
>>> Regards,
>>> Kumaran T
>>>
>>>
>>> On 3/26/2012 11:54 AM, George Niculae wrote:
>>>
>>>
>>> On Mar 26, 2012 9:22 AM, "Kumaran"<[email protected]>
>>> wrote:
>>>>
>>>> Hi All,
>>>>    I stopped the supervisor service and then yum update the 4.6
>>>> build...After yum update completed I started the supervisor service and
>>>> run sipxecs-setup which displays the error message as follow
>>>>
>>>> "[root@sipx-test ~]# sipxecs-setup
>>>> Configuring system, this may take a few minutes...
>>>> Error. System reports error for fopen: "No such file or directory"
>>>> Failure to run command /usr/bin/sipxagent  -d setup. See
>>>> /var/log/sipxpbx/sipxagent.log for details. After you
>>>> have addressed the issue, you may rerun this script.
>>>> failed."
>>>>
>>> Any clue in sipxagent.log?
>>>
>>> George
>>>
>>>
>>>
>>> _______________________________________________
>>> sipx-dev mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>>>
>>>
>>>
>>> _______________________________________________
>>> sipx-dev mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>>
>> _______________________________________________
>> sipx-dev mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to