[
https://issues.apache.org/jira/browse/CLOUDSTACK-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562959#comment-13562959
]
Noa Resare commented on CLOUDSTACK-1004:
----------------------------------------
[[email protected]] Thanks for the tip; I'll remember that.
[[email protected]] The error message I got on the management server
was the following:
2013-01-17 10:33:55,596 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-11:null) Details from executing class
com.cloud.agent.api.storage.ListTemplateCommand:
com.cloud.utils.exception.CloudRuntimeException: GetRootDir for
nfs://lon2-cloudtest-a2/spotify/export/secondary failed due to
java.net.UnknownHostException: lon2-cloudtest-a2
at
com.cloud.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1003)
at
com.cloud.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:711)
at
com.cloud.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:166)
at com.cloud.agent.Agent.processRequest(Agent.java:518)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:831)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
It was not obvious to me that the exception was actually serialized on the
agent and sent to the manager to be logged. I spent a fair amount of time to
try to figure out why the logging framework somehow failed to propagate the log
statement on NfsSecondaryStorageResource.java:1002 to the manager logfile. In
hindsight it is kind of obvious that the loggins ends up in the logfile on the
secondary storage VM. I have opened CLOUDSTACK-1005 to track this.
> add to install guide: fqdn required when adding secondary storage
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-1004
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1004
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Reporter: Noa Resare
> Assignee: Radhika Nair
> Priority: Minor
>
> I set up a fresh test install of cloudstack 4.0 now and ran into some
> problems. It turned out that the secondary storage VM could not mount the
> secondary storage via NFS because the NFS URI configured when setting up the
> zone only held the hostname and not hostname plus fully qualified domain
> name.
> This worked fine when testing mounts form the hypervisors (that had a
> properly configured search path) but the secondary storage VM doesn't have
> it's domain configured to match the rest of the machines, so secondary
> storage operation failed.
> The error I got in the logfile was kind of unhelpful when tracking down this,
> so a brief note in the installation instruction would have been nice.
> I propose we change item 11 of section 6.2.2 of the installation instruction,
> replacing "The IP address of the server" with "The IP address or fully
> qualified hostname of the server. Please note that only the hostname will not
> work, as the secondary storage VM will not be able to properly resolve the
> hostname"
--
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
