tampler edited a comment on issue #3397:
URL: https://github.com/apache/cloudstack/issues/3397#issuecomment-992220822


   I'm having the same issue with the latest 4.15 code. Simulator seems to be 
totally unmainted on Docker as per 
[this](https://hub.docker.com/r/cloudstack/simulator).
   
   Ubuntu 21.10
   Docker 20.10.11
   
   After building the ACS I had to manually run `ssh-keygen` command to produce 
a `id_rsa.cloud` key and restart the simulator container. Now, I'm getting a 
null-pointer exception as below. The full log is here: 
[sim.log](https://github.com/apache/cloudstack/files/7702115/sim.log)
   ```bash
   [0m INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) (logid:) 
Loading module context [root-ca] from URL 
[jar:file:/acs/client/target/cloud-client-ui-4.15.3.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
   [0m INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) 
Configuring CloudStack Components
   [0m [WARNING] Failed startup of context 
o.e.j.m.p.JettyWebAppContext@10f192d8{/client,file:///acs/client/target/classes/META-INF/webapp/,UNAVAILABLE}{file:///acs/client/target/classes/META-INF/webapp/}
   [0m org.springframework.context.ApplicationContextException: Failed to start 
bean 'cloudStackLifeCycle'; nested exception is java.lang.NullPointerException
   [0m     at 
org.springframework.context.support.DefaultLifecycleProcessor.doStart 
(DefaultLifecycleProcessor.java:181)
   [0m     at 
org.springframework.context.support.DefaultLifecycleProcessor.access$200 
(DefaultLifecycleProcessor.java:54)
   [0m     at 
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start
 (DefaultLifecycleProcessor.java:356)
   ```
   
   @rhtyd Could you pls take a look 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to