cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From he...@powershield.ru
Subject Re: VR starting problem
Date Mon, 06 Nov 2017 17:48:33 GMT
Changed few hours ago, and anyway still the same problem.



Ivan Kudryavtsev писал 2017-11-06 20:40:
> Hi. Don't mix "used" and "allocated". Just change the specified 
> threshold
> to 0.98 and go ahead.
> 
> 7 нояб. 2017 г. 0:22 пользователь <hello@powershield.ru> написал:
> 
>> No, i re-checked maybe 10 times. I just added some more space, but the
>> problem is same. All VM's working but if client restart - they goes 
>> down,
>> with the same error with insufficient storage.
>> 
>> 
>> Ivan Kudryavtsev писал 2017-11-06 20:16:
>> 
>>> Could it be, that your storage, cluster, pod, zone is in the 
>>> maintanence
>>> mode?
>>> 
>>> 6 нояб. 2017 г. 23:51 пользователь "Ivan Kudryavtsev" <
>>> kudryavtsev_ia@bw-sw.com> написал:
>>> 
>>> Hi. Try to find in early logs what exactly resource is insufficient. 
>>> Try
>>>> to play with threshold of it.
>>>> 
>>>> 6 нояб. 2017 г. 21:57 пользователь <hello@powershield.ru>
написал:
>>>> 
>>>> Now, i see the problem, then VR restarting.
>>>>> 
>>>>> 2017-11-06 11:54:15,821 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>>> (API-Job-Executor-43:ctx-02214ed9 job-14455) (logid:18ad84ad) 
>>>>> Complete
>>>>> async job-14455, jobStatus: FAILED, resultCode: 530, result:
>>>>> org.apache.cloudstack.api.response.ExceptionResponse/null/{"
>>>>> uuidList":[],"errorcode":530,"errortext":"Resource [Host:17] is
>>>>> unreachable: Host 17: Unable to start instance due to Unable to 
>>>>> start
>>>>> VM:18985a14-3cb5-46d5-a3f0-3a065cd8b014 due to error in 
>>>>> finalizeStart,
>>>>> not retrying"}
>>>>> 2017-11-06 15:47:27,814 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>>> (API-Job-Executor-69:ctx-be0b5550 job-14663) (logid:8b609324) 
>>>>> Complete
>>>>> async job-14663, jobStatus: FAILED, resultCode: 530, result:
>>>>> org.apache.cloudstack.api.response.ExceptionResponse/null/{"
>>>>> uuidList":[],"errorcode":530,"errortext":"Unable to start a VM due 
>>>>> to
>>>>> insufficient capacity"}
>>>>> 2017-11-06 16:54:19,055 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>>> (API-Job-Executor-70:ctx-deaaf8e8 job-14668) (logid:6a7700af) 
>>>>> Complete
>>>>> async job-14668, jobStatus: FAILED, resultCode: 530, result:
>>>>> org.apache.cloudstack.api.response.ExceptionResponse/null/{"
>>>>> uuidList":[],"errorcode":530,"errortext":"Resource [DataCenter:2] 
>>>>> is
>>>>> unreachable: Unable to reboot domR, it is not in right state 
>>>>> Stopped"}
>>>>> 2017-11-06 16:58:54,235 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>>> (API-Job-Executor-71:ctx-b26b3b33 job-14669) (logid:436e6183) 
>>>>> Complete
>>>>> async job-14669, jobStatus: FAILED, resultCode: 530, result:
>>>>> org.apache.cloudstack.api.response.ExceptionResponse/null/{"
>>>>> uuidList":[],"errorcode":530,"errortext":"Unable to create a 
>>>>> deployment
>>>>> for VM[DomainRouter|r-1919-VM]"}
>>>>> 
>>>>> I'm pretty sure, what i have enough resources:
>>>>> 
>>>>> Primary Storage Used
>>>>> Allocated: 4.22 TB / 4.88 TB
>>>>> 
>>>>> Primary Storage Allocated
>>>>> Allocated: 3.02 TB / 4.88 TB
>>>>> 
>>>>> Memory Allocated
>>>>> Allocated: 78.00 GB / 597.93 GB
>>>>> 
>>>>> CPU Allocated
>>>>> Allocated: 81.00 GHz / 440.00 GHz
>>>>> 
>>>>> Shared Network IPs
>>>>> Allocated: 34 / 253
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Ivan Kudryavtsev писал 2017-11-06 15:28:
>>>>> 
>>>>> Hi, you should dive into management server logs to find relevant
>>>>>> messages.
>>>>>> Otherwise it's impossible to predict what's wrong with the system.
>>>>>> Check
>>>>>> logs and find exceptions and other errornous stuff.
>>>>>> 
>>>>>> 6 нояб. 2017 г. 18:14 пользователь <hello@powershield.ru>
написал:
>>>>>> 
>>>>>> Hello,
>>>>>> 
>>>>>>> 
>>>>>>> ACS: 4.8.0
>>>>>>> XenServer 6.5SP1
>>>>>>> 
>>>>>>> 
>>>>>>> We have got some problem with additional space for our client.
>>>>>>> 
>>>>>>> We are created new Disk Offering, then we tryed to attach for
our
>>>>>>> client,
>>>>>>> but got error: Unable to find suitable primary storage when 
>>>>>>> creating
>>>>>>> volume
>>>>>>> 
>>>>>>> We checked datadisk and we see, there is not hypervisor (should

>>>>>>> it be
>>>>>>> showed? Now saying: None)
>>>>>>> 
>>>>>>> We tryed to create new instance, but also unlucky.
>>>>>>> 
>>>>>>> After it, we restarted VR and he can't start. He started and

>>>>>>> again
>>>>>>> goes
>>>>>>> to
>>>>>>> offline. We tryed to check from XenCenter and got this reason:
>>>>>>> apache2:
>>>>>>> Could not reliably determine the server's fully qualified domain

>>>>>>> name,
>>>>>>> using 127.0.0.1 for ServerName.
>>>>>>> 
>>>>>>> We delete VR and now, we can not start it manually and he is
not
>>>>>>> starting
>>>>>>> automatically about 40min.
>>>>>>> 
>>>>>>> 
>>>>>>> 

Mime
View raw message