I am only aware that before ssvm is up, you will see such message in
StatCollector, but that is no hurt. I don't understand why you encountered
this even if your ssvm is up? Is your s-1-VM entry in host db table is in
Up state? Are you using devcloud or real hypervisor in your setup? We may
need detailed log to figure out what is going on here in your case.

Thanks
-min

On 9/26/13 6:39 AM, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote:

>I get "No running ssvm is found, so command will be sent to
>LocalHostEndPoint" while I can see and log into a machine called
>s-1-VM which has state 'RUNNING' in the database. Is there some
>relation? I never though much of it as it does not seem to be the
>first thing stopping me usually.
>
>On Wed, Sep 25, 2013 at 11:20 PM, Edison Su <edison...@citrix.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
>>> Sent: Wednesday, September 25, 2013 12:38 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: LocalHostEndPoint seems to get called
>>>
>>> While I'm doing development and restarting things and what not, it
>>>seems
>>> often storage commands get routed to LocalHostEndPoint.  This seems
>>>bad.  I
>>> don't have sudo setup for my user on my laptop, so things like "Unable
>>>to
>>> create local folder for:
>>> /mnt/secStorage/64d6e26f-e656-3ba3-908f-ce6610ede011 in order to mount
>>> nfs://192.168.3.134:/exports/secondary1" fail.  But the bigger problem
>>>is,
>>> shouldn't that not happen at all.  It seems like in a normal setup it
>>>should
>>> never try to use LocalHostEndpoint.  Do I have some setting flipped
>>>that is
>>> enabling that?
>>
>> The current code has bug if ssvm agent is not in the up state, then
>>template downloading will likely choose localhostendpoint to download
>>template.
>> Localhostendpoint should only be used to download system vm template.
>>
>>>
>>> Seems like with the current code you might accidentally mount
>>>secondary to
>>> the management server if the conditions are right...
>>>
>>> Darren

Reply via email to