I tried running sipxconfig.sh directly from the console to see if I got 
any better diagnostics and saw this
exception:

org.springframework.beans.factory.access.BootstrapException: Unable to 
initialize group definition. Group resource name 
[classpath*:beanRefContext.xml], factory key [servicelayer-context]; 
nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'servicelayer-context' defined in URL 
[jar:file:/usr/share/sipxpbx/lib/sipxconfig.jar!/beanRefContext.xml]: 
Instantiation of bean failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Could not 
instantiate bean class 
[org.springframework.context.support.ClassPathXmlApplicationContext]: 
Constructor threw exception; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'sip' defined in class path resource 
[org/sipfoundry/sipxconfig/sip/sip.beans.xml]: Invocation of init method 
failed; nested exception is java.lang.NullPointerException
        at 
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180)
        at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
        at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
        at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
        at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at 
org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
        at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at 
org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:378)
        at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
        at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
        at org.apache.tools.ant.Main.runBuild(Main.java:668)
        at org.apache.tools.ant.Main.startAnt(Main.java:187)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)

M. Ranganathan wrote:
> On Tue, Jun 3, 2008 at 11:25 AM, Scott Lawrence <[EMAIL PROTECTED]> wrote:
>   
>> On Tue, 2008-06-03 at 10:03 -0400, Michael Cote wrote:
>>     
>>> I have been running sipX under CentOS 5.   I started with a 3.8
>>> installation, upgraded to 3.10 and
>>> had everything working fine.   Yesterday, I upgraded (via the RPMs) to
>>> 3.11.3
>>>       
>> Why?
>>
>> >From the download page:
>>
>>        The builds in the main directory are of the current mainline
>>        development code. They may not work, and may badly disrupt your
>>        system. It is not a goal of the project to support upgrade from
>>        or between development builds. They may not be suitable for any
>>        production purpose - you have been warned.
>>
>> All users... please take the above seriously.In particular, we are
>> currently early in the development cycle for the next release - this is
>> when we put in the really high risk stuff (so that we get lots of
>> testing time to shake it down).  Very late in the cycle, the development
>> builds get to be pretty good, but we are not there yet.
>>
>>     
>
> In this case the problem might have to do with my commit. This problem
> may have been caused by my style beautification which lead to a bug in
> initialzing logging ( see my reply to Andre ). Will be fixed in a day
> or two ( after Damian deems the next patch acceptable ).
>
> Ranga
>
>
>   
>> --
>> Scott Lawrence  tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED]
>>  sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
>>  CTO, Voice Solutions   - Bluesocket Inc. http://www.bluesocket.com/
>>                                           http://www.pingtel.com/
>>
>> _______________________________________________
>> sipx-users mailing list
>> [EMAIL PROTECTED]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users
>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
>>
>>     
>
>
>
>   

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

Reply via email to