cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6754) SSVM not responding with S3 secondary sotre
Date Tue, 27 May 2014 18:38:02 GMT


Min Chen commented on CLOUDSTACK-6754:

>From MS log, I can see that your SSVM agent is not running at all, that is why you saw
"There is no secondary storage VM for downloading template to image store s3perfgolstore"
in registering a template. Since SSVM agent is not running, it will not send back commands
to management server to sync default centos template. 

Also from cloud.out, you can see that SSVM agent failed to start due to this error:
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell
: Unsupported major.minor version 51.0
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(
        at Method)
        at java.lang.ClassLoader.loadClass(
        at sun.misc.Launcher$AppClassLoader.loadClass(
        at java.lang.ClassLoader.loadClass(
Could not find the main class: Program will exit.

This error indicates that you are using Java 6 to run Java 7 code on SSVM, you should use
the new system vm template that is upgraded to use Java 7.

> SSVM not responding with S3 secondary sotre
> -------------------------------------------
>                 Key: CLOUDSTACK-6754
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller, SystemVM, Template
>    Affects Versions: 4.4.0
>         Environment: Host: Xenserver
> Secondary Store: Image store with S3 as provider
>            Reporter: Pavan Kumar Bandarupally
>            Assignee: Min Chen
>            Priority: Blocker
>             Fix For: 4.4.0
>         Attachments: cloud.log,, management-server.log
> A new zone is created and systemVMs are up. The systemvm template is downloaded to S3
bucket. Once the SSVMs are up, the default BUILTIN centos template or any other template that
we try to register manually are not getting downloaded to SSVM. There is no exception generated
as well. 
> The registerTemplate API call is just listed in the MS traces and no further action happens.
Attaching the MS logs and SSVM log. There is no trace of any exception in SSVM log as well.
Attaching the /var/log/cloud/cloud.out , which is the only file that has some exception listed.

This message was sent by Atlassian JIRA

View raw message