Vladimir, What is the current state of SSVM (has been been deployed and functional)? How recent is the error? Does it still occur or does it have an old timestamp?
Thanks ilya > -----Original Message----- > From: Ahmad Emneina [mailto:aemne...@gmail.com] > Sent: Tuesday, March 05, 2013 4:15 PM > To: Cloudstack users > Subject: Re: nfs://192.168.12.50/secondary Alert state detected. > > hey vladimir can you post more logs? preferably to an external paste site, > like > pastebin.com. > > > On Mon, Mar 4, 2013 at 10:39 PM, Vladimir Ivanov > <company....@gmail.com>wrote: > > > I'm trying to install the СloudStack. Use runbook: > > http://people.apache.org/~ke4qqq/runbook/< > > > http://www.linkedin.com/redirect?url=http%3A%2F%2Fpeople%2Eapache% > 2Eor > > g%2F%7Eke4qqq%2Frunbook%2F&urlhash=yruc&_t=tracking_disc > > >. > > When > > I add secondary storage my dashboard is saying : > > nfs://192.168.12.50/secondary Alert state detected. > > In the logs I see: > > 2013-03-05 10:24:09,250 INFO > > [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) > > Unable to start secondary storage vm for standby capacity, secStorageVm > vm Id : > > 1047, will recycle it and start a new one > > 2013-03-05 10:24:22,944 DEBUG [cloud.server.StatsCollector] > > (StatsCollector-3:null) There is no secondary storage VM for secondary > > storage host nfs://192.168.12.50/secondary How do I solve this > > problem? > > And yes I can read and write to my primary and secondary mount. > >
