java - is beanstalk plugin deploy nothing to aws elb? -
i'm trying deploy war file aws elb. in logs can see that:
war file uploaded s3 new application created elb environment replacedbut in aws log can't see actions application...
pom.xml:
<plugin> <groupid>br.com.ingenieux</groupid> <artifactid>beanstalk-maven-plugin</artifactid> <version>1.3.5</version> <configuration> <environmentname>my</environmentname> <cnameprefix>my</cnameprefix> <s3bucket>archive-for-elb</s3bucket> <s3key>${project.build.finalname}-${maven.build.timestamp}.war</s3key> <artifactfile>target/my.war</artifactfile> </configuration> </plugin> maven log:
[info] [info] --- beanstalk-maven-plugin:1.3.5:upload-source-bundle (default-cli) @ --- [info] target path: s3://archive-for-elb/my-0.1.0-2014-10-23t22:21:21z.war [info] uploading artifact file: .../my.war 100.00% 29 mib/29 mib done [info] artifact uploaded [info] success [info] [info] --- beanstalk-maven-plugin:1.3.5:create-application-version (default-cli) @ --- [info] success [info] * datecreated: fri oct 24 01:21:39 fet 2014 [class: date] [info] * sourcebundle: {s3bucket: archive-for-elb,s3key: my-0.1.0-2014-10-23t22:21:21z.war} [class: s3location] [info] * versionlabel: 0.1.0 [class: string] [info] * description: update beanstalk-maven-plugin [class: string] [info] * applicationname: [class: string] [info] * dateupdated: fri oct 24 01:21:39 fet 2014 [class: date] [info] [info] --- beanstalk-maven-plugin:1.3.5:replace-environment (default-cli) @ --- [info] creating new environment on my-0.elasticbeanstalk.com [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:aws_secret_key[''] [info] excluding alternative setting: aws:cloudformation:template:parameter:appsource['http://s3-eu-west-1.amazonaws.com/elasticbeanstalk-samples-eu-west-1/elasticbeanstalk-sampleapp.war'] [info] including alternative setting: aws:elasticbeanstalk:container:tomcat:jvmoptions:xmx['1024m'] [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:aws_access_key_id[''] [info] excluding alternative setting: aws:elasticbeanstalk:container:tomcat:jvmoptions:jvm options[''] [info] including alternative setting: aws:cloudformation:template:parameter:jvmoptions['jvm options=,xx:maxpermsize=128m,xmx=1024m,xms=512m'] [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:param1[''] [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:param2[''] [info] including alternative setting: aws:cloudformation:template:parameter:instanceport['80'] [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:param4[''] [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:param3[''] [info] including alternative setting: aws:cloudformation:template:parameter:environmentvariables['param3=,param4=,param1=,param2=,jdbc_connection_string=,aws_secret_key=,param5=,aws_access_key_id='] [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:param5[''] [info] including alternative setting: aws:elasticbeanstalk:hostmanager:logpublicationcontrol['false'] [info] including alternative setting: aws:elasticbeanstalk:container:tomcat:jvmoptions:xx:maxpermsize['128m'] [info] including alternative setting: aws:elasticbeanstalk:container:tomcat:jvmoptions:xms['512m'] [info] including alternative setting: aws:autoscaling:launchconfiguration:instancetype['m1.small'] [info] excluding alternative setting: aws:elasticbeanstalk:application:environment:jdbc_connection_string[''] [info] including alternative setting: aws:elb:loadbalancer:crosszone['false'] [info] including alternative setting: aws:elb:healthcheck:interval['30'] [info] including alternative setting: aws:elb:loadbalancer:loadbalancerhttpsport['off'] [info] including alternative setting: aws:elb:healthcheck:timeout['5'] [info] excluding alternative setting: aws:elb:loadbalancer:sslcertificateid[''] [info] including alternative setting: aws:elb:healthcheck:unhealthythreshold['5'] [info] excluding alternative setting: aws:ec2:vpc:elbsubnets[''] [info] including alternative setting: aws:elb:policies:stickiness policy['false'] [info] including alternative setting: aws:elb:policies:connectiondrainingtimeout['20'] [info] including alternative setting: aws:elb:loadbalancer:loadbalancerportprotocol['http'] [info] including alternative setting: aws:elb:loadbalancer:loadbalancersslportprotocol['https'] [info] including alternative setting: aws:elb:healthcheck:target['tcp:80'] [info] including alternative setting: aws:elb:policies:stickiness cookie expiration['0'] [info] including alternative setting: aws:elb:healthcheck:healthythreshold['3'] [info] including alternative setting: aws:elb:policies:connectiondrainingenabled['false'] [info] including alternative setting: aws:ec2:vpc:elbscheme['public'] [info] including alternative setting: aws:elb:loadbalancer:loadbalancerhttpport['80'] [info] including alternative setting: aws:autoscaling:launchconfiguration:imageid['ami-937474e7'] [info] including alternative setting: aws:autoscaling:launchconfiguration:monitoringinterval['5 minute'] [info] excluding alternative setting: aws:autoscaling:launchconfiguration:securitygroups['awseb-e-5dguwgvhms-stack-awsebsecuritygroup-16adzataghya2'] [info] excluding alternative setting: aws:autoscaling:launchconfiguration:rootvolumetype[''] [info] excluding alternative setting: aws:autoscaling:launchconfiguration:iaminstanceprofile[''] [info] excluding alternative setting: aws:autoscaling:launchconfiguration:rootvolumesize[''] [info] excluding alternative setting: aws:autoscaling:launchconfiguration:blockdevicemappings[''] [info] excluding alternative setting: aws:autoscaling:launchconfiguration:ec2keyname[''] [info] excluding alternative setting: aws:autoscaling:launchconfiguration:rootvolumeiops[''] [info] excluding alternative setting: aws:ec2:vpc:associatepublicipaddress[''] [info] including alternative setting: aws:autoscaling:asg:maxsize['4'] [info] including alternative setting: aws:autoscaling:asg:cooldown['360'] [info] including alternative setting: aws:autoscaling:asg:minsize['1'] [info] including alternative setting: aws:autoscaling:asg:availability zones['any'] [info] excluding alternative setting: aws:autoscaling:updatepolicy:rollingupdate:mininstancesinservice[''] [info] including alternative setting: aws:autoscaling:updatepolicy:rollingupdate:rollingupdateenabled['false'] [info] excluding alternative setting: aws:autoscaling:asg:custom availability zones[''] [info] excluding alternative setting: aws:ec2:vpc:subnets[''] [info] excluding alternative setting: aws:autoscaling:updatepolicy:rollingupdate:maxbatchsize[''] [info] excluding alternative setting: aws:autoscaling:updatepolicy:rollingupdate:pausetime[''] [info] excluding alternative setting: aws:ec2:vpc:vpcid[''] [info] including alternative setting: aws:autoscaling:trigger:upperthreshold['6000000'] [info] including alternative setting: aws:autoscaling:trigger:period['5'] [info] including alternative setting: aws:autoscaling:trigger:statistic['average'] [info] including alternative setting: aws:autoscaling:trigger:measurename['networkout'] [info] including alternative setting: aws:autoscaling:trigger:lowerthreshold['2000000'] [info] including alternative setting: aws:autoscaling:trigger:evaluationperiods['1'] [info] including alternative setting: aws:autoscaling:trigger:unit['bytes'] [info] including alternative setting: aws:autoscaling:trigger:breachduration['5'] [info] including alternative setting: aws:autoscaling:trigger:lowerbreachscaleincrement['-1'] [info] including alternative setting: aws:autoscaling:trigger:upperbreachscaleincrement['1'] [info] including alternative setting: aws:elasticbeanstalk:control:rollbacklaunchonfailure['false'] [info] including alternative setting: aws:elasticbeanstalk:control:defaultsshport['22'] [info] including alternative setting: aws:elasticbeanstalk:control:launchtype['migration'] [info] including alternative setting: aws:elasticbeanstalk:monitoring:automatically terminate unhealthy instances['true'] [info] including alternative setting: aws:elasticbeanstalk:control:launchtimeout['0'] [info] including alternative setting: aws:elasticbeanstalk:environment:environmenttype['loadbalanced'] [info] including alternative setting: aws:autoscaling:launchconfiguration:sshsourcerestriction['tcp,22,22,0.0.0.0/0'] [info] excluding alternative setting: aws:elasticbeanstalk:sns:topics:notification topic arn[''] [info] excluding alternative setting: aws:elasticbeanstalk:sns:topics:notification endpoint[''] [info] including alternative setting: aws:elasticbeanstalk:command:batchsize['100'] [info] including alternative setting: aws:elasticbeanstalk:command:timeout['600'] [info] excluding alternative setting: aws:elasticbeanstalk:application:application healthcheck url[''] [info] excluding alternative setting: aws:elasticbeanstalk:sns:topics:notification topic name[''] [info] including alternative setting: aws:elasticbeanstalk:sns:topics:notification protocol['email'] [info] including alternative setting: aws:elasticbeanstalk:command:batchsizetype['percentage'] [info] , it'll named my-0 [info] using latest available application version 0.1.0 [info] environment lookup [info] ... environmentid equal 'e-wt6wzxjpyj' [info] ... status set 'ready' [info] ... health equal 'green' [info] info fri oct 24 01:21:48 fet 2014 using elasticbeanstalk-eu-west-1-896684893807 amazon s3 storage bucket environment data. [info] info fri oct 24 01:22:02 fet 2014 created load balancer named: awseb-e-w-awsebloa-ws5l7g9xb5xu [info] info fri oct 24 01:22:23 fet 2014 created security grouping named: awseb-e-wt6wzxjpyj-stack-awsebsecuritygroup-ut0k8k743bwj [info] info fri oct 24 01:22:26 fet 2014 created auto scaling launch configuration named: awseb-e-wt6wzxjpyj-stack-awsebautoscalinglaunchconfiguration-onmfrqkqfvf1 [info] info fri oct 24 01:23:24 fet 2014 created auto scaling grouping named: awseb-e-wt6wzxjpyj-stack-awsebautoscalinggroup-1glbecapxkowg [info] info fri oct 24 01:23:28 fet 2014 created auto scaling grouping policy named: arn:aws:autoscaling:eu-west-1:896684893807:scalingpolicy:315fb3b8-e461-441d-8d8d-5aa9e9e09f40:autoscalinggroupname/awseb-e-wt6wzxjpyj-stack-awsebautoscalinggroup-1glbecapxkowg:policyname/awseb-e-wt6wzxjpyj-stack-awsebautoscalingscaleuppolicy-iuq473krvy73 [info] info fri oct 24 01:23:28 fet 2014 created auto scaling grouping policy named: arn:aws:autoscaling:eu-west-1:896684893807:scalingpolicy:96912dc4-b9ac-4c47-9d76-99ef4087600e:autoscalinggroupname/awseb-e-wt6wzxjpyj-stack-awsebautoscalinggroup-1glbecapxkowg:policyname/awseb-e-wt6wzxjpyj-stack-awsebautoscalingscaledownpolicy-1hpvbp4235ci2 [info] info fri oct 24 01:23:31 fet 2014 created cloudwatch alarm named: awseb-e-wt6wzxjpyj-stack-awsebcloudwatchalarmhigh-1b5fqs201rin7 [info] info fri oct 24 01:23:32 fet 2014 created cloudwatch alarm named: awseb-e-wt6wzxjpyj-stack-awsebcloudwatchalarmlow-v2im7cxm1xr0 [info] waiting environmentid e-wt6wzxjpyj ready state [info] environment lookup [info] ... environmentid equal 'e-wt6wzxjpyj' [info] ... status set 'ready' [info] ... health equal 'green' [info] swapping environment cnames e-wt6wzxjpyj , e-5dguwgvhms [info] skipping r53 domain binding [info] environment lookup [info] ... environmentid equal 'e-wt6wzxjpyj' [info] ... status set 'ready' [info] terminating environmentid=e-5dguwgvhms (attempt 1/15) [info] success [info] * solutionstackname: 32bit amazon linux running tomcat 7 [class: string] [info] * description: [class: string] [info] * health: gray [class: string] [info] * dateupdated: fri oct 24 01:21:44 fet 2014 [class: date] [info] * datecreated: fri oct 24 01:21:44 fet 2014 [class: date] [info] * environmentid: e-wt6wzxjpyj [class: string] [info] * versionlabel: 0.1.0 [class: string] [info] * tier: {name: webserver,type: standard,version: 1.0} [class: environmenttier] [info] * environmentname: my-0 [class: string] [info] * cname: my-0.elasticbeanstalk.com [class: string] [info] * applicationname: [class: string] [info] * status: launching [class: string] [info] ------------------------------------------------------------------------ [info] build success [info] ------------------------------------------------------------------------ catalina.out aws:
------------------------------------- /var/log/tomcat7/catalina.out ------------------------------------- tomcat7-7.0.27 rpm installed oct 23, 2014 10:25:48 pm org.apache.catalina.core.aprlifecyclelistener init info: apr based apache tomcat native library allows optimal performance in production environments not found on java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib oct 23, 2014 10:25:49 pm org.apache.coyote.abstractprotocol init info: initializing protocolhandler ["http-bio-8080"] oct 23, 2014 10:25:49 pm org.apache.coyote.abstractprotocol init info: initializing protocolhandler ["ajp-bio-8009"] oct 23, 2014 10:25:49 pm org.apache.catalina.startup.catalina load info: initialization processed in 1507 ms oct 23, 2014 10:25:49 pm org.apache.catalina.core.standardservice startinternal info: starting service catalina oct 23, 2014 10:25:49 pm org.apache.catalina.core.standardengine startinternal info: starting servlet engine: apache tomcat/7.0.27 oct 23, 2014 10:25:49 pm org.apache.catalina.startup.hostconfig deploydirectory info: deploying web application directory /var/lib/tomcat7/webapps/root oct 23, 2014 10:26:04 pm org.apache.catalina.core.applicationcontext log info: no spring webapplicationinitializer types detected on classpath oct 23, 2014 10:26:04 pm org.apache.coyote.abstractprotocol start info: starting protocolhandler ["http-bio-8080"] oct 23, 2014 10:26:04 pm org.apache.coyote.abstractprotocol start info: starting protocolhandler ["ajp-bio-8009"] oct 23, 2014 10:26:04 pm org.apache.catalina.startup.catalina start info: server startup in 14683 ms upd1
<properties> <beanstalker.region>eu-west-1</beanstalker.region> </properties> upd2
i got access instance via ssh , found deployed application in /var/lib/tomcat7/webapps/root described in log. dowloaded same version of tomcat , tried deploy in same folder same war (i downloaded war aws) in aws - fine , application started...
any ideas why not started in aws tomcat?
can confirm availability zone aws console?
by default, beanstalker uses us-east-1, new aws accounts, default tends us-west-1 instead
java maven amazon-web-services elastic-beanstalk
No comments:
Post a Comment