Amazon-ecs-agent: ECS Task stopped with Exit Code 139

[fshahnaz]

ECS cluster lists multiple containers under stopped list that were stopped with following info

• Stopped reason Essential container in task exited
• Details Exit Code 139

Can someone please offer any insight into what that code means?

[samuelkarp]

Exit code 139 typically indicates that your program had a segmentation fault and was killed by the kernel. Exit codes starting with 128 usually indicate the receipt of a signal, which you can get by subtracting 128 from the exit code: 139 - 128 = 11 (SIGSEGV). See general information on special exit codes.

I'm going to close this here since this is a general Linux question rather than something ECS specific.

[opinionmachine]

I disagree. It'll be because ECS is failing to do something that works elsewhere. I e at the very least a bug in the documentation, but most likely in the logging or something, that led somebody to google "ecs Exit Code 139" because that's all they got. I know a key design goal of ECS is to completely hide any useful information or feedback of what's going wrong so that the customer always is completely blind, but it might be a nice change of pace to get some information occasionally.