I have observed some odd behavior that I just wanted to check if anyone
else had seen or had any ideas on.  I have my own RPM build with some
additions to SipXConfig and I was trying to update a server with a
SipXecs build from source from about 10 days ago.

 

1.  When I tried to yum update the server with my latest RPM builds
(which are rebased with current SipXecs code excluding sq and rls)
SipXconfig UI would start but when I clicked the "Server" menu item the
menu list on the side would be empty (none of the new role menu items).

 

2.  When I rolled back to a snapshot and tried to update the server with
the current SipXecs snapshot repo I could no longer get into the
SipXconfig UI and would keep getting Jetty 404 errors

 

3.  When I completely wipe the server and start over with a new CentOS
6.2 image, install the current SipXecs snapshot repo, then update with
my custom RPM build, everything works fine.  That is, left-panel menu
now appears under "Server" and things generally seem to hold together.

 

Again just checking if anyone had seen this kind of behavior?  Or anyone
have any debug ideas?  Or anyone can tell me "yea, you cannot update,
always re-brick and install from scratch"?

 

As always, thanks for the input!

 

D Chang

 

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to