I see this happen when sipXconfig is still churning around trying to get started up and hasn't fully initialized. This also happens if something throws in sipxconfig before things are initialized. Look in the sipxconfig log file for stack backtraces maybe.
If you have DEBUG logging on the startup time for sipXconfig can be a couple of minutes depending on the h/w. -Eric On Apr 23, 2010, at 2:55 PM, Picher, Michael wrote: > Trying to help out on an upgrade gone bad… > > Anybody seen this after an upgrade? > > HTTP ERROR: 404 > > /sipxconfig Not Found > RequestURI=/sipxconfig > > Powered by Jetty:// > > > > I did get a backup from command line, reinstalled, I uninstalled sipX > cleared the database, could get into the gui after that with the blank > database, restored and am right back to the above. > > Mike > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
