cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1746) Cloudstack Usage Server won't start
Date Sat, 30 Mar 2013 20:23:16 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618146#comment-13618146
] 

ASF subversion and git services commented on CLOUDSTACK-1746:
-------------------------------------------------------------

Commit 80c588e6b6d04fa97d4934d12ae191aafde67319 in branch refs/heads/4.1 from Chip Childers
<chip.childers@gmail.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=80c588e ]

CLOUDSTACK-1746: fix logging warning in usage server

                
> Cloudstack Usage Server won't start
> -----------------------------------
>
>                 Key: CLOUDSTACK-1746
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1746
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0
>            Reporter: Francois Gaudreault
>            Assignee: Kelven Yang
>            Priority: Blocker
>             Fix For: 4.1.0
>
>         Attachments: cloudstack-usage.zip
>
>
> Using the latest 4.1 (commit cfff6708f35cfbe3a8f8a61b854b8043942d5b4c), the cloudstack-usage
server will not start.  Error is :
> log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> java.lang.reflect.InvocationTargetException
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:616)
> 	at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
> Caused by: java.lang.ExceptionInInitializerError
> 	at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:34)
> 	at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:616)
> 	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> 	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> 	at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> 	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> 	at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> 	at com.cloud.configuration.dao.ConfigurationDaoImpl$$EnhancerByCGLIB$$27aaa385.configure(<generated>)
> 	at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:97)
> 	at com.cloud.usage.UsageServer.start(UsageServer.java:53)
> 	... 5 more
> Caused by: java.lang.NullPointerException
> 	at java.io.FileInputStream.<init>(FileInputStream.java:133)
> 	at com.cloud.utils.crypt.EncryptionSecretKeyChecker.check(EncryptionSecretKeyChecker.java:65)
> 	at com.cloud.utils.db.Transaction.<clinit>(Transaction.java:101)
> 	... 19 more
> 20/03/2013 13:53:33 20255 jsvc.exec error: Cannot start daemon
> 20/03/2013 13:53:33 20254 jsvc.exec error: Service exit with a return value of 5

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message