Rob, silly question Have you tried splitting the install from launching.
Initally I was building my blueprints like you did until I came across the gitlab example in the blueprint library (L79-110) https://github.com/brooklyncentral/blueprint-library/blob/b8ce11a26cffa72a0fd27d131475a6eeb4cdad09/gitlab-w-postgresql-redis-store-and-nginx.yaml I use the install.command to install binaries and wrap them into services I want and then the launch.command to start the services, and the stop.command to stop them. Brooklyn will automatically use the checkRunning.command until the service is up Arno -----Original Message----- From: Robert Moss [mailto:[email protected]] Sent: Tuesday, February 09, 2016 9:19 AM To: [email protected] Subject: Re: VanillaSoftwareProcess install failing - any ideas? Well, it seems to be a problem with the AWS ubuntu image only, works elsewhere. Robert On 9 February 2016 at 13:47, Robert Moss <[email protected]> wrote: > Hi, > > I'm trying to run a VanillaSoftwareProcess with the install script at > [1], but L23 seems to exit the script with the return code 1. We've > tried a few things but can't come up with any reason why this might > be. Has anyone seen this before or know why this might be happening? > > Robert > > [1] > https://github.com/alien4cloud/samples/blob/master/mongo/scripts/insta > ll-mongo.sh#L23 > ******************************************************************************************************************************** ******************************************************************************************************************************** This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail, and delete the message, or call +1-613-576-2480. ******************************************************************************************************************************** ********************************************************************************************************************************
