RE: Error on deployment

[Aldrin Leal]

look if your zipfile contents matches. plus, check the stack versoon. usually a visit to the forum helps

Sent from my Windows Phone

---

From: David
Sent: ‎3/‎10/‎2015 7:23 AM
To: beanstal...@googlegroups.com
Subject: Error on deployment

Hi, So I use mvn beanstalk:upload-source-bundle beanstalk:create-application-version when I do want to deploy a new version of my tomcat application to Elastic Beanstalk. When I deploy the version from the AWS console to my environment, I run into this error. Are container commands supposed to work using pom.xml? I haven't had any issues with the container commands I have when running a deployment without maven and beanstalker plugin.

2015-03-10 13:58:20 UTC+0200	ERROR	Update environment operation is complete, but with errors. For more information, see troubleshooting documentation.
2015-03-10 13:58:20 UTC+0200	INFO	New application version was deployed to running EC2 instances.
2015-03-10 13:58:18 UTC+0200	INFO	Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2015-03-10 13:58:18 UTC+0200	ERROR	[Instance: i-c18ed92e Module: AWSEBAutoScalingGroup ConfigSet: null] Command failed on instance. Return code: 1 Output: [CMD-AppDeploy/AppDeployStage0/EbExtensionPostBuild] command failed with error code 1: Error occurred during build: Command 08-restart opsview-agent failed.
2015-03-10 13:57:19 UTC+0200	INFO	Deploying new version to instance(s).

My question is, why is the container command failing? I have used this container command in the past without using maven and the Beanstalker plugin and has worked without issues.

The directory structure of my app.

/root/projects/<Project Name>

  -pom.xml

  -src

     >-main

     >-ebextensions

           -vpc.config           

           >-conf

           >-packages

           >-scripts

     >-java

     >-webapp

     -TestServlet.class

  >-target

My vpc.config file

---
container_commands:

 01-remove-old:

   command: "rm -rf /company/.ebextensions"

 02-make-company-dir:

   command: "mkdir -p /company/.ebextensions"

 03-copy-contents:

   command: "cp -R .ebextensions/* /company/.ebextensions/"

 04-convert-to-linux:

   command: "dos2unix -k /company/.ebextensions/scripts/setup.sh"

 05-make-runnable:

   command: "chmod 700 /company/.ebextensions/scripts/setup.sh"

 06-run-setup-only-once:

   command: "bash /company/.ebextensions/scripts/setup.sh"

   test: "test ! -f .semaphore_lock_only_once"

 07-restart-rsyslog:

   command: "/etc/init.d/rsyslog restart"

 08-restart opsview-agent:

   command: "/etc/init.d/opsview-agent restart"

 09-add company-monitor to boot:

   command: "/sbin/chkconfig --add company-monitor"

 10-turn company-monitor on:

   command: "/sbin/chkconfig company-monitor on"

 11-start company-monitor :

   command: "/etc/in

[The entire original message is not included.]