hi Jan, yes you are correct. And even in the old configuration, a connection reset is a network issue, so you would have to see who initiated the the reset (TCP RST package). Most likely the IP that

Sorry, I've missed your notes about the firewalls you configure for each CF machine - this firewalls is what needs to be configured to accept UDP traffic to ports 3456 and 3457 from any host. vSphere

Sorry, I've missed your notes about the firewalls you configure for each CF machine - this firewalls is what needs to be configured to accept UDP traffic to ports 3456 and 3457 from any host. vSphere

I have never worked with vSphere, unfortunately. I've googled a bit and found this table which shows which TCP and UDP ports are open by default on vSphere VMs

I deployed my CF on vshpere server. Sent: 2015年6月2日 18:30 To: Discussions about Cloud Foundry projects and the system overall. Subject: Re: [cf-dev] What ports will be needed to support hm and

You have posted your Application Security Groups - http://docs.pivotal.io/pivotalcf/adminguide/app-sec-groups.html. This groups are created and managed by Cloud Foundry. But the issue here is with

Hi, Lev Would you please let me know what exactly I should add to my security group? Following are the current configuration. - name: public_networks rules: - protocol: all

Hi, At least for loggregator to successflly talk to metron agents, you need to add a rule to a security group for your private subnet allowing the ingress UDP traffic through ports 3456 and 3457 from

Hi, I am updating my cf env from 172 to 197. But I found some issues after upgrade is done. I couldn't get the correct running application instance number: CF_TRACE=true cf apps ...

Am I right this problem is obsolete since the login-uaa merge in CF 208 [1]? Regards, Jan [1] http://lists.cloudfoundry.org/pipermail/cf-dev/2015-May/000087.html

Hi, I'm running a v205 CF deployment with ~350 application instances. I just found that the doppler process on the doppler node and the metron_agent process on the gorouter node used too much

Good afternoon, Last week, we merged a branch into cf-release that upgraded the postgres instance if you are running one. We saw this fail on two of our environments and reverted these changes

Hi, while running the CF 207 smoke and acceptance tests repeatedly, we noticed sporadic connection resets during 'cf login' (see log snippet from login log below). The connection reset is happening

+1 for password expiry; that'd be really handy to have. -- Regards, Daniel Jones EngineerBetter.com

Hello, thank you for the hint! I'd prefer to do something at application level, like a shell script to run in parallel to the application that every X seconds prints the output of netstat, as the

i may miss standup but I'll be there for IPM

fyi, we use UAA for our social login , take a look www.merv.id F -- Frans Thamura (曽志胜) Java Champion Shadow Master and Lead Investor Meruvian. Integrated Hypermedia Java Solution

1. For users created in UAA database, are there any policies we could apply regarding password expiry/strength of the password/lockout on repeated retry failures etc..? Currently there is a

Looking into using UAA and have couple of questions: 1. For users created in UAA database, are there any policies we could apply regarding password expiry/strength of the password/lockout on

Kim and James, thanks for responding and asking clarifying questions. Regarding latest, the end manifest ended up with lucid stemcell references. I changed them to trusty and then the deploy failed