Question: I am new on using a Kinect sensor, I have Kinect XBOX 360 and I need to use it to get a real moving body 3D positions. I need to use it with c++ and openCV. I could not find anything helpful on the web. So, please if anyone can give me some advice or if there any code for opening Kinect XBOX 360 with c++ to start with I will appreciate that.

Answer: 
3 days ago, Our team had met this question. We spent a lot of time for that.

Problem reason should be in AWS ecs-agent(we have 2 envrionment, one ecs-agent's version is 1.21 and another one is 1.24)

Yesterday, We solved this problem: Using AWS console to update ecs-agent to the latest version: 1.34 and restart the ecs-agent(docker contianer) Then the problem was solved.

Just paste this solution here. Hope it would be helpful to others!
Firstly, it's a good idea to avoid using domain names within your Nginx config, especially when defining upstream servers. It's confusing if nothing else.

Are all your values for `example.com` the same? If so you have an upstream block which defines an upstream server cluster with the name `example.com`, then you have a server block with a server name directive of `example.com` and then you are trying to proxy\_pass to `example.com`.

Typically you specify an upstream block as a method of load balancing if you have several servers capable of handling the same request. Edit your upstream block and include all your upstream servers address:port, you can include other options to configure how Nginx distributes the load across them if you wish, see the Nginx docs for more info. The name you give to your upstream block is only used by Nginx and can be anything, don't use your domain name here. Something like:

`upstream dockergroup {`

Then add an ip address before the port in the `listen` directive in the server block and change the `proxy_pass` directive to `http://dockergroup`

I'm not sure of the specifics, but according to the docs on the page you linked:

> 
> you can To add settings on a per-VIRTUAL\_HOST basis, add your
>  configuration file under /etc/nginx/vhost.d. Unlike in the proxy-wide
>  case, which allows multiple config files with any name ending in
>  .conf, the per-VIRTUAL\_HOST file must be named exactly after the
>  VIRTUAL\_HOST.
> 
> 
> 

The important issues to address are that your upstream block cannot be empty and the name of the upstream block should not conflict with any domains or hostnames on your network. From what I read you should be able to fix that using the various config options.