On Thu, 2008-10-16 at 07:48 -0400, Damian Krzeminski wrote: > Alberto wrote: > > Hi, > > sipxconfig does not start in 3.11.7-013728 on CentOs 5.2. Some errors in > > the database upgrade prevent it to start. > > I got this error after updating with yum. > > > > Attached sipxconfig.log with all exceptions in it. > > > > Thanks in advance > > Alberto > > > > Yes. Probably some problems with the latest DB patch or data migration. I see > the same thing... > > "2008-10-16 09:30:41,027": INFO:DataInitializer:?:Creating task > init-location-specific-service > "2008-10-16 09:30:41,028": INFO:InitTaskListener:?:Initialization task > init-location-specific-service being handled by > org.sipfoundry.sipxconfig.service.LocationSpecificServiceInitTrigger > "2008-10-16 09:30:41,028": > INFO:LocationSpecificServiceInitTrigger:?:Initializing location-specific > service info > "2008-10-16 09:30:41,315": WARN:JDBCExceptionReporter:77:SQL Error: 0, > SQLState: null > "2008-10-16 09:30:41,315":ERROR:JDBCExceptionReporter:78:Batch entry 0 update > location_specific_service set location_id=null where location_id=1 was > aborted. Call getNextException to see the cause. > "2008-10-16 09:30:41,316": WARN:JDBCExceptionReporter:77:SQL Error: 0, > SQLState: 23502 > "2008-10-16 09:30:41,316":ERROR:JDBCExceptionReporter:78:ERROR: null value in > column "location_id" violates not-null constraint > > > Kevin: any chance for a quick workaround? > D. >
The quickest workaround is bin/sipxconfig.sh --database drop create ... though I realize that is not an ideal workaround. I am trying to reproduce the error on my system Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
