Failed to advertising brokered service, 403 error
228 views
Skip to first unread message
linnad...@gmail.com
Jul 23, 2012, 4:19:13 AM7/23/12
to vcap...@cloudfoundry.org
Hi all,
I've installed service_broker component, and by using the service_broker_cli tool to broker a local MySQL service, i got the 'successful to create brokered service mysql-broker-5.1' message, but there was no service named "mysql-broker-5.1" listed in neither the system services nor provisioned services catalog. By looking into the service_broker.log, it said that "Failed to advertising brokered service, status=403". I am now confused about this function.
(1) What is the exact regular of parameters in the configure file if I want to connect to a local MySQL database server?
Previously, I use the ".../bin/service_broker_cli -c my-config-file -v" command, and the content of my-config-file.yml is shown as below:
--------------
service_broker: http://service_broker.vcap.me
token: "0xdeadbeef"
service:
name:mysql-broker
description:bla bla
version: "5.1"
options:
- name: mysql
acls:
users: [us...@gmail.com]----->These users should be users on CloudFoundry, right?
wildcards: []
credentials:
conn: mysql://mysqluser:mysqlpwd@local-IP-Address/dbname --------->What regular of these url here should I provide exactly?Am I right?
(2) Since I provided the credential parameters (username, password, database name,etc)in the config file, is the brokered service a system-built-in service or a provisioned one ?
I've installed service_broker component, and by using the service_broker_cli tool to broker a local MySQL service, i got the 'successful to create brokered service mysql-broker-5.1' message, but there was no service named "mysql-broker-5.1" listed in neither the system services nor provisioned services catalog. By looking into the service_broker.log, it said that "Failed to advertising brokered service, status=403". I am now confused about this function.
(1) What is the exact regular of parameters in the configure file if I want to connect to a local MySQL database server?
Previously, I use the ".../bin/service_broker_cli -c my-config-file -v" command, and the content of my-config-file.yml is shown as below:
--------------
service_broker: http://service_broker.vcap.me
token: "0xdeadbeef"
service:
name:mysql-broker
description:bla bla
version: "5.1"
options:
- name: mysql
acls:
users: [us...@gmail.com]----->These users should be users on CloudFoundry, right?
wildcards: []
credentials:
conn: mysql://mysqluser:mysqlpwd@local-IP-Address/dbname --------->What regular of these url here should I provide exactly?Am I right?
(2) Since I provided the credential parameters (username, password, database name,etc)in the config file, is the brokered service a system-built-in service or a provisioned one ?
Aaron
Aug 6, 2012, 4:31:26 AM8/6/12
to vcap...@cloudfoundry.org
I encountered a 500 error；
my config file:
service_broker: http://service-broker.vcap.me
token: "changebrokertoken"
service:
name: xyz_hr_db
description: XYZ HR Database
version: "2.0"
options:
- name: sqlerver
acls:
users: [sa]
wildcards: []
credentials:
conn: sqlserver://sa:123...@sqlserver.vcap.me/test
在 2012年7月23日星期一UTC+8下午4时19分13秒，linnad...@gmail.com写道：
Chunjie Zhu
Aug 8, 2012, 9:27:15 AM8/8/12
to vcap...@cloudfoundry.org
(1) Have you edit the token into CloudController configuration file? Most likely, 403 means token verification failure.
The format is as follows.
builtin_services:
redis:
token: changeredistoken
mongodb:
token: changemongodbtoken
mysql:
token: changemysqltoken
neo4j:
token: changeneo4jtoken
rabbitmq:
token: changerabbitmqtoken
postgresql:
token: changepostgresqltoken
vblob:
token: changevblobtoken
memcached:
token: changememcachedtoken
filesystem:
token: changefilesystemtoken
elasticsearch:
token: changeelasticsearchtoken
couchdb:
token: changecouchdbtoken
service_broker:
token: ["changebrokertoken"]
(2) appear as a system built-in service
Regards,
Chunjie
The format is as follows.
builtin_services:
redis:
token: changeredistoken
mongodb:
token: changemongodbtoken
mysql:
token: changemysqltoken
neo4j:
token: changeneo4jtoken
rabbitmq:
token: changerabbitmqtoken
postgresql:
token: changepostgresqltoken
vblob:
token: changevblobtoken
memcached:
token: changememcachedtoken
filesystem:
token: changefilesystemtoken
elasticsearch:
token: changeelasticsearchtoken
couchdb:
token: changecouchdbtoken
service_broker:
token: ["changebrokertoken"]
(2) appear as a system built-in service
Regards,
Chunjie
From: linnad...@gmail.com
To: vcap...@cloudfoundry.org
Sent: Monday, July 23, 2012 4:19:13 PM
Subject: [vcap-dev] Failed to advertising brokered service, 403 error
To: vcap...@cloudfoundry.org
Sent: Monday, July 23, 2012 4:19:13 PM
Subject: [vcap-dev] Failed to advertising brokered service, 403 error
Chunjie Zhu
Aug 8, 2012, 9:42:46 AM8/8/12
to vcap...@cloudfoundry.org
credentials format, more specific
credentials
hostname: ****** #optional
host: 192.168.1.100
port: 5000
username: helloworld
password: ChangeMe
name: ****** #optional
db: test
url: mysql://helloworld:Chan...@192.168.1.100:5000/test
When bindings, application can fetch host ip address directly from ENV['host'] but not parse ENV['url'] string.
credentials
hostname: ****** #optional
host: 192.168.1.100
port: 5000
username: helloworld
password: ChangeMe
name: ****** #optional
db: test
url: mysql://helloworld:Chan...@192.168.1.100:5000/test
When bindings, application can fetch host ip address directly from ENV['host'] but not parse ENV['url'] string.
Subject: [vcap-dev] Failed to advertising brokered service, 403 error
Chunjie Zhu
Aug 8, 2012, 9:45:23 AM8/8/12
to vcap...@cloudfoundry.org
One obvious error,
acls:
users: [sa] <-- this use is cloudfoundry user, not database user
For the 500 error, could you please give more specific information?
Regards,
Chunjie
acls:
users: [sa] <-- this use is cloudfoundry user, not database user
For the 500 error, could you please give more specific information?
Regards,
Chunjie
From: "Aaron" <guowei...@163.com>
To: vcap...@cloudfoundry.org
Sent: Monday, August 6, 2012 4:31:26 PM
Subject: [vcap-dev] Re: Failed to advertising brokered service, 403 error
To: vcap...@cloudfoundry.org
Sent: Monday, August 6, 2012 4:31:26 PM
Subject: [vcap-dev] Re: Failed to advertising brokered service, 403 error
Aaron
Aug 19, 2012, 11:01:00 PM8/19/12
to vcap...@cloudfoundry.org
in broker_service_cli
the services.yml:
---
service_broker: http://service-broker.vcap.me
token: "changebrokertoken"
service:
name: xyz_hr_db
description: XYZ HR Database
version: "2.0"
options:
- name: rw
acls:
users: [guowei...@163.com]
wildcards: []
credentials:
conn: sqlserver://sa:123...@10.0.110.126:1433/test
D:\workspace\broker_service_cli\bin>ruby service_broker_cli
host:service-broker.vcap.me;port:80;url:/service-broker/v1/offerings.
Request Body:{"description":"XYZ HR Database","options":[{"name":"rw","acls":{"u
sers":["guowei...@163.com"],"wildcards":[]},"credentials":{"conn":"sqlserver://sa
:123...@10.0.110.126:1433/test"}}],"label":"xyz_hr_db-2.0"}..............
Failed to create service xyz_hr_db-2.0: status=500, response body=Internal Serve
r Error
在 2012年8月8日星期三UTC+8下午9时45分23秒，Chunjie Zhu写道：
the services.yml:
---
service_broker: http://service-broker.vcap.me
token: "changebrokertoken"
service:
name: xyz_hr_db
description: XYZ HR Database
version: "2.0"
options:
acls:
users: [guowei...@163.com]
wildcards: []
credentials:
conn: sqlserver://sa:123...@10.0.110.126:1433/test
D:\workspace\broker_service_cli\bin>ruby service_broker_cli
host:service-broker.vcap.me;port:80;url:/service-broker/v1/offerings.
Request Body:{"description":"XYZ HR Database","options":[{"name":"rw","acls":{"u
sers":["guowei...@163.com"],"wildcards":[]},"credentials":{"conn":"sqlserver://sa
:123...@10.0.110.126:1433/test"}}],"label":"xyz_hr_db-2.0"}..............
Failed to create service xyz_hr_db-2.0: status=500, response body=Internal Serve
r Error
在 2012年8月8日星期三UTC+8下午9时45分23秒，Chunjie Zhu写道：
conn: sqlserver://sa:123456@sqlserver.vcap.me/test
Aaron
Aug 19, 2012, 11:25:16 PM8/19/12
to vcap...@cloudfoundry.org
in ~/projects/.deployments/devbox/log/service_broker.log
RuntimeError - downstream app not set:
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:703:in `forward'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:787:in `route_missing'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:734:in `route!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:730:in `route!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:730:in `route!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:857:in `dispatch!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:659:in `block in call!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:823:in `block in invoke'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:823:in `catch'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:823:in `invoke'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:659:in `call!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:644:in `call'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:80:in `block in pre_process'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:53:in `process'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/bundler/gems/eventmachine-2806c630d863/lib/eventmachine.rb:256:in `run_machine'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/bundler/gems/eventmachine-2806c630d863/lib/eventmachine.rb:256:in `run'
/home/guowei/projects/vcap/bin/../services/service_broker/bin/service_broker:71:in `start'
/home/guowei/projects/vcap/bin/../services/service_broker/bin/service_broker:93:in `<main>'
在 2012年8月8日星期三UTC+8下午9时45分23秒，Chunjie Zhu写道：
RuntimeError - downstream app not set:
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:703:in `forward'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:787:in `route_missing'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:734:in `route!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:730:in `route!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:730:in `route!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:857:in `dispatch!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:659:in `block in call!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:823:in `block in invoke'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:823:in `catch'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:823:in `invoke'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:659:in `call!'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/sinatra-1.2.8/lib/sinatra/base.rb:644:in `call'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:80:in `block in pre_process'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:53:in `process'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/bundler/gems/eventmachine-2806c630d863/lib/eventmachine.rb:256:in `run_machine'
/home/guowei/projects/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/bundler/gems/eventmachine-2806c630d863/lib/eventmachine.rb:256:in `run'
/home/guowei/projects/vcap/bin/../services/service_broker/bin/service_broker:71:in `start'
/home/guowei/projects/vcap/bin/../services/service_broker/bin/service_broker:93:in `<main>'
在 2012年8月8日星期三UTC+8下午9时45分23秒，Chunjie Zhu写道：
conn: sqlserver://sa:123456@sqlserver.vcap.me/test
Chunjie Zhu
Aug 20, 2012, 5:37:35 AM8/20/12
to vcap...@cloudfoundry.org
Seems there is something wrong with ruby rack middleware, a webserver interface. I have not encountered fault of this type, not sure the root cause.
Have you tried to restart it? Does it crash frequently?
Regards,
Chunjie
Have you tried to restart it? Does it crash frequently?
Regards,
Chunjie
Sent: Monday, August 20, 2012 11:25:16 AM
Subject: Re: [vcap-dev] Re: Failed to advertising brokered service, 403 error
Subject: Re: [vcap-dev] Re: Failed to advertising brokered service, 403 error
conn: sqlserver://sa:123...@sqlserver.vcap.me/test
Reply all
Reply to author
Forward
0 new messages