2016-08-22 5 views
0

Spring Boot Docker 이미지의 인스턴스가있는 AWS EC2에서 자동 크기 조정 클러스터를 설정하려고합니다. 내가 명령을 실행하면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

종료 된 컨테이너의 도커 로그로 질문을 업데이트했습니다. – FiguringThisOut

답변

0

문제는 내가 충분한 메모리가 설정되어 있지 않은 것이 었습니다. 그러므로 Tomcat에 도착하기 전에 메모리가 부족하여 Tomcat에 도착할 때까지 모든 것이 정상적인 것처럼 보였습니다. 나는 기억을 부딪혔다. 그리고 그것은 잘 시작했다.

관련 문제