Guys,

Well I have identified the issue by looking into sipxconfig.log, I got some
java exception about my-color.css and then I remind that I have played with
it in the past:

http://wiki.sipfoundry.org/display/sipXecs/Customizing+Colors%2C+Layout+and+Logo

/etc/sipxpbx/sipxplugin.beans.xml file was present but not my-layout,
my-colors.css so I have just created it and it works now...

Sorry for the noise it's around 3AM in France, so the lesson will be never
start to upgrade your system at 1 AM if you are tired, sorry for the noise.

Thanks Tony and George for pointing me on sipxconfig.log.

Have a nice evening.

Best Regards.

Cyril

2011/12/13 George Niculae <[email protected]>

>
> On Dec 13, 2011 3:30 AM, "Cyril Constantin" <[email protected]>
> wrote:
> >
> > I just tried but same result:
> >
> > [root@ps0sipx01 tmp]# sipxproc -r ConfigServer
> > {"ConfigServer"=>true}
> >
>
> As Tony advised please provide sipxconfig.log
>
> George
>
> > 2011/12/13 Tony Graziano <[email protected]>
> >>
> >> Did you try
> >>
> >> sipxproc -r ConfigServer
> >>
> >> If it doesn't start look at your sipxconfig.log.
> >>
> >> On Dec 12, 2011 8:12 PM, "Cyril Constantin" <[email protected]>
> wrote:
> >>>
> >>> I can't because I don't have access to the GUI, if you know how to do
> it by command line, it will be appreciated.
> >>>
> >>> Thanks
> >>>
> >>> 2011/12/13 Tony Graziano <[email protected]>
> >>>>
> >>>> DD you send all the sercvers their profiles after updating?
> >>>>
> >>>> On Dec 12, 2011 7:55 PM, "Cyril Constantin" <
> [email protected]> wrote:
> >>>>>
> >>>>> Hi Guys,
> >>>>>
> >>>>> I just have upgraded my sipxecs server 4.4 to latest release by
> using yum update like in the wiki below:
> >>>>>
> http://wiki.sipfoundry.org/display/sipXecs/Upgrade+to+Latest+Stable+Version
> >>>>>
> >>>>> but I'm getting this webpage error when I'm trying to connect on GUI
> >>>>>
> >>>>> HTTP ERROR: 500
> >>>>>
> >>>>> Unable to read OGNL expression '<parsed OGNL expression>' of
> $Exception_39@3c1[InternalErrorPage]: Method "getStylesheets" failed for
> object org.sipfoundry.sipxconfig.components.TapestryContext@da20b4f
> >>>>>
> >>>>> RequestURI=/sipxconfig/app
> >>>>>
> >>>>> Powered by Jetty://
> >>>>>
> >>>>>
> >>>>> I have already upgraded sipxecs few months ago with yum update
> without issue, it's the first time that I met this case.
> >>>>>
> >>>>> I have HA cluster, I have started by primary server and started back
> up the system by using "service sipxecs start" and then tried to connect to
> GUI but no luck to have it working.
> >>>>>
> >>>>> I'm still able to connect with my Sip softphone and to provisioning,
> openfire still work as well., only GUI is unreachable.
> >>>>> Any ideas?
> >>>>>
> >>>>> Thanks a lot in advance.
> >>>>>
> >>>>>
> >>>>> Best Regards.
> >>>>>
> >>>>>
> >>>>> Cyril
> >>>>>
> >>>>> _______________________________________________
> >>>>> sipx-users mailing list
> >>>>> [email protected]
> >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> sipx-users mailing list
> >>>> [email protected]
> >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> sipx-users mailing list
> >>> [email protected]
> >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >>
> >>
> >> _______________________________________________
> >> sipx-users mailing list
> >> [email protected]
> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >
> >
> >
> > _______________________________________________
> > sipx-users mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to