-
Notifications
You must be signed in to change notification settings - Fork 60
Create service fails with timeout #156
Comments
Next step, looking into gateways 0 I see:
Comparing to the ports in the database:
So they are completely different. What's also interesting is that,
The question is, if the Jobs are failing? That would explain, why the ports are changing that often in the database. I will keep debugging. |
Ok, started the mongodb_gateway by hand and I could see the ruby process being started:
Running for a few seconds, and then they are gone. |
And completely manually starting results in the same behaviour:
Now I need to think about the next steps. :-) |
So I can still see the service brokers stopping continuously, while the services itself a running without any problems. Is there any crash log, where I can see, why the service stopped working? |
mmm. We also met some instability with this release. No community effort on cf-services-contrib anyway. |
Yeah the docker-boshrelease or its spinoffs like postgresql-docker-boshrelease and logstash-docker-boshrelease have been my go-to for some quick primitive services. On Thu, Sep 10, 2015 at 11:25 AM, Pierre Oblin [email protected]
|
I have v212 deployed with the specified diego release and with service-contrib-release 6. The deployment runs through smoothly, but when I try to create a service I get:
Looking into the api_z1 I can see:
On the gateway I don't see the ports mapped. Do they change regularly? How is the updating of the ports done?
The text was updated successfully, but these errors were encountered: