Re: Usage is not working | ACS 4.15

2022-07-12 Thread Vivek Kumar
Hello Daan,

Thanks for the response.

So we have deployed a replica of our management servers and databases  on a 
complete isolated environment, Tried a work around which you have suggested but 
PID is not getting updated in the usage_job. Usage.logs gets stuck on below 
logs - We have also tried to upgrade on 4.16 on the replica setup but same 
situation with 4.16 as well. 


2022-07-04 10:23:11,977 INFO  [cloud.usage.UsageManagerImpl] (main:null) 
(logid:) Implementation Version is 4.16.1.0
2022-07-11 04:26:23,905 DEBUG [utils.crypt.EncryptionSecretKeyChecker] 
(main:null) (logid:) Encryption Type: file
2022-07-11 04:26:23,927 INFO  [db.Transaction.Transaction] (main:null) (logid:) 
Is Data Base High Availiability enabled? Ans : true
2022-07-11 04:26:23,981 INFO  [db.Transaction.Transaction] (main:null) (logid:) 
The replicas configured for Cloud Data base is/are : 198.18.8.8
2022-07-11 04:26:24,014 DEBUG [utils.db.DriverLoader] (main:null) (logid:) 
Successfully loaded DB driver com.mysql.cj.jdbc.Driver
2022-07-11 04:26:24,063 DEBUG [utils.db.DriverLoader] (main:null) (logid:) DB 
driver com.mysql.cj.jdbc.Driver was already loaded.
2022-07-11 04:26:24,070 DEBUG [utils.db.DriverLoader] (main:null) (logid:) DB 
driver com.mysql.cj.jdbc.Driver was already loaded.
2022-07-11 04:26:25,172 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Setup Spring Application context
2022-07-11 04:26:25,616 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
org.apache.cloudstack.framework.config.dao.ConfigurationDaoImpl_EnhancerByCloudStack_b5109665
2022-07-11 04:26:25,616 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.user.dao.UserStatsLogDaoImpl_EnhancerByCloudStack_42da784f
2022-07-11 04:26:25,616 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.usage.dao.UsageVMSnapshotDaoImpl_EnhancerByCloudStack_bf461acb
2022-07-11 04:26:25,616 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.event.dao.UsageEventDaoImpl_EnhancerByCloudStack_a66084d9
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.domain.dao.DomainDaoImpl_EnhancerByCloudStack_35dea57c
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
org.apache.cloudstack.quota.dao.UserVmDetailsDaoImpl_EnhancerByCloudStack_7ec9190f
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.user.dao.SSHKeyPairDaoImpl_EnhancerByCloudStack_98c3bb86
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.usage.dao.UsageVmDiskDaoImpl_EnhancerByCloudStack_a3d9d9aa
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.user.dao.UserStatisticsDaoImpl_EnhancerByCloudStack_c06bb621
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
org.apache.cloudstack.quota.dao.QuotaUsageDaoImpl_EnhancerByCloudStack_82eb64e0
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.usage.dao.UsageVPNUserDaoImpl_EnhancerByCloudStack_95b19ecb
2022-07-11 04:26:25,617 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.event.dao.EventDaoImpl_EnhancerByCloudStack_6458895c
2022-07-11 04:26:25,618 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.usage.dao.UsageLoadBalancerPolicyDaoImpl_EnhancerByCloudStack_d545c0a0
2022-07-11 04:26:25,618 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.user.dao.UserAccountDaoImpl_EnhancerByCloudStack_ef2ae44f
2022-07-11 04:26:25,618 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.usage.dao.UsageStorageDaoImpl_EnhancerByCloudStack_39357dcf
2022-07-11 04:26:25,619 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.configuration.dao.ResourceCountDaoImpl_EnhancerByCloudStack_421ab841
2022-07-11 04:26:25,619 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
org.apache.cloudstack.quota.dao.QuotaBalanceDaoImpl_EnhancerByCloudStack_3d9daaed
2022-07-11 04:26:25,619 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.usage.dao.UsageVMInstanceDaoImpl_EnhancerByCloudStack_a3dbe792
2022-07-11 04:26:25,619 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
org.apache.cloudstack.quota.dao.QuotaEmailTemplatesDaoImpl_EnhancerByCloudStack_9f537032
2022-07-11 04:26:25,619 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_5b9ccd8c
2022-07-11 04:26:25,619 INFO  [utils.component.ComponentContext] (main:null) 
(logid:) Configuring 
com.cloud.usage

Re: Cloudstack NFS server installation issue

2022-07-12 Thread Vivek Kumar
Hello Bunmi,

That option is required when you install NFS on the management server, it’s 
clearly mentioned on the doc that - "using the management server as the nfs 
server". If you have separate node for NFS you can simply go - 

1- create two directories that you will use for primary and secondary storage. 
For example

# mkdir -p /export/primary
# mkdir -p /export/secondary

2- To configure the new directories as NFS exports, edit /etc/exports. Export 
the NFS share(s) with rw,async,no_root_squash,no_subtree_check. For example:

# vi /etc/exports

Insert the following line.
/export  *(rw,async,no_root_squash,no_subtree_check)

3- Export the /export directory.
exportfs -a

4- Restart your NFS server and do a test mount from your hypvervisor or from 
any other node

# mount -t nfs :/ /




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 11-Jul-2022, at 7:22 PM, Bunmi Adeleye  wrote:
> 
> Dear Team,
>  
> I’m new to cloudstack and trying to implement a POC. I have been able to 
> install cloudstack management server on Ubuntu VM. Currently I’m installing 
> NFS server on a separate node (Ubuntu OS) using the step by step guide 
> cloudstack documentation. Everything was fine until I got to step 5. I could 
> not locate /etc/sysconfig/nfs. My question is doI have to create the 
> directory ‘sysconfig’ and file ‘nfs’ afresh or how do I locate the path 
> specified in step 5. Kindly see below for reference.
> https://docs.cloudstack.apache.org/en/4.17.0.0/installguide/management-server/index.html#using-the-management-server-as-the-nfs-server
>  
> 
>  
> 
>  
> Please your advice is highly appreciated
>  
>  
>  
> Best regards,
>  
> Best regards,
> Bunmi Adeleye
> GM Technical Operations
> Syscodes Communications Ltd
> Tel: +234 8067480263
> Address: 3rd Floor, 19, Toyin Street, Ikeja, Lagos
> Website: www.syscodescomms.com 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.


Re: Cloudstack mgt server not connecting to the DB server

2022-07-12 Thread Vivek Kumar
Hello Bunmi,

Since your screenshot is visible on the mailing list. Pasting the logs would 
rather help much. But you can check few things, I am assuming that server 
reachability is not a problem at network level.

1- Is your management server able to login to data base server.  You can check 
using -h option, Run the command from your management server - > # mysql -uroot 
-p’’ -h;
2- have your mysql-setup-database command gave any errors ?


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 11-Jul-2022, at 9:38 PM, Bunmi Adeleye  wrote:
> 
> Dear Team,
>  
> I installed cloudstack management server successfully but could not launch 
> the home page via a web browser. I checked the logs and discovered that the 
> mgt. server could not connect to the database server as shown in below 
> screenshot. What is probably responsible for this? The mgt. server and the 
> database server were installed on separate Ubuntu OS nodes. Your response is 
> highly appreciated.
>  
> 
>  
> Best regards,
>  
> Best regards,
> Bunmi Adeleye
> GM Technical Operations
> Syscodes Communications Ltd
> Tel: +234 8067480263
> Address: 3rd Floor, 19, Toyin Street, Ikeja, Lagos
> Website: www.syscodescomms.com 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.


Cloudstack mgt server not connecting to the DB server

2022-07-12 Thread Bunmi Adeleye
Dear Team,

 

I installed cloudstack management server successfully but could not launch
the home page via a web browser. I checked the logs and discovered that the
mgt. server could not connect to the database server as shown in below
screenshot. What is probably responsible for this? The mgt. server and the
database server were installed on separate Ubuntu OS nodes. Your response is
highly appreciated.

 



 

Best regards,

 

Best regards,

Bunmi Adeleye

GM Technical Operations

Syscodes Communications Ltd

Tel: +234 8067480263

Address: 3rd Floor, 19, Toyin Street, Ikeja, Lagos

Website:   www.syscodescomms.com



 



Cloudstack NFS server installation issue

2022-07-12 Thread Bunmi Adeleye
Dear Team,

 

I'm new to cloudstack and trying to implement a POC. I have been able to
install cloudstack management server on Ubuntu VM. Currently I'm installing
NFS server on a separate node (Ubuntu OS) using the step by step guide
cloudstack documentation. Everything was fine until I got to step 5. I could
not locate /etc/sysconfig/nfs. My question is doI have to create the
directory 'sysconfig' and file 'nfs' afresh or how do I locate the path
specified in step 5. Kindly see below for reference.

https://docs.cloudstack.apache.org/en/4.17.0.0/installguide/management-serve
r/index.html#using-the-management-server-as-the-nfs-server 

 



 

Please your advice is highly appreciated

 

 

 

Best regards,

 

Best regards,

Bunmi Adeleye

GM Technical Operations

Syscodes Communications Ltd

Tel: +234 8067480263

Address: 3rd Floor, 19, Toyin Street, Ikeja, Lagos

Website:   www.syscodescomms.com



 



Re: Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

2022-07-12 Thread Vivek Kumar
Hello Oliver,

You will need to study the cloud-init. It works pretty well with all below 
mentioned OS. You can achieve a lot more then Hostname, Password and grow 
partition. You should use standard partition rather than LVM and there should 
be no portion after the root partition. Cloud-init will auto resize the 
partition if it finds any free sector in backend HDD.  You may also need to 
install few extra packages like - cloud-utils-growpart. Just have a look on the 
document. 

However, you can achieve same with Window’s instance as well. Cloud base-init 
works with windows and it provides the same functionality that way cloud-init 
provides with Linux OS.

Please find the link below - 

For Linux - 
https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart 




For Windows - 
https://cloudbase-init.readthedocs.io/en/latest/config.html#cloudstack 





Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 12-Jul-2022, at 10:02 PM, Olivier GUIN  wrote:
> 
> Hello Vivek,
> 
> Can you help me to create template with xcp-ng.
> 
> Debian, Ubuntu and CentOS, also hostname, password, it's OK but Grow 
> partition not !
> 
> Best regards,
> 
> Olivier
> 
> Le 12/07/2022 à 11:10, Vivek Kumar a écrit :
>> Hello Oliver,
>> 
>> 
>> Can you check the path of your vhd in DB and then check on your XenServer. 
>> If this is giving error for ROOT disk then mention the ROOT disk name and if 
>> it is data disk then mention the data disk name.
>> 
>> 1- select * from volumes where name = ‘ROOT-’; ( Note the PATH ).
>> 2- Go to your XenServer and search - xe vdi-list name-label = ‘ROOT-***’
>> 
>> Check if the UUID from above XenServer command is matching with the path 
>> from DB. If not then try to manually update the path ( Note the UUID from xe 
>> vdi-list command and update in the volume table for that disk ).
>> 
>> 
>> 
>> 
>> Vivek Kumar
>> Sr. Manager - Cloud & DevOps
>> TechOps | Indiqus Technologies
>> 
>> vivek.ku...@indiqus.com  
>> >
>>  www.indiqus.com  > >
>> 
>> 
>> 
>> 
>>> On 12-Jul-2022, at 7:16 PM, Olivier GUIN 
>>>  wrote:
>>> 
>>> New message !
>>> 
>>> 2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
>>> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start i-40-76-VM 
>>> due to
>>> The uuid you supplied was invalid.
>>> 
>>> 2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
>>> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD due 
>>> to
>>> You gave an invalid object reference. The object may have recently been 
>>> deleted. The class parameter gives the type of reference given, and the 
>>> handle parameter echoes the bad value given.
>>> 
>>> ?
>>> 
>>> Le 12/07/2022 à 09:16, Olivier GUIN a écrit :
 Hi there,
 
 I have a message 'Unable to start a VM due to insufficient capacity'I 
 can't find the problem.
 
 I have this problem on only 2 VMs!
 
 2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Unexpected 
 exception while executing 
 org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
 com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due 
 to insufficient capacity
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
 at jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
 at 
 java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
 at 
 org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java

[SOLVE] Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

2022-07-12 Thread Olivier GUIN

Hello Vivek,

It's OK now,

Thank's a lot

Olivier

Le 12/07/2022 à 11:10, Vivek Kumar a écrit :


Hello Oliver,


Can you check the path of your vhd in DB and then check on your XenServer. If 
this is giving error for ROOT disk then mention the ROOT disk name and if it is 
data disk then mention the data disk name.

1- select * from volumes where name = ‘ROOT-’; ( Note the PATH ).
2- Go to your XenServer and search - xe vdi-list name-label = ‘ROOT-***’

Check if the UUID from above XenServer command is matching with the path from 
DB. If not then try to manually update the path ( Note the UUID from xe 
vdi-list command and update in the volume table for that disk ).




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 





On 12-Jul-2022, at 7:16 PM, Olivier GUIN  
wrote:

New message !

2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start i-40-76-VM due 
to
The uuid you supplied was invalid.

2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD due to
You gave an invalid object reference.  The object may have recently been 
deleted.  The class parameter gives the type of reference given, and the handle 
parameter echoes the bad value given.

?

Le 12/07/2022 à 09:16, Olivier GUIN a écrit :

Hi there,

I have a message 'Unable to start a VM due to insufficient capacity'I can't 
find the problem.

I have this problem on only 2 VMs!

2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Unexpected 
exception while executing 
org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
 at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
 at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
 at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
 at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
 at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
 at jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown 
Source)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
 at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
 at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
 at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
 at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
 at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
 at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
 at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
 at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
 at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
 at 
org.apache.cloudstack.framework.jo

Re: Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

2022-07-12 Thread Vivek Kumar
Hello Oliver, 


Can you check the path of your vhd in DB and then check on your XenServer. If 
this is giving error for ROOT disk then mention the ROOT disk name and if it is 
data disk then mention the data disk name.

1- select * from volumes where name = ‘ROOT-’; ( Note the PATH ).
2- Go to your XenServer and search - xe vdi-list name-label = ‘ROOT-***’

Check if the UUID from above XenServer command is matching with the path from 
DB. If not then try to manually update the path ( Note the UUID from xe 
vdi-list command and update in the volume table for that disk ).




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 12-Jul-2022, at 7:16 PM, Olivier GUIN  
> wrote:
> 
> New message !
> 
> 2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start i-40-76-VM 
> due to
> The uuid you supplied was invalid.
> 
> 2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD due to
> You gave an invalid object reference.  The object may have recently been 
> deleted.  The class parameter gives the type of reference given, and the 
> handle parameter echoes the bad value given.
> 
> ?
> 
> Le 12/07/2022 à 09:16, Olivier GUIN a écrit :
>> Hi there,
>> 
>> I have a message 'Unable to start a VM due to insufficient capacity'I can't 
>> find the problem.
>> 
>> I have this problem on only 2 VMs!
>> 
>> 2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
>> (API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Unexpected 
>> exception while executing 
>> org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
>> com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
>> insufficient capacity
>> at 
>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
>> at 
>> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
>> at 
>> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
>> at 
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
>> at 
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
>> at jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown 
>> Source)
>> at 
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>> at 
>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
>> at 
>> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
>> at 
>> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
>> at 
>> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
>> at 
>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
>> at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
>> at 
>> org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)
>> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
>> at 
>> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
>> at 
>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
>> at 
>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
>> at 
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
>> at 
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
>> at 
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
>> at 
>> org.apache.cloudstack.managed.context

Re: Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

2022-07-12 Thread Olivier GUIN

New message !

2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start 
i-40-76-VM due to

The uuid you supplied was invalid.

2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD 
due to
You gave an invalid object reference.  The object may have recently been 
deleted.  The class parameter gives the type of reference given, and the 
handle parameter echoes the bad value given.


?

Le 12/07/2022 à 09:16, Olivier GUIN a écrit :

Hi there,

I have a message 'Unable to start a VM due to insufficient capacity'I 
can't find the problem.


I have this problem on only 2 VMs!

2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) 
Unexpected exception while executing 
org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM 
due to insufficient capacity
    at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
    at 
jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
    at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
    at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
    at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)

    at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
    at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)

    at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
    at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
    at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

    at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.cloud.exception.InsufficientServerCapacityException: 
Unable to create a deployment for VM[User|i-40-76-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1119)
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5502)
    at 
jdk.internal.reflect.GeneratedMethodAccessor908.inv

Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

2022-07-12 Thread Olivier GUIN

Hi there,

I have a message 'Unable to start a VM due to insufficient capacity'I 
can't find the problem.


I have this problem on only 2 VMs!

2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) 
Unexpected exception while executing 
org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM 
due to insufficient capacity
    at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
    at 
jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
    at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
    at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
    at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)

    at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
    at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)

    at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
    at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
    at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

    at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.cloud.exception.InsufficientServerCapacityException: 
Unable to create a deployment for VM[User|i-40-76-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1119)
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5502)
    at 
jdk.internal.reflect.GeneratedMethodAccessor908.invoke(Unknown Source)

    ... 17 more
2022-07-12 09:00:10,694 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Complete 
async job-462574, 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"}


Can someone help me?

Best regards,
Olivier