AutoScaling app failed to start saying 'org.ektorp.DbAccessException: Connection refused' about app-autoscaler HOT 7 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/135681559

The labels on this github issue will be updated when the story is started.

from app-autoscaler.

Does the config.properties in your built server/target/server-1.0.war look correct?
Can you get into the container and see if you can access couchdb? Do you have any security groups blocking the outbound connect?

from app-autoscaler.

Thanks Michael. config.properties looks good and not modified. I can access the couchdb from the runner vm. There is no security groups settings in my network.

I see that these are iptables rules for the containers on the runner vm and the allowed destination ip range for each containers excludes10.0.0.0/8 and 192.168.0.0/16. my couchdb ip is192.168.101.208. maybe this is the root cause, but i don't know how to modify the defualt allowed networks for new containers.

from app-autoscaler.

You have to fix your default security group rule.

from app-autoscaler.

Do you mean this doc https://docs.cloudfoundry.org/adminguide/app-sec-groups.html ? Any specific section? Thanks a lot.

from app-autoscaler.

The default security group only allows communication to public networks. You need to add access to private networks. See the example they have in the provided docs you linked above.

from app-autoscaler.

Thanks @fraenkel a lot. My problem is solved after adding a security group for CouchDB server.

cf create-security-group my-priviate-sg my-priviate-sg.json
cf bind-security-group my-priviate-sg ORG SPACE 

cat my-priviate-sg.json
[
  {
    "protocol": "tcp",
    "destination": "192.168.101.0-192.168.101.255",
    "ports": "5984",
    "description": "internal CouchDB"
  }
]

from app-autoscaler.