`[2015-09-24 15:06:25.24 (UTC)]> cf logout Logging out... OK • Failure [22.809 seconds] Admin

Containers have a default iptables rule for REJECT all traffic. If there is not a security group configured to allow the traffic to the destination, you'll get a connection refused. Security groups

Ok, after more investigating the problem was that network manager was running on the machine and was trying to take control of new network interfaces after they came up, so it would cause problems

My vote on to wait a couple more months. I guess we'll see if anyone else would like more months. Mike

Hi Dieu, many thanks for the technical info. I will consider this factor to add this restriction in the development. Juan Antonio

Thanks Mike. Totally understandable.

Your edge load balancer should be configured to add x-forwarded-for and x-forwarded-proto headers. bren(a)juanantonio.info> wrote:

Separate from this proposal, the CAPI team has stories for spiking on a few different api documentation options for the cloud controller api [1]. Swagger is one of the options we are looking into, but

That did help. It showed us the real error. ==> metron_agent/metron_agent.stdout.log <== {"timestamp":1443054247.927488327,"process_id":23472,"source":"metron","log_level":"warn","message":"Failed to

That does makes sense. Especially since I'm seeing a consistent percentage. At one point, one app was getting 100% throughput and another was only getting 75%. So maybe one of the dopplers didn't have

We are running with 2 zones, 2 loggregators in each zone. I thought the same thing. Stopping all but one loggregator showed the same results. If it helps, yesterday I was seeing 75% of the logs

v210 has quite a few bugs in this area. One fairly major one is a connection leak [1] in the syslog_drain_binder component. When this happens, changes to the syslog drain bindings do not make their

Hi Michael First question that springs to mind when I see ~50% - how many zones are you running as part of your setup? ("every other log" sounds like a round-robin to something dead or

The system is currently running ~200 apps and they all bind to an external syslog drain.

Loggregator appears to be dropping logs without notice. I'm noticing about 50% of the logs do not make it to our external log service. If I tail the logs using "cf logs ...", all logs are visible.

Hi Mohamed and Dr. Max, I fully support this effort. By having Swagger based “Application Interface” capability as part of the overall CF PaaS platform would be very useful for the CF community as

I often take the following approach to debugging issues like this: * Open two shell sessions to your failing VM using bosh ssh, and switch to superuser * In one session, `watch monit summary`. You

Thanks Dieu, honestly I was just trying to find an angle to bargain for a bit more time. :) Three months is generous. But six months would be glorious. :) After the CAB call this month we got

Here's the output from those commands: https://gist.github.com/MrEnzyme/36592831b1c46d44f007 Soon after running those I noticed that the container loses its IPv4 address shortly after coming up and

hi Anna, Can you elaborate a little bit about what you are referring to? I'm not quite sure what you are asking. Filip wrote: