It seems the routers and Haproxy works as you get the 404 from the routers
"404 Not Found: Requested route ('api.subdomain.domain') does not exist."
Maybe something wrong in the manifest especially around system or apps
domain

On Mon, Jul 20, 2015 at 6:26 PM, Schwerdtfeger, Christian <
christian.schwerdtfeger(a)n4group.de> wrote:

Hello together,

i've deployed Cloudfoundry into AWS like following:

- bosh aws create like descriped here:
http://docs.cloudfoundry.org/deploying/ec2/bootstrap-aws-vpc.html
- Installation of bosh like descriped on this page:
http://bosh.io/docs/deploy-microbosh-to-aws.html
- installed cloudfoundry using cf-boshworkspace (
https://github.com/cloudfoundry-community/cf-boshworkspace)

My deployment uses the cf-tiny-scalable.yml deployment of
cf-boshworkspace and is starting secondary AZ nodes for backbone, api and
runner.

With some minor modifications i've got the installation to run through
without error.
After that i tried to "curl api.subdomain.domain/info" and get "404 Not
Found: Requested route ('api.subdomain.domain') does not exist."

Does someone of you have a glue where to search the error? The output of
"monit status" on nodes "public_haproxy_z1/0" and "api_z1/0" seems to be
okay. All processes are marked as "running" and "monitored".

Thank you
Christian

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev