Yes, Thank you so much, You find out exact reason. Now I fix this issue.
:)
Thanks again.
On 11/27/2021 12:46 AM, Wei ZHOU wrote:
Hi,
This is indeed a capacity issue with memory (capacity Type : 0).
2021-11-26 18:47:42,550 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-8:ctx-dfeedfec job-1
Please download and see full log from ACS
https://drive.google.com/file/d/1BEB6HYgI8VWTjg9rwk3BZlfLlpPaRzZL/view?usp=sharing
Thank you so much.
On 11/26/2021 7:18 PM, Wei ZHOU wrote:
Hi,
Normally it is not a capacity issue. It might be caused by the systemvm
template, VR, etc. Please share th
Hi,
Normally it is not a capacity issue. It might be caused by the systemvm
template, VR, etc. Please share the full log (from job-16 is started).
-Wei
On Fri, 26 Nov 2021 at 14:12, technologyrss.mail <
technologyrss.m...@gmail.com> wrote:
> *Hi, *
>
> Please see error log:
>
> (logid:9bd01412)
Hi there :-)
I want to bring up the shapeBlue tutorial (
https://www.shapeblue.com/virtualbox-test-env/ ) a last time
Even if this tutorial is a bit old, I get it working flawlessly on my
laptop with Apache Cloudstack 4.11.1.0
That's pretty neat to have a sandbox environment for novice like me, to
Hello dear list,
@Andrija @Yordan thanks for these insightful informations! I did check with
attention pieces of information you brought up about my setup. I am still
sticking with XenServer because I feel It is more appealing for me.
Applying your precious information I got rid of previous misco
Hi
I went over your log file. Here are some memorable mentions:
- Checking resources in Cluster: 1 under Pod: 1
<- Tries to find resources for the VM
- Looking for speed=500Mhz, Ram=1024
- Host name: xenserver, hostId: 1 is in avoid set, s
Hi,
that is the famous setup article from one of CloudStack conferences, if I'm
not mistaken - but since things have changed "a bit" during last 4 years
(both cloudstack and the XenServer versions), that means that probably some
steps might be missing (just a guess)
Anyway, since system VM is not
Sure – you can log bugs and feature requests on the official Jira board – just
make sure you open the ticket against the CloudStack project:
https://issues.apache.org/jira/secure/Dashboard.jspa
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 20/10/2017, 16:01, "Jevgeni Zolotarjov" wrote:
true, it does.
But for understanding the problem, I would have to
1. analyze the logs,
2. multiply [service offering core count] x [service offering MHz] and
3. check it against the remainder from the indicator on the dashboard.
Yes, it works that way too. But then I also have to
4. consider cpu.o
Agree the error could be clearer – but if you check your CloudStack dashboard
the pie chart for CPU already tells you your CPU utilisation.
You can also use the listCapacity API call mentioned before:
# cloudmonkey list capacity
count = 9
capacity:
+--+--
Thanks a lot!
It was it!
Actually the error reporting could be done in a wiser way to inform
administrator about what is the problem in particular. Do you know, where
can I request this feature?
Regards,
Jevgeni
On Fri, Oct 20, 2017 at 1:25 PM, Dag Sonstebo
wrote:
> Capacity type 1 is CPU: ht
Capacity type 1 is CPU:
http://cloudstack.apache.org/api/apidocs-4.10/apis/listCapacity.html
You would look at changing cluster.cpu.allocated.capacity.disablethreshold in
global settings – or the same under your cluster settings.
You can also play with cpu.overprovisioning.factor – but keep in
Ok, you decide, then)
20 окт. 2017 г. 17:16 пользователь "Jevgeni Zolotarjov" <
j.zolotar...@gmail.com> написал:
> I changed cluster.threshold.enabled to false. But it didn't help.
> I guess the root cause it something different.
>
> My storage capacity if above 3TB, and only under 300GB used.
>
I changed cluster.threshold.enabled to false. But it didn't help.
I guess the root cause it something different.
My storage capacity if above 3TB, and only under 300GB used.
No threshold setting was changed ever since installation.
On Fri, Oct 20, 2017 at 12:59 PM, Ivan Kudryavtsev wrote:
> Ju
Just look for threshold. Logs don't include such information.
2017-10-20 16:56 GMT+07:00 Jevgeni Zolotarjov :
> What is exact parameter name?
>
> On Fri, Oct 20, 2017 at 12:44 PM, Ivan Kudryavtsev <
> kudryavtsev...@bw-sw.com
> > wrote:
>
> > Ah, OK
> >
> > 2017-10-20 09:10:53,697 DEBUG [c.c.d.Fi
What is exact parameter name?
On Fri, Oct 20, 2017 at 12:44 PM, Ivan Kudryavtsev wrote:
> Ah, OK
>
> 2017-10-20 09:10:53,697 DEBUG [c.c.d.FirstFitPlanner]
> (API-Job-Executor-40:ctx-a4cff151 job-181 ctx-91a5717c) (logid:25e762a0)
> Cannot allocate cluster list [1] for vm creation since their all
Ah, OK
2017-10-20 09:10:53,697 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-40:ctx-a4cff151 job-181 ctx-91a5717c) (logid:25e762a0)
Cannot allocate cluster list [1] for vm creation since their allocated
percentage crosses the disable capacity threshold defined at each cluster/
at global value fo
Hi,
Yes I have one host. But I have exactly zero affinity group
s - I dont use affinity groups. I could successfully add few instances and
they are running.
The exceptions says: InsufficientServerCapacityException
But there is plenty of storage.
Disk Total 3.24 TB
Disk Allocated 265.33 GB
On Fri
Hi,
Yes I have one host. But I have exactly zero affinity groups. I could
successfully add few instances and they are running.
The
On Fri, Oct 20, 2017 at 12:35 PM, Ivan Kudryavtsev wrote:
> Hi,
> It seems you have one host and place several VMs in a single anti-affinity
> group, don't you? Th
Hi,
It seems you have one host and place several VMs in a single anti-affinity
group, don't you? This is how it should really work if you do that thing.
Anti-affinity groups are meaningless if you don't have several hosts.
2017-10-20 16:19 GMT+07:00 Jevgeni Zolotarjov :
> I could successfully cre
_1&apikey=oSiamYtTnncCNh8iJRiM-K5IpHqqJkryJiRSKKYCDkRoq9l_U0mzBGDQhGkYQ_pHBrrkNY0dM8B8t5gceov6MA&command=deployVirtualMachine&diskofferingid=db258461-8b03-4666-b6a8-d3459b0097ff&displayname=SRV212&domainid=c468ebec-2479-4897-a347-4bb96d63804d&name=srv212&response=json&
pleteMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2015-09-11 13:15:45,820 DEBUG [c.c.a.ApiServlet] (catalina-exec-3:ctx-cd5ff82c
ctx-9c7257a8 ctx-06e84516) ===END=== 172.10.10.221 -- GET
account=client_3_1&apikey=oSiamYtTnncCNh8iJRiM-K5IpHqqJkryJiRSKKYCDkRoq9l_U0mzBGDQ
rds,
Somesh
-Original Message-
From: Cristian Ciobanu [mailto:cristian.c@istream.today]
Sent: Thursday, September 10, 2015 2:25 PM
To: users@cloudstack.apache.org
Subject: RE: Unable to create a deployment for VM (Additional DATADISK -
API-job)
Hello,
Thanks for answer and suggestion ( is
hursday, September 10, 2015 2:25 PM
To: users@cloudstack.apache.org
Subject: RE: Unable to create a deployment for VM (Additional DATADISK -
API-job)
Hello,
Thanks for answer and suggestion ( is a testing environment )
Also i did a grep for the job-754, and i found more events about this
pr
@cloudstack.apache.org
Subject: RE: Unable to create a deployment for VM (Additional DATADISK -
API-job)
Hello,
Thanks for answer and suggestion ( is a testing environment )
Also i did a grep for the job-754, and i found more events about this
problem ( I use CS 4.5.2 with KVM on CentOS-6.6, Local
Hello,
Thanks for answer and suggestion ( is a testing environment )
Also i did a grep for the job-754, and i found more events about this
problem ( I use CS 4.5.2 with KVM on CentOS-6.6, Local Storage enabled,basic
network )
[root@mgcs management]# cat *.log | grep job-754
2015-09-10 1
Cristian,
First off, I would recommend masking information such as apikey, signature,
public IPs, etc. when posting on the list for security reasons.
The reason for failure as per logs is "InsufficientServerCapacityException"
however, from the logs snippets it is not possible to find the root c
Hosts are OK!
I've downgraded the comoute offering from "4*2.4GHZ and 8G RAM" to "2*2.4GHZ
and 4G RAM".
- Original Message -
From: "James Scott"
To:
Sent: Tuesday, October 07, 2014 12:10 PM
Subject: Re: Unable to create a deployment for
It looks like not enough CPU?
// Hosts's actual total CPU: 38384 and CPU after applying
overprovisioning: 307072
What is the Old and New Service Offering?
On Tue, Oct 7, 2014 at 10:31 AM, Amir Abbasi wrote:
> Hi,
>
> After changing the Service Offering I can't start the VM:
>
>
> 2014-10-07
This is happening using a Centos 6.5 netinstall. I just tried a debian 7.6
netinstall and the cd booted just fine. Would a bad .iso keep it from
creating a VM? If so I think that the VM should be created but not started
and notify the user of a bad CD.
-Original Message-
From: Matthew Mid
Can you share your management server logs .
-Original Message-
From: sandeep khandekar [mailto:cloudstack.sand...@gmail.com]
Sent: Friday, July 25, 2014 11:23 AM
To: users@cloudstack.apache.org
Subject: Unable to create a deployment for VM[User|
Dear ALL,
Got this error while creating an
original -
> De: "Francois Gaudreault"
> À: users@cloudstack.apache.org
> Cc: "Laurent Steff" , "Florent Paillot"
>
> Envoyé: Vendredi 7 Mars 2014 13:38:42
> Objet: Re: Unable to create a deployment for vm
>
> And also, you might want to look a couple
arting all cloudstack-agent or not ?
Regards,
Pierre
- Mail original -
> De: "Geoff Higginbottom"
> À: users@cloudstack.apache.org
> Cc: "Laurent Steff" , "Florent Paillot"
>
> Envoyé: Vendredi 7 Mars 2014 13:24:55
> Objet: RE: Unable to cre
And also, you might want to look a couple lines before the log snippet you
sent. The "real" answer will likely be there.
Francois
On Fri, Mar 7, 2014 at 7:24 AM, Geoff Higginbottom <
geoff.higginbot...@shapeblue.com> wrote:
> Pierre,
>
> Sometimes a host gets put into an 'avoid set' which means
Pierre,
Sometimes a host gets put into an 'avoid set' which means its not available for
new deployments.
One way of forcing CloudStack to re-evaluate hosts in avoid sets is to restart
the cloudstack management service
You say that resources all below thresholds, but would they be if this VM is
Hello Sabareesh,
The logs doesn't show the root cause of the problem you have seen on your
setup. The Insufficient Server Capacity Exception that you have seen might have
been thrown for the following reasons.
1. The host on which the VM previously resided on before stopping it, is no
longer
Can you grep for job-77 in the logs and see if there are any exceptions ?
On 28/03/13 12:42 PM, "Maurice Lawler" wrote:
>Attempting to create a VM from a template I created (Twice) getting this
>in my logs:
>
>013-03-28 02:07:17,873 WARN [cloud.api.ApiDispatcher]
>(Job-Executor-22:job-77) clas
It seems you have a cluster of management servers. It is possible that the
host/agents are owned by the the management server that is inactive:
2013-03-28 02:07:22,340 INFO [cloud.cluster.ClusterManagerImpl]
(Cluster-Heartbeat-1:null) Management node 1 is *detected inactive* by
timestamp but is p
38 matches
Mail list logo
