If you still wanna try it, the sipxconfig.properties is the file you need to change. I think the lines you need to remove are:
1. locationsMigrationTrigger.hostname 2. sipImpl.hostIpAddress 3. sipImpl.proxyPort 4. sipImpl.hostName 5. sipImpl.proxyHost They might be shown at the end of the file. - MM On Mon, May 18, 2009 at 6:24 AM, Borginger Rikard < rikard.borgin...@combitech.se> wrote: > > > Here are my output and logs.. > > > > > [...] > > > > Here is the interesting part (and the reason that sipXconfig is not > > starting): > > > > > > > "2009-05-12T14:13:26.437000Z":3:JAVA:ERR:xx.xx.se:main:0000000 > > 0:ContextLoader:"Context initialization failed" > > > org.springframework.beans.factory.BeanCreationException: Error > > > creating bean with name 'locationsMigrationTrigger' defined > > in class > > > path resource > > > [org/sipfoundry/sipxconfig/admin/commserver/commserver.beans.xml]: > > > Initialization of bean failed; nested exception is > > > org.springframework.beans.InvalidPropertyException: Invalid > > property > > > 'hostname' of bean class > > > > > [org.sipfoundry.sipxconfig.admin.commserver.LocationsMigrationTrigger] > > > : No property 'hostname' found Caused by: > > > org.springframework.beans.InvalidPropertyException: Invalid > > property > > > 'hostname' of bean class > > > > > [org.sipfoundry.sipxconfig.admin.commserver.LocationsMigrationTrigger] > > > : No property 'hostname' found > > [...] > > > > In general, we don't test upgrades from an unstable version > > to a stable version. That being said, there are two things > > we can do here. The first is the easiest. You can remove > > the offending line from > > sipxconfig.properties.in: > > locationsMigrationTrigger.hostname=xxxxx > > > > Then just restart sipx and all should be well. Should be. > > If this error is there, then there may be others. There was > > significant work done to sipxconfig.properties and you may > > run into more problems (again, due to upgrading from unstable > > to stable versions). > > > > That line was removed at some point between your 3.11 build > > and the 4.0 build. The more interesting question is why your > > sipxconfig.properties wasn't updated. Would you mind > > attaching sipxconfig.properties.in for us to look at? > > I would if there was one. Apparently that file is gone. There is a file > called sipxconfig.properties but no file with the .in-extension. Something > went really bad here and it's time to wipe it. So I am going to reinstall > the server from scratch with the new 4.0. > > It's good to know that you don't test upgrades from unstable to stable. So > I should keep my unstable servers that way. > > Thanks for your time! > > / Rick > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
