should report the
secondary storage host status and update DB.
Anthony
-Original Message-
From: Nitin Mehta
Sent: Monday, May 07, 2012 7:45 AM
To: cloudstack-dev@incubator.apache.org; Ram Chinta
Cc: David Nalley; Anthony Xu
Subject: RE: Secondary nfs server alert issue
+Anthony
I think
> -Original Message-
> From: Nitin Mehta [mailto:nitin.me...@citrix.com]
> Sent: Monday, May 07, 2012 7:57 AM
> To: cloudstack-dev@incubator.apache.org; Ram Chinta
> Cc: David Nalley; Anthony Xu
> Subject: RE: Secondary nfs server alert issue
>
> Just to add to it
o:nitin.me...@citrix.com]
Sent: Monday, May 07, 2012 8:15 PM
To: cloudstack-dev@incubator.apache.org; Ram Chinta
Cc: David Nalley; Anthony Xu
Subject: RE: Secondary nfs server alert issue
+Anthony
I think we should not put the secondary storage in the host table since we do
not create an agent for it and d
Subject: RE: Secondary nfs server alert issue
There are two related entries in the host table related to secondary storage.
One is the entry has type as "SecondaryStorageVM" the other one is
"SecondaryStorage".
If SSVM is working fine then entry of type SecondaryStorageVM should b
incubator.apache.org
Cc: David Nalley
Subject: Re: Secondary nfs server alert issue
>It typically indicates a problem with the SSVM (Secondary Storage VM).
>It either did not get created, or most likely is unable to connect back
>to the Management once created and running.
>
>Do yo
>It typically indicates a problem with the SSVM (Secondary Storage VM). It
>either did not get created, or most likely is unable to connect back to
>the Management once created and running.
>
>Do you see any errors in the management server log? Refer to
>"Troubleshooting the Secondary Storage VM"
It typically indicates a problem with the SSVM (Secondary Storage VM). It
either did not get created, or most likely is unable to connect back to the
Management once created and running.
Do you see any errors in the management server log? Refer to "Troubleshooting
the Secondary Storage VM" sect
