or Create a profile

Home → Suggestions →

Failed S3 deployment should have better error message, i.e. not complain about missing memcached.yml

André Wendt's Avatar

André Wendt

17 Apr, 2012 11:56 AM

Hi,

we tried to deploy from S3 yesterday. The deployment failed, complaining about a missing memcached.yml. After a lot of debugging, we found out that we provided the wrong URL for the deployment—the bucket had a policy requiring secureTransport: true while we typed in the HTTP URL.

An error message like "Can't download app tarball from http://..." would have saved us a lot of time. (Apparently, s3curl does not report errors by default. That resulted in an XML response from S3 being written to disk which in turn was unzipped during deployment.)

Thanks,
André

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

1 person watching.

  • New Issue

  • Conversation Started

    A conversation has been started with the Peritor Scalarium staff to resolve this discussion.

  • Close the discussion

Recent Discussions

14 Jan, 2011 06:04 PM HAProxy Cookbook Questions
10 Jul, 2012 05:35 PM wordpress uploads files to shared/wp-content/uploads but doesn't have permissions
08 May, 2013 12:07 PM how to use AWS Elastic Load Balancer (ELB) instead of HAproxy
16 Mar, 2011 10:16 PM Suggesting Scalarium provide a community-maintained wiki of HOWTOs

Recent Articles

Update and Delete Applications
Update and Delete Clouds
Creating Roles
Creating Clouds
Creating, Starting, Stopping and Rebooting Instances