Could Anyone help to identified which setting should I change to fix
this error ? Thanks
2015-10-14 14:11:31,615 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-4164dc8b) ===START=== 10.0.16.102 -- POST
command=addCluster&zoneId=a8ac4174-634f-4d3f-b5b8-279069bec599&hypervisor=VMware&cluste
Ok, I will make some deep research.
I will let you know, a.s.a.p.
On Oct 14, 2015 00:21, "Somesh Naidu" wrote:
> Ilya, the operation SEQ is based on the host (also referred to as agent).
> So, this concurrency isn't at the object level but at the host/agent level.
>
> In this case, I believe it i
Please provide some more details
1) Type of networking used?
2) Tagged or untagged networking?
3) From where you are using Hyper-V agent?
4) CloudStack version
> On 08-Oct-2015, at 11:34 PM, Yousri Farouk
> wrote:
>
>
> Kindly I followed
> (http://cloudstack-installation.readthedocs.org/en/
No problem, you are welcome. It is nice to heat that worked for you.
Sometimes, it is easier to know how things work looking at the source code
directly.
On Tue, Oct 13, 2015 at 9:37 PM, Ryan Farrington
wrote:
> Confirmed. We migrated a few TB worth of volumes without issue. Thanks
> for help
Confirmed. We migrated a few TB worth of volumes without issue. Thanks for
helping nail this down!
From: Rafael Weingärtner [rafaelweingart...@gmail.com]
Sent: Tuesday, October 13, 2015 6:12 PM
To: users@cloudstack.apache.org
Subject: [Questionable] Re
Nice, thanks.
Did that solve your problem? Did you migrate the volume?
On Tue, Oct 13, 2015 at 7:00 PM, Ryan Farrington
wrote:
> Issue #1) Terrible parameter names
> https://issues.apache.org/jira/browse/CLOUDSTACK-8946
>
> Issue #2) Wait value for MigrateVolume
> https://issues.apache.org/jira/
Issue #1) Terrible parameter names
https://issues.apache.org/jira/browse/CLOUDSTACK-8946
Issue #2) Wait value for MigrateVolume
https://issues.apache.org/jira/browse/CLOUDSTACK-8949
From: Rafael Weingärtner [rafaelweingart...@gmail.com]
Sent: Tuesday, Oc
Thanks for clarification.
Nux! wrote
>Cristian,
>
>That's because the UI is behind with this feature (especially as it's only
>supported on KVM).
>You can do it from cloudmonkey with the machine shut down (ideally), e.g.
>resize volume id=5cbb6528-9ebe-4884-aaf3-40451897352f size=320
Ilya, the operation SEQ is based on the host (also referred to as agent). So,
this concurrency isn't at the object level but at the host/agent level.
In this case, I believe it is SSVM. Have Emil verify this from host table
querying for the ID in the SEQ.
Regards,
Somesh
-Original Message
Somesh,
Not certain how that is going to help the problem with concurrent
tasks.. Please explain..
Thanks,
ilya
On 10/13/15 1:58 PM, Somesh Naidu wrote:
> Can you check what value is set for global configuration parameter
> "vmware.create.full.clone"? If false, try setting it to true and see if
Can you check what value is set for global configuration parameter
"vmware.create.full.clone"? If false, try setting it to true and see if that
works.
Regards,
Somesh
-Original Message-
From: Emil [mailto:emi...@gmail.com]
Sent: Tuesday, October 13, 2015 3:08 PM
To: users@cloudstack.ap
Hi Emil,
I believe there are some restrictions on how migration is handled with
vmware.
Please explain from resource standpoint what you are running and how
test is made..
i.e. how many hosts and datastores in your cluster and how tests are made..
Example:
Test 1 Source: vm1, host 1, datastore1
That is good. Now I can report to you what is in the code.
Let’s start:
First: when I looked at the problem at first time, I went straight to the
class that sends commands to Xen, and there the ACs uses a parameter
called: “migratewait” to control the timeout of command. You tried that,
and you st
Looks like whatever change I made actually resulted in a change in behavior.
Prior to the change we were seeing a message every hour stating that the job
agent was waiting now we see it waited 2hours and 8 minutes without a peep
before finishing. So making the change to the "wait" parameter is
Cristian,
That's because the UI is behind with this feature (especially as it's only
supported on KVM).
You can do it from cloudmonkey with the machine shut down (ideally), e.g.
resize volume id=5cbb6528-9ebe-4884-aaf3-40451897352f size=320
The size is given in Gigabytes.
--
Sent from the Delta
Hello,
I use 4.5 but I don't find option to resize from the cloudstack Admin UI
Thanks,
Cristian
Nux! wrote
>Cristian,
>
>Which version are you running? Root volume support is a relatively recent
>feature. I think 4.4.
>
>--
>Sent from the Delta quadrant using Borg technolog
Cristian,
Which version are you running? Root volume support is a relatively recent
feature. I think 4.4.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Cristian Ciobanu"
> To: users@cloudstack.apache.org
> Sent: Tuesday, 13 Octobe
Hello,
We have a big problem in our environment which not letting us keep working.
We are trying to use the command migrateVolume which is written as
asynchronous in cloudstack API.
But in some way every time we try to run the command (through the API or
Web)
only 1x migration running at a time (
Yeah
I'm sorry guys, enabling a STATIC NAT resolve my issue! :)
By
On Tue, Oct 13, 2015 at 8:43 PM, Alessandro Caviglione <
c.alessan...@gmail.com> wrote:
> Hi guys,
> I'd like to know if it's possible to change Source NAT for a specific
> server/IP.
> I'm running ACS 4.4.4 with XS6.2SP1
Hi guys,
I'd like to know if it's possible to change Source NAT for a specific
server/IP.
I'm running ACS 4.4.4 with XS6.2SP1 with Advanced Network.
I'm having some issue with a cPanel instance with multiple public IP.
I made some port forwarding from the Public IPs to the primary and
secondary cPa
You should be able to do it with resizevolume API
https://cloudstack.apache.org/api/apidocs-4.5/user/resizeVolume.html
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support
On Tue, Oct 13, 2015 at 5:11 PM, Cristian Ciobanu
wrote:
> Hello,
>
>How can i re-size the roo
Hello,
How can i re-size the root volume for a linux vm ?
For hypervisor i use KVM ( cloudstack )
Regards,
Cristian
Let’s wait to see if there is nothing else messing with that timeout. Then
I send you the details to put into the Jira ticket.
On Tue, Oct 13, 2015 at 10:06 AM, Ryan Farrington wrote:
> Rafael,
> I am still a bit confused as to what you would like for me to place in
> the JIRA ticket. I hav
Hi Timothy,
Thanks for your help. I had already conducted all the possible
troubleshooting techniques before dropping an email to the group.
I was able to resolve the issue few minutes back by dropping the cloud mysql db
and restoring it with the last working copy.
--
best wishes,
Thomas Jos
Rafael,
I am still a bit confused as to what you would like for me to place in the
JIRA ticket. I have adjusted the "wait" parameter and will be able to test it
in about an hour. But i would think the JIRA ticket should be as detailed as I
can make it or will you be adding details once I h
I guess so, for some reason that I do not understand, the code is
multiplying the value from that parameter by 2, something like 18000 should
do the tricky
On Tue, Oct 13, 2015 at 12:15 AM, Ryan Farrington wrote:
> Yes i can open JIRA tickets. What would you like for me to do?
>
> I'll be happy
Hi Thomas,
I had a similar scenario (albeit not a crashed SS Server). My SS is using NFS,
server went down due to FC failure.
1. Confirm that the SS is online and reachable - Test with external mount etc.
2. Check out
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secon
Hi All,
I'm facing a peculiar issue with my cloudstack setup.
1. My Storage server crashed last night and my SSVM was destroyed
automatically.
2. After resolving the hardware issues, I find that my systemvm template is in status
"Timeout waiting for response from storage host".
My clou
Thank you Giles!!
Thank you,
Suneel Mallela
From: Giles Sirett
Sent: Tuesday, October 13, 2015 5:15 PM
To: users@cloudstack.apache.org
Cc: Erik Weber
Yes
Erik (in CC) is moving forward with this
Regards
Giles
-Original Message-
From: mvs babu [mailto:mvsbabu0
Yes
Erik (in CC) is moving forward with this
Regards
Giles
-Original Message-
From: mvs babu [mailto:mvsbabu0...@outlook.com]
Sent: 06 October 2015 06:26
To: users@cloudstack.apache.org
Subject: Re: CloudStack Users survey
Hi,
Any one looking into this?
Thank you,
Suneel Mallel
Hi Ryan,
we hit the same problem few days ago. After we changed parameters:
migratewait, storage.pool.max.waitseconds, vm.op.cancel.interval and
vm.op.cleanup.wait to 36000 (10h) we can migrate large volumes (500GB
and more).
We use xenserver 6.5 and ACS 4.5.1
Regards,
Kuba
W dniu 2015-10-13
31 matches
Mail list logo
