2016-08-22 76 views
0

我正在设置AWS EC2中具有Spring Boot Docker映像实例的自动缩放群集。Tomcat未在AWS EC2的Spring Docker中启动

我能够手动火起来的形象就好在AWS EC2实例,如果我运行命令:

docker run -e "SPRING_PROFILES_ACTIVE=foo" -p 9634:8080 <image>

然而,当我安装在AWS服务任务的自动定集群,它会运行映像,Spring Boot将启动,但Tomcat不会启动。然后,健康检查失败并退出重复执行该服务任务的过程。

我有AWS配置为作为特权用户运行服务任务。我还需要做些什么才能使图像触发Tomcat?

的日志:

2016-08-22 17:41:38.548 INFO 1 --- [   main] com.foo.FooBarApplication   : Starting FooBarApplication v0.0.1 on 1d31be68cda1 with PID 1 (/app.jar started by root in /) 
2016-08-22 17:41:38.625 INFO 1 --- [   main] com.foo.FooBarApplication   : The following profiles are active: dev 
2016-08-22 17:41:38.868 INFO 1 --- [   main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.spring[email protected]5c8da962: startup date [Mon Aug 22 17:41:38 UTC 2016]; root of context hierarchy 
2016-08-22 17:41:40.812 INFO 1 --- [   main] trationDelegate$BeanPostProcessorChecker : Bean 'configurationPropertiesRebinderAutoConfiguration' of type [class org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$fdc7c2d9] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 
2016-08-22 17:41:44.078 INFO 1 --- [   main] com.foo.FooBarApplication   : Started FooBarApplication in 8.984 seconds (JVM running for 27.345) 

    . ____   _   __ _ _ 
/\\/___'_ __ _ _(_)_ __ __ _ \ \ \ \ 
(()\___ | '_ | '_| | '_ \/ _` | \ \ \ \ 
\\/ ___)| |_)| | | | | || (_| | )))) 
    ' |____| .__|_| |_|_| |_\__, |//// 
=========|_|==============|___/=/_/_/_/ 
:: Spring Boot ::  (v1.3.2.RELEASE) 


2016-08-22 17:41:44.296 INFO 1 --- [   main] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at: http://config-server-dev.us-east-1.elasticbeanstalk.com/ 
2016-08-22 17:41:45.153 INFO 1 --- [   main] c.c.c.ConfigServicePropertySourceLocator : Located environment: name=foo-bar, profiles=[dev], label=master, version=null 
2016-08-22 17:41:45.159 INFO 1 --- [   main] b.c.PropertySourceBootstrapConfiguration : Located property source: CompositePropertySource [name='configService', propertySources=[MapPropertySource [name='https://git-codecommit.us-east-1.amazonaws.com/v1/repos/dev-config/foo-bar.yml'], MapPropertySource [name='https://git-codecommit.us-east-1.amazonaws.com/v1/repos/dev-config/application.yml']]] 
2016-08-22 17:41:45.186 INFO 1 --- [   main] com.foo.FooBarApplication   : The following profiles are active: dev 
2016-08-22 17:41:45.215 INFO 1 --- [   main] ationConfigEmbeddedWebApplicationContext : Refreshing org.springframework.boot[email protected]3e6fa38a: startup date [Mon Aug 22 17:41:45 UTC 2016]; parent: org.spring[email protected]5c8da962 
2016-08-22 17:41:47.634 INFO 1 --- [   main] o.s.b.f.s.DefaultListableBeanFactory  : Overriding bean definition for bean 'accessorialsMapping' with a different definition: replacing [Generic bean: class [com.foo.config.AccessorialsMapping]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [jar:file:/app.jar!/com/foo/config/AccessorialsMapping.class]] with [Root bean: class [null]; scope=; abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=fooBarConfiguration; factoryMethodName=configurationBean; initMethodName=null; destroyMethodName=(inferred); defined in class path resource [com/foo/config/FooBarConfiguration.class]]foofoofoo 
2016-08-22 17:41:52.121 INFO 1 --- [   main] o.s.b.f.config.PropertiesFactoryBean  : Loading properties file from URL [jar:file:/app.jar!/lib/spring-integration-core-4.2.4.RELEASE.jar!/META-INF/spring.integration.default.properties] 
2016-08-22 17:41:52.301 INFO 1 --- [   main] o.s.i.config.IntegrationRegistrar  : No bean named 'integrationHeaderChannelRegistry' has been explicitly defined. Therefore, a default DefaultHeaderChannelRegistry will be created. 
2016-08-22 17:41:54.861 INFO 1 --- [   main] faultConfiguringBeanFactoryPostProcessor : No bean named 'errorChannel' has been explicitly defined. Therefore, a default PublishSubscribeChannel will be created. 
2016-08-22 17:41:55.099 INFO 1 --- [   main] faultConfiguringBeanFactoryPostProcessor : No bean named 'taskScheduler' has been explicitly defined. Therefore, a default ThreadPoolTaskScheduler will be created. 
2016-08-22 17:41:57.175 INFO 1 --- [   main] o.s.cloud.context.scope.GenericScope  : BeanFactory id=1cf7e5f3-c000-3b6c-a1fa-5e27219c90be 
2016-08-22 17:43:10.290 INFO 1 --- [   main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [class org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$fdc7c2d9] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 
2016-08-22 17:43:22.515 INFO 1 --- [   main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.RefreshEndpointAutoConfiguration' of type [class org.springframework.cloud.autoconfigure.RefreshEndpointAutoConfiguration$$EnhancerBySpringCGLIB$$30a5be0f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 
+1

你有任何日志文件? – Ralph

+0

使用docker日志更新了退出容器的问题。 – FiguringThisOut

回答

0

的问题是,我没有足够的内存集。因此,在它进入Tomcat之前,内存已经不足了,这让Tomcat看起来一切都很好。我撞上了记忆,它启动得很好。