如何查看AWS Batch Compute Environment错误? [英] How do I view AWS Batch Compute Environment Errors?

查看:71
本文介绍了如何查看AWS Batch Compute Environment错误?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们设置了一个批处理计算环境,作业队列和作业定义.计算环境的最小CPU设置为16,因此它应始终至少运行一个EC2实例.这是一个MANAGED环境.它还没有开始,但是一切仍然报告健康.我查看了问题排查页面,没有任何有用的信息来吧.

We setup a batch compute environment, job queue, and job definition. The min CPUs for the compute environment is set to 16, so it should always have at least one EC2 instance running. It's a MANAGED environment. It is not starting any, yet everything is still reporting healthy. I've looked at the troubleshooting page and nothing useful has come of it yet.

我在哪里可以找到问题所在?这完全是一个黑匣子吗,如果我在配置中的某个地方犯了错误(可能是某种ARN权限问题),我必须扫描每一行,直到碰巧看到错误为止.

Where can I go to see what is going wrong? Is this completely a black box and if I make a mistake somewhere in my config (Probable some kind of ARN permissions problem), I have to scan every line till I happen to see the mistake?

推荐答案

答案是,看一下EC2 Auto Scaling组.应该有一个以计算环境命名的自动扩展组.启动EC2实例的所有错误都应该在该自动伸缩组中,该组由批处理计算环境创建和管理.

The answer is, look at EC2 Auto Scaling Groups. There should be an autoscaling group named after the compute environment. All of the errors for starting EC2 instances should be in that auto scaling group, which is created and managed by the batch compute environment.

这篇关于如何查看AWS Batch Compute Environment错误?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆