您的位置: 首页  >  技术问答  >  如何在Elastic Beanstalk中自定义hosts文件？

如何在Elastic Beanstalk中自定义hosts文件？

分类: 技术问答 • 2022-09-12 22:47:04
问题描述：

我们，这是获得通过EBS（在Tomcat）部署的应用程序，每一个现在，然后我们得到了一个错误：如何在Elastic Beanstalk中自定义hosts文件？

unable to resolve host ip-172-30-0-167

这会导致其他问题。 据我所知，解决这个问题的方法之一是通过更新hosts文件并使用指向服务器真实IP地址的条目ip-172-30-0-167。

我的问题是，如何在部署中向主机文件添加条目？我没有通过.ebsextensions发现与它相关的任何内容。

也许有另一种方法来解决它。

UPDATE

其中之一，我有问题是发送电子邮件：

ERROR g.plugins.mail.MailMessageBuilder: Failed to send email 
Jan 27 15:40:30 unknown staging: org.springframework.mail.MailSendException: Mail server connection failed; nested exception is javax.mail.MessagingException: 501 Syntax: EHLO hostname 
Jan 27 15:40:30 unknown staging: . Failed messages: javax.mail.MessagingException: 501 Syntax: EHLO hostname 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:417) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:345) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:340) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSender$send$0.call(Unknown Source) ~[na:na] 
Jan 27 15:40:30 unknown staging: at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) ~[groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) ~[groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) ~[groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at grails.plugins.mail.MailMessageBuilder$_sendMessage_closure1.doCall(MailMessageBuilder.groovy:124) [mail-2.0.0.RC6.jar:na] 
Jan 27 15:40:30 unknown staging: at grails.plugins.mail.MailMessageBuilder$_sendMessage_closure1.doCall(MailMessageBuilder.groovy) [mail-2.0.0.RC6.jar:na] 
Jan 27 15:40:30 unknown staging: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.Closure.call(Closure.java:426) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.Closure.call(Closure.java:420) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.Closure.run(Closure.java:507) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: Caused by: javax.mail.MessagingException: 501 Syntax: EHLO hostname 
Jan 27 15:40:30 unknown staging: at com.sun.mail.smtp.SMTPTransport.issueCommand(SMTPTransport.java:1481) ~[mail-1.4.1.jar:1.4.1] 
Jan 27 15:40:30 unknown staging: at com.sun.mail.smtp.SMTPTransport.helo(SMTPTransport.java:917) ~[mail-1.4.1.jar:1.4.1] 
Jan 27 15:40:30 unknown staging: at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:417) ~[mail-1.4.1.jar:1.4.1] 
Jan 27 15:40:30 unknown staging: at javax.mail.Service.connect(Service.java:345) ~[javax.mail-api-1.5.1.jar:1.5.1] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.connectTransport(JavaMailSenderImpl.java:486) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:406) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: ... 22 common frames omitted 
Jan 27 15:40:30 unknown staging: ERROR g.plugins.mail.MailMessageBuilder: Failed to send email 
Jan 27 15:40:30 unknown staging: org.springframework.mail.MailSendException: Mail server connection failed; nested exception is javax.mail.MessagingException: 501 Syntax: EHLO hostname 
Jan 27 15:40:30 unknown staging: . Failed messages: javax.mail.MessagingException: 501 Syntax: EHLO hostname 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:417) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:345) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:340) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSender$send$0.call(Unknown Source) ~[na:na] 
Jan 27 15:40:30 unknown staging: at grails.plugins.mail.MailMessageBuilder$_sendMessage_closure1.doCall(MailMessageBuilder.groovy:124) [mail-2.0.0.RC6.jar:na] 
Jan 27 15:40:30 unknown staging: at grails.plugins.mail.MailMessageBuilder$_sendMessage_closure1.doCall(MailMessageBuilder.groovy) [mail-2.0.0.RC6.jar:na] 
Jan 27 15:40:30 unknown staging: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.Closure.call(Closure.java:426) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.Closure.call(Closure.java:420) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at groovy.lang.Closure.run(Closure.java:507) [groovy-2.4.5.jar:2.4.5] 
Jan 27 15:40:30 unknown staging: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111] 
Jan 27 15:40:30 unknown staging: Caused by: javax.mail.MessagingException: 501 Syntax: EHLO hostname 
Jan 27 15:40:30 unknown staging: at com.sun.mail.smtp.SMTPTransport.issueCommand(SMTPTransport.java:1481) ~[mail-1.4.1.jar:1.4.1] 
Jan 27 15:40:30 unknown staging: at com.sun.mail.smtp.SMTPTransport.helo(SMTPTransport.java:917) ~[mail-1.4.1.jar:1.4.1] 
Jan 27 15:40:30 unknown staging: at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:417) ~[mail-1.4.1.jar:1.4.1] 
Jan 27 15:40:30 unknown staging: at javax.mail.Service.connect(Service.java:345) ~[javax.mail-api-1.5.1.jar:1.5.1] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.connectTransport(JavaMailSenderImpl.java:486) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:406) ~[spring-context-support-4.1.8.RELEASE.jar:4.1.8.RELEASE] 
Jan 27 15:40:30 unknown staging: ... 19 common frames omitted

，它看起来像上部署该方法并没有帮助：

ERROR net.sf.ehcache.Cache: Unable to set localhost. This prevents creation of a GUID. Cause was: ip-172-35-11-183: ip-172-35-11-183: Name or service not known 
Jan 27 15:35:25 unknown staging: java.net.UnknownHostException: ip-172-35-11-183: ip-172-35-11-183: Name or service not known 
Jan 27 15:35:25 unknown staging: at java.net.InetAddress.getLocalHost(InetAddress.java:1505) ~[na:1.8.0_111] 
Jan 27 15:35:25 unknown staging: at net.sf.ehcache.Cache.<clinit>(Cache.java:200) ~[ehcache-core-2.4.3.jar:na] 
Jan 27 15:35:25 unknown staging: at net.sf.ehcache.config.ConfigurationHelper.createCache(ConfigurationHelper.java:302) [ehcache-core-2.4.3.jar:na] 
Jan 27 15:35:25 unknown staging: at net.sf.ehcache.config.ConfigurationHelper.createDefaultCache(ConfigurationHelper.java:218) [ehcache-core-2.4.3.jar:na] 
Jan 27 15:35:25 unknown staging: at net.sf.ehcache.CacheManager.configure(CacheManager.java:599) [ehcache-core-2.4.3.jar:na] 
Jan 27 15:35:25 unknown staging: at net.sf.ehcache.CacheManager.init(CacheManager.java:358) [ehcache-core-2.4.3.jar:na]
+0

这在Tomcat Elastic Beanstalks上总是出错 - 它会导致什么问题？ – stdunbar

+0

在我们的例子中，似乎发送电子邮件是窒息+有时nginx代理需要在部署后重新启动。 –

+0

@stdunbar因此，这种方法似乎并没有真正的帮助。请参阅最新信息 –

答

好吧，我说这是常见的，然后看看其他代码，发现我在.ebextensions中设置主机名。我有类似的东西：

01_command: 
    echo 127.0.0.1 `hostname` >> /etc/hosts"

添加主机名。请注意，我没有发送电子邮件，所以我不确定是否需要真正的主机名。如果你这样做，可改为：

01_command: 
    echo `curl -s http://169.254.169.254/latest/meta-data/local-ipv4` `hostname` >> /etc/hosts"

最终的问题是，弹性魔豆将主机名设置的东西，是不是在/ etc /像你说的主机。

+0

此解决方案有几个问题。我需要知道这个内部知识产权，我不知道（当然也不总是）。 +它会在每个部署中都这样做，所以我最终会得到一堆这些条目。至于你的最后一个问题，我没有说这是在hosts文件中设置任何东西。我认为它离开了骨头Ubuntu的镜像。 –

+0

curl命令为您提供内部IP（私有IP）。你是对的 - 我的部署过程取消了所有的实例并加入新的实例，所以如果你重用实例，你会得到多个条目。这实际上不会伤害任何东西，但它可能是不正确的。 – stdunbar

+0

另一个问题，但是：这是什么：http://169.254.169.254/latest/meta-data/local-ipv4？ –

答

我认为这是由您的VPC配置中的enableDnsHostnames参数引起的。

看看AWS error - sudo: unable to resolve host ip-10-0-xx-xx

谢谢！

相关推荐