Amazon ec2 Teamcity错误-亚马逊EC2中不存在图像

Amazon ec2 Teamcity错误-亚马逊EC2中不存在图像,amazon-ec2,teamcity,agent,Amazon Ec2,Teamcity,Agent,我正在使用teamcity server 8.0.3(build 27540),并建立了几个git项目。我正在使用AmazonEC2图像,这些图像被设置为云代理 我的安装程序启动代理,并在将新作业放入队列时对其运行测试 我让它正常工作了几个星期,没有接触服务器,突然它停止了工作 在云标签中,我现在看到“Image error”,并显示消息:“Image不存在于amazonec2中”。即使图像存在于那里 如果我打开并保存或重新创建我的云代理设置,那么teamcity会唤醒其中一个代理并正常进行构建

我正在使用teamcity server 8.0.3(build 27540),并建立了几个git项目。我正在使用AmazonEC2图像,这些图像被设置为云代理

我的安装程序启动代理,并在将新作业放入队列时对其运行测试

我让它正常工作了几个星期,没有接触服务器,突然它停止了工作

在云标签中,我现在看到“Image error”,并显示消息:“Image不存在于amazonec2中”。即使图像存在于那里

如果我打开并保存或重新创建我的云代理设置,那么teamcity会唤醒其中一个代理并正常进行构建,但警告仍然存在,当代理在我的时间延迟后关闭时,我必须重新保存云代理设置以强制启动代理

我尝试重新启动Teamcity,但没有成功

这是teamcity-cloud.log中的错误

[2013-12-12 06:11:00,850]   WARN [rome'{id=cp3} 1] - .clouds.amazon.image.ImageBase - Failed to fetch data of image AmazonImageInstance{id=i-d123cd29, amazonId=ami-463edb31} from EC2. Image does not exist in Amazon EC2 
[2013-12-12 06:11:00,958]   INFO [ue; Flush Queue] - .instances.StartInstanceAction - Starting cloud instance: profile 'EC2 TC Win Chrome'{id=cp3}, AmazonImageInstance{id=i-d123cd29, amazonId=ami-463edb31}, hash=EZObYYzWwxDOZ4o9svYSvGbdLqf5e7KQ, reason=Automatic start: Compatible with queued build Booking Log Client :: Win Chrome(promotionId=12008) 
[2013-12-12 06:11:01,565]   INFO [ue; Flush Queue] - .server.impl.CloudEventsLogger - Cloud instance start succeeded: profile 'EC2 TC Win Chrome'{id=cp3}, Amazon Instance{instanceId=i-d123cd29, imageId=i-d123cd29, amazonImageId=ami-463edb31, status: Scheduled to start} 
[2013-12-12 06:11:03,135]   INFO [rome'{id=cp3} 1] - r.impl.DBCloudStateManagerImpl - Image: i-d123cd29, Instance: i-d123cd29 is marked with state: running. 
[2013-12-12 06:12:18,441]   WARN [uled executor 4] - .instances.StoppedInstanceTask - Instance has changed status from stopped to Running: Amazon Instance{instanceId=i-d123cd29, imageId=i-d123cd29, amazonImageId=ami-463edb31, status: Running}, profile 'EC2 TC Win Chrome'{id=cp3} 
[2013-12-12 06:12:20,759]   WARN [rome'{id=cp3} 1] - .clouds.amazon.image.ImageBase - Failed to fetch data of image AmazonImageInstance{id=i-d123cd29, amazonId=ami-463edb31} from EC2. Image does not exist in Amazon EC2 
[2013-12-12 06:13:04,668]   INFO [nio-8111-exec-9] - r.impl.DBCloudStateManagerImpl - Image: AmazonImageInstance{id=i-d123cd29, amazonId=ami-463edb31}, profile: profile 'EC2 TC Win Chrome'{id=cp3} was marked to CONTAIN agent 
[2013-12-12 06:13:04,672]   INFO [nio-8111-exec-9] - .server.impl.CloudEventsLogger - Detected cloud agent EC2-i-d123cd29 {id=24, host=10.254.1.23:9090, agentTypeId=122, pool=Win Chrome}, profile 'EC2 TC Win Chrome'{id=cp3}, Amazon Instance{instanceId=i-d123cd29, imageId=i-d123cd29, amazonImageId=ami-463edb31, status: Running} 
并从teamcity-server.log

[2013-12-12 06:13:04,648]   WARN -    jetbrains.buildServer.AGENT - Agent EC2-i-dd123cd29 is unauthorized with comment: Cloud instance (id=i-dd123cd29, imageId=i-dd123cd29, profileId=cp3) has gone (is not reported by cloud profile) 
[2013-12-12 06:13:04,661]   INFO -   jetbrains.buildServer.SERVER - Agent has been registered: EC2-i-dd123cd29 {id=24, host=10.254.1.23:9090, agentTypeId=122, pool=Win Chrome}, not running a build 
[2013-12-12 06:13:04,690]   INFO - tbrains.buildServer.ACTIVITIES - Agent "EC2-i-dd123cd29 {id=24, host=10.254.1.23:9090, agentTypeId=122, pool=Win Chrome}" was authorised with comment "Virtual agent is authorized automatically." 
[2013-12-12 06:13:05,022]   INFO - tbrains.buildServer.ACTIVITIES - Build started; Booking Log Client :: Win Chrome {id=booking_log_client, internal id=bt18} #34 {build id=6213, promotion id=12008, branch=<default>, history=false, agent=EC2-i-dd123cd29 {id=24, host=10.254.1.23:9090, agentTypeId=122, pool=Win Chrome}, triggered by "Nisse Nilsson" (##userId='10'). Started Thu Dec 12 06:13:04 UTC 2013} 
[2013-12-12 06:13:57,586]   INFO -   jetbrains.buildServer.SERVER - Agent description updated for agent: EC2-i-dd123cd29 {id=24, host=10.254.1.23:9090, agentTypeId=122, pool=Win Chrome} 
[2013-12-12 06:23:54,323]   INFO -   jetbrains.buildServer.SERVER - Agent description updated for agent: EC2-i-dd123cd29 {id=24, host=10.254.1.23:9090, agentTypeId=122, pool=Win Chrome} 
[2013-12-12 06:13:04648]警告-jetbrains.buildServer.AGENT-代理EC2-i-dd123cd29未经授权,带有注释:云实例(id=i-dd123cd29,imageId=i-dd123cd29,profileId=cp3)已消失(云配置文件未报告)
[2013-12-12 06:13:04661]信息-jetbrains.buildServer.SERVER-代理已注册:EC2-i-dd123cd29{id=24,host=10.254.1.23:9090,agentTypeId=122,pool=Win Chrome},未运行生成
[2013-12-12 06:13:04690]信息-tbrains.buildServer.ACTIVITIES-Agent“EC2-i-dd123cd29{id=24,host=10.254.1.23:9090,agentTypeId=122,pool=Win Chrome}”已通过注释“虚拟代理已自动授权”进行授权
[2013-12-12 06:13:05022]信息-tbrains.buildServer.ACTIVITIES-构建已开始;预订日志客户端:Win Chrome{id=Booking_Log_Client,内部id=bt18}{34{build id=6213,促销id=12008,branch=,history=false,agent=EC2-i-dd123cd29{id=24,host=10.254.1.23:9090,agentTypeId=122,pool=Win Chrome},由“Nisse Nilsson”(##userId='10')触发。于2013年12月12日06:13:04 UTC开始
[2013-12-12 06:13:57586]信息-jetbrains.buildServer.SERVER-代理的代理描述已更新:EC2-i-dd123cd29{id=24,主机=10.254.1.23:9090,代理类型id=122,池=Win Chrome}
[2013-12-12 06:23:54323]信息-jetbrains.buildServer.SERVER-代理的代理描述已更新:EC2-i-dd123cd29{id=24,主机=10.254.1.23:9090,代理类型id=122,池=Win Chrome}
出现错误的原因是: AMI“AMI-463edb31”在EC2的“欧盟(爱尔兰)”地区不再可用

来源:

出现错误的原因是: AMI“AMI-463edb31”在EC2的“欧盟(爱尔兰)”地区不再可用

资料来源: