嗨,当我试图在OpenSatck上提供一个从服务器时,我得到了一个follwing错误。在openstack上创建了从机,但它会破坏它,出现以下异常
在sun.reflect.nativeMethodAccessorImpl.Invoke0(原生方法)在sun.reflect.nativeMethodAccessorImpl.Invoke(未知源)在java.lang.reflect.Method.Invoke(未知源)在jav.kohsuke.stapler.function$instanceFunction.Invoke(Function.java:298)在org.kohsuke.stapler.function.bindandInvoke(Function.java:161)在doDispatch(Metaclass.java:121),org.kohsuke.stapler.namebaseddispatcher.dispatcher(namebaseddispatcher.java:53),org.kohsuke.stapler.stapler.tryInvoke(stapler.java:746),org.kohsuke.stapler.metaclass$6.doDispatch(Metaclass.java:249),org.kohsuke.stapler.namebaseddispatist cher.dispatch(namebaseddispatcher.java:53)位于org.kohsuke.statryInvoke(stapler.java:746),在org.kohsuke.stapler.stapler.invoke(stapler.java:876),在org.kohsuke.stapler.stapler.invoke(stapler.java:649),在org.kohsuke.stapler.stapler.service(stapler.java:238),在javax.servlet.http.httpservlet.service(httpservlet.java:848),在lethandler.java:1494)在hudson.util.pluginServletFilter.1.doFilter(pluginServletFilter.java:123)在hudson.util.pluginServletFilter.doFilter(pluginServletFilter.java:114)在org.eclipse.jetty.servlet.servlet.servlet.servlet.doFilter(pluginServletFilter.java:114)在hudson.security.csrf.crumfilter.doFilter(servlethandler.java:1482)在security.chainedServletFilter$1.doFilter(chainedServletFilter.java:84)在hudson.security.chainedServletFilter.doFilter(chainedServletFilter.java:76)在doFilter(hudsonFilter.java:164)在org.eclipse.jetty.servlet.servlethandler$cachedchain.doFilter(servlethandler.java:1482)在org.kohsuke.stapler.compression.compressionfilter.doFilter(compressionfilter.java:49)在org.eclipse.jetty.servlet.servlet.doFilter(compressionfilter.java:1482)在hudson.util.characeEncodingFilter.doFilter在org.kohsuke.stapler.diagnosticthreadnamefilter.doFilter(diagnosticthreadnamefilter.java:30)在org.eclipse.jetty.servlet.servlet.servlethandler$cachedchain.doFilter(servlethandler.java:1474)在org.eclipse.jetty.servlet.servlethandler$cachedchain.doFilter(servlethandler.java:499)在org.eclipse.jetty.scopedhandler.handle(在org.eclipse.jetty.server.session.sessionhandler.doHandle(SessionHandler.java:231)在org.eclipse.jetty.server.handler.contextHandler.dohandle(contextHandler.java:1086)在org.eclipse.jetty.servlet.servlet.servlet.servlethandler.doScope(servlethandler.java:428)在org.eclipse.jetty.server.session.sessionhandler.doScope(sessionhandler.java:193)在org.eclipse.jetty.sessionhandler.doScope(:135)在org.eclipse.jetty.server.handlerwrapper.handlerwrapper.handlerwrapper.handler(handlerwrapper.java:116),在org.eclipse.jetty.server.server.handler(server.java:370),在org.eclipse.jetty.server.abstracthttpConnection.handlerequest(abstracthttpConnection.java:489),在org.eclipse.jetty.server.abstracthttpConnection.content在org.eclipse.jetty.httpparser.parsenext(httpparser.java:865)A:240)在org.eclipse.jetty.server.asynchttpConnection.handle(AsynchttpConnection.java:82)在org.eclipse.jetty.io.nio.selectChannelEndpoint.handle(SelectChannelEndpoint.java:668)在org.eclipse.jetty.io.nio.selectChannelEndpoint.java:1.run(selectChannelEndpoint.java:52)在winstone.boundedExecutorService$1.run)在java.lang.thread.run(来源未知)处由:java.lang.runtimeException:org.jclouds.compute.runnodesException:运行1个节点组(ubuntu)位置(RegionOne)映像(bf68af6f-e6a1-43f6-8ff7-25b54d257fe8)时出错(2)选项({)执行失败:
0 error[s]
Node failures:
1) NoSuchElementException on node RegionOne/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7:
java.util.NoSuchElementException: could not connect to any ip address port 22 on node {id=RegionOne/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, providerId=873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, uri=http://172.27.59.30:8774/v2/98e76fc602cc4a2ca945ff7140a4c1a5/servers/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, name=ubuntu-d64, uri=http://172.27.59.30:8774/v2/98e76fc602cc4a2ca945ff7140a4c1a5/servers/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, location={scope=HOST, id=049edc6318675e518ceb2b7b4628dc2d680176680f59204d452b8314, description=049edc6318675e518ceb2b7b4628dc2d680176680f59204d452b8314, parent=RegionOne}, group=ubuntu, imageId=RegionOne/bf68af6f-e6a1-43f6-8ff7-25b54d257fe8, os={family=unrecognized, name=Ubuntu-14.04, description=Ubuntu-14.04, is64Bit=true}, status=RUNNING, loginPort=22, hostname=ubuntu-d64, privateAddresses=[10.0.0.2], hardware={id=RegionOne/2, providerId=2, name=m1.small, location={scope=ZONE, id=RegionOne, description=RegionOne, parent=openstack-nova}, processors=[{cores=1.0, speed=1.0}], ram=2048, volumes=[{type=LOCAL, size=20.0, bootDevice=true, durable=true}], supportsImage=ALWAYS_TRUE}, loginUser=ubuntu, userMetadata={Name=ubuntu, jclouds-group=ubuntu}}
at org.jclouds.compute.util.ConcurrentOpenSocketFinder.findOpenSocketOnNode(ConcurrentOpenSocketFinder.java:107)
at org.jclouds.compute.functions.CreateSshClientOncePortIsListeningOnNode.apply(CreateSshClientOncePortIsListeningOnNode.java:71)
at org.jclouds.compute.functions.CreateSshClientOncePortIsListeningOnNode.apply(CreateSshClientOncePortIsListeningOnNode.java:45)
at org.jclouds.compute.callables.SudoAwareInitManager.init(SudoAwareInitManager.java:71)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.init(RunScriptOnNodeAsInitScriptUsingSsh.java:68)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.init(RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.java:81)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.init(RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.java:42)
at org.jclouds.compute.strategy.InitializeRunScriptOnNodeOrPlaceInBadMap.call(InitializeRunScriptOnNodeOrPlaceInBadMap.java:65)
at org.jclouds.compute.strategy.InitializeRunScriptOnNodeOrPlaceInBadMap.call(InitializeRunScriptOnNodeOrPlaceInBadMap.java:38)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:123)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:146)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:53)
at shaded.com.google.common.util.concurrent.Futures$1.apply(Futures.java:711)
at shaded.com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:849)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
1 error[s]
at shaded.com.google.common.base.Throwables.propagate(Throwables.java:160)
at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.destroyBadNodesAndPropagate(JCloudsSlaveTemplate.java:347)
at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.get(JCloudsSlaveTemplate.java:336)
at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.provisionSlave(JCloudsSlaveTemplate.java:191)
at jenkins.plugins.jclouds.compute.JCloudsCloud.doProvision(JCloudsCloud.java:281)
... 58 more
Caused by: org.jclouds.compute.RunNodesException: error running 1 node group(ubuntu) location(RegionOne) image(bf68af6f-e6a1-43f6-8ff7-25b54d257fe8) size(2) options({loginUser=ubuntu, loginPasswordPresent=true, loginPrivateKeyPresent=true, scriptPresent=true, securityGroups=[default], userMetadata={Name=ubuntu}, autoAssignFloatingIp=false, keyPairName=pub, userData=[B@7c1521, configDrive=false})
Execution failures:
0 error[s]
Node failures:
1) NoSuchElementException on node RegionOne/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7:
java.util.NoSuchElementException: could not connect to any ip address port 22 on node {id=RegionOne/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, providerId=873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, uri=http://172.27.59.30:8774/v2/98e76fc602cc4a2ca945ff7140a4c1a5/servers/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, name=ubuntu-d64, uri=http://172.27.59.30:8774/v2/98e76fc602cc4a2ca945ff7140a4c1a5/servers/873b9f1f-8c3b-41c1-9590-c85ba0bd39c7, location={scope=HOST, id=049edc6318675e518ceb2b7b4628dc2d680176680f59204d452b8314, description=049edc6318675e518ceb2b7b4628dc2d680176680f59204d452b8314, parent=RegionOne}, group=ubuntu, imageId=RegionOne/bf68af6f-e6a1-43f6-8ff7-25b54d257fe8, os={family=unrecognized, name=Ubuntu-14.04, description=Ubuntu-14.04, is64Bit=true}, status=RUNNING, loginPort=22, hostname=ubuntu-d64, privateAddresses=[10.0.0.2], hardware={id=RegionOne/2, providerId=2, name=m1.small, location={scope=ZONE, id=RegionOne, description=RegionOne, parent=openstack-nova}, processors=[{cores=1.0, speed=1.0}], ram=2048, volumes=[{type=LOCAL, size=20.0, bootDevice=true, durable=true}], supportsImage=ALWAYS_TRUE}, loginUser=ubuntu, userMetadata={Name=ubuntu, jclouds-group=ubuntu}}
at org.jclouds.compute.util.ConcurrentOpenSocketFinder.findOpenSocketOnNode(ConcurrentOpenSocketFinder.java:107)
at org.jclouds.compute.functions.CreateSshClientOncePortIsListeningOnNode.apply(CreateSshClientOncePortIsListeningOnNode.java:71)
at org.jclouds.compute.functions.CreateSshClientOncePortIsListeningOnNode.apply(CreateSshClientOncePortIsListeningOnNode.java:45)
at org.jclouds.compute.callables.SudoAwareInitManager.init(SudoAwareInitManager.java:71)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.init(RunScriptOnNodeAsInitScriptUsingSsh.java:68)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.init(RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.java:81)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.init(RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.java:42)
at org.jclouds.compute.strategy.InitializeRunScriptOnNodeOrPlaceInBadMap.call(InitializeRunScriptOnNodeOrPlaceInBadMap.java:65)
at org.jclouds.compute.strategy.InitializeRunScriptOnNodeOrPlaceInBadMap.call(InitializeRunScriptOnNodeOrPlaceInBadMap.java:38)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:123)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:146)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:53)
at shaded.com.html" target="_blank">google.common.util.concurrent.Futures$1.apply(Futures.java:711)
at shaded.com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:849)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
1 error[s]
at org.jclouds.compute.internal.BaseComputeService.createNodesInGroup(BaseComputeService.java:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)
at com.sun.proxy.$Proxy90.createNodesInGroup(Unknown Source)
at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.get(JCloudsSlaveTemplate.java:334)
... 60 more
jclouds似乎无法ssh到您的机器中。默认情况下,您的映像支持SSH吗?或者可能是网络问题。
我正在尝试搜索亚马逊的产品广告,并使用botlenose来帮助我做到这一点。但是,我刚刚收到HTTP错误400。 其他一些重要信息: 我来自巴西,我的标签也来自亚马逊。这是个问题吗? 我确实检查了我的钥匙、秘密和标签,一切正常。我确实在StackOverflow上查看了其他一些问题,但对我来说没有任何效果。 当然,出于安全原因,我更改了密钥。 Traceback(最近一次调用最后一次):File"
我有一个基于Spring Web model view controller(MVC)框架的项目。Spring Web模型-视图-控制器(MVC)框架的版本是3.2.8 我有这个控制器 这个URL一切正常:
目前从Angular JS controller中,我试图将JSON数据发送到后端服务。但是我有400个错误的请求错误。 在Controller中,我试图通过http服务发送数据,如下所示:
我得到了这个错误,有什么想法会导致它吗?我试图发送一个DTO,它有一个扩展抽象类的对象列表,我想这个问题可能是因为DTO中的列表,还是因为抽象类的子类?
在月食中, ”org.apache.axis2。AxisFault:传输错误: 403错误:禁止”试图从svn检出项目时发生错误。我不能实现这个错误,因此我检查了从终端使用"svn-co"命令的项目。 但是,有趣的是,当我试图在Eclipse中运行应用程序时,在输入凭据(用户名和密码)并按下“登录”按钮之后,我又遇到了相同的错误。响应是JFrame上的无效用户名/密码,但凭据没有错误。这只发生在日
Errors 错误 Library routines must often return some sort of error indication to the caller. As mentioned earlier, Go’s multivalue return makes it easy to return a detailed error description alongside th
本章概述了Google API错误模型,以及开发人员如何正确生成和处理错误的一般指南。 Google API使用简单的协议无关错误模型,这使我们能够在不同的API,API协议(如gRPC或HTTP)以及错误上下文(例如,异步,批处理或工作流错误)中获得一致的体验。 错误模型 错误模型在逻辑上由google.rpc.Status定义,当API发生错误时,返回一个Status实例给客户端。 以下代码段
5.4. 错误 在Go中有一部分函数总是能成功的运行。比如strings.Contains和strconv.FormatBool函数,对各种可能的输入都做了良好的处理,使得运行时几乎不会失败,除非遇到灾难性的、不可预料的情况,比如运行时的内存溢出。导致这种错误的原因很复杂,难以处理,从错误中恢复的可能性也很低。 还有一部分函数只要输入的参数满足一定条件,也能保证运行成功。比如time.Date函数