Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sandeep.patni@cumulogic.com
 designates 216.32.180.30 as permitted sender)
Received-SPF: pass (mail181-va3: domain of cumulogic.com designates
 157.56.241.5 as permitted sender) client-ip=157.56.241.5;
 envelope-from=sandeep.patni@cumulogic.com;
 helo=BL2PRD0811HT004.namprd08.prod.outlook.com ;.outlook.com ;
From: Sandeep Patni <sandeep.patni@cumulogic.com>
To: "cloudstack-users@incubator.apache.org"
	<cloudstack-users@incubator.apache.org>
Subject: RE: Getting "504 Gateway Time-out. The server didn't respond in
 time" error while making multiple enableStaticNat calls in parallel on
 CloudStack 3.0.5.
Thread-Topic: Getting "504 Gateway Time-out. The server didn't respond in
 time" error while making multiple enableStaticNat calls in parallel on
 CloudStack 3.0.5.
Thread-Index: Ac4g5fnObV5aIVEFQ7yMwllycGT2kAACG3/gAALynvAA7enwEA==
Date: Tue, 19 Mar 2013 14:57:03 +0000
Message-ID: 
 <275CAEC988899B4583AA806F3BAA9A9C19DE0023@BL2PRD0811MB410.namprd08.prod.outlook.com>
References: 
 <275CAEC988899B4583AA806F3BAA9A9C19DDEB86@BL2PRD0811MB410.namprd08.prod.outlook.com>
 <4AD15F3FB0BD7A4EA1B53E9A093921E5A4E68E27@DSSEMAIL1.dsscorp.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Just checking if anyone has seen this issue and has any suggestions.

-----Original Message-----
From: Sandeep Patni=20
Sent: Thursday, March 14, 2013 5:25 PM
To: cloudstack-users@incubator.apache.org
Subject: RE: Getting "504 Gateway Time-out. The server didn't respond in ti=
me" error while making multiple enableStaticNat calls in parallel on CloudS=
tack 3.0.5.

Yes, that is correct. Each instance is getting it's own public ip and we ar=
e setting up static-nat and firewall rules etc.

-----Original Message-----
From: Brandon Arms [mailto:BArms@dsscorp.com]=20
Sent: Thursday, March 14, 2013 4:02 PM
To: cloudstack-users@incubator.apache.org
Subject: RE: Getting "504 Gateway Time-out. The server didn't respond in ti=
me" error while making multiple enableStaticNat calls in parallel on CloudS=
tack 3.0.5.

Sandeep

Is it safe to assume you are using a different ipaddressid for each vm stat=
ic nat?

Brandon Arms
-----Original Message-----
From: Sandeep Patni [mailto:sandeep.patni@cumulogic.com]=20
Sent: Thursday, March 14, 2013 3:02 PM
To: cloudstack-users@incubator.apache.org
Subject: Getting "504 Gateway Time-out. The server didn't respond in time" =
error while making multiple enableStaticNat calls in parallel on CloudStack=
 3.0.5.


Hi,


We are provisioning VM instances and configuring staticNat via API on one o=
f the cloudstack 3.0.5 cloud. When we provision a single vm instance it wor=
ks fine. But while provisioning 3 or more instances in parallel, we get 504=
 Gateway Time-out error. We noticed that the VMs get created, but the error=
 occurs in enableStaticNat API.

Any pointers what could be causing this ?

The cloudstack version is cloud-stack-version=3D"3.0.5.20120904142539"


Error in our log:

CloudStack service failed to create instance.Error executing CloudStack API=
, reason - <html><body><h1>504 Gateway Time-out</h1> The server didn't resp=
ond in time. </body></html>

... 6 more
Caused by: java.lang.Exception: Error executing CloudStack API, reason - <h=
tml><body><h1>504 Gateway Time-out</h1> The server didn't respond in time. =
</body></html>


Thanks
Sandeep