hey guys

thanks it worked, i had a different address saved in the keystone endpoint
for swift, but I still get the same error on the dashboard.

here's the command that worked and the output:
swift -v -V 2.0 -A http://10.17.12.163:5000/v2.0/ -U admin:admin -K admin
stat
StorageURL: http://10.17.13.29:8080/v1/AUTH_db70ab799000449eb51c2b490c2591ee
Auth Token: 7030c42e528d4d70bdc48da26da59b4f
   Account: AUTH_db70ab799000449eb51c2b490c2591ee
Containers: 0
   Objects: 0
     Bytes: 0
Accept-Ranges: bytes
X-Trans-Id: tx3089d0c2ccb34155ad9d7934442e2007

here's the error from the dashboard http://pastebin.com/w6HxYfaB

how do i fix this?

On Sat, Aug 11, 2012 at 9:44 PM, Kuo Hugo <tonyt...@gmail.com> wrote:

> I used to debug via curl for separating the AUTH section(Keystone) and
> Data Section(Swift-proxy) .
>
>  #>curl -v -d {%json%}  http://keystone_ip:port/v2.0
>  #>curl -H "X-AUTH-TOKEN: %TOKEN%" http://swift_ip:port/v1/AUTH_%account%
>
> And monitor the log on both keystone and swift.
>
> Several Steps you can followed
>
> 1. Check keystone is working on proper port
> 2. Check Swift is working and on proper port
> 3. Check swift endpoint under Keystone's DB
> 4. Does the network accessible between keystone and Swift
>
>
>
> 2012/8/12 Miguel Alejandro González <maggo...@gmail.com>
>
>> Hello
>>
>> I have 3 nodes with ubuntu 12.04 server and installed openstack with
>> packages from the ubuntu repos
>>
>>    - controller (where keystone is installed)
>>    - compute
>>    - swift
>>
>> I'm trying to configure Swift with Keystone but I'm having some problems,
>> here's my proxy-server.conf
>>
>> [DEFAULT]
>> bind_port = 8080
>> user = swift
>> swift_dir = /etc/swift
>> [pipeline:main]
>> # Order of execution of modules defined below
>> pipeline = catch_errors healthcheck cache authtoken keystone proxy-server
>> [app:proxy-server]
>> use = egg:swift#proxy
>> allow_account_management = true
>> account_autocreate = true
>> set log_name = swift-proxy
>> set log_facility = LOG_LOCAL0
>> set log_level = INFO
>> et access_log_name = swift-proxy
>> set access_log_facility = SYSLOG
>> set access_log_level = INFO
>> set log_headers = True
>> account_autocreate = True
>> [filter:healthcheck]
>> use = egg:swift#healthcheck
>> [filter:catch_errors]
>> use = egg:swift#catch_errors
>> [filter:cache]
>> use = egg:swift#memcache
>> set log_name = cache
>> [filter:authtoken]
>> paste.filter_factory = keystone.middleware.auth_token:filter_factory
>> auth_protocol = http
>> auth_host = 10.17.12.163
>> auth_port = 35357
>> auth_token = admin
>> service_protocol = http
>> service_host = 10.17.12.163
>> service_port = 5000
>> admin_token = admin
>> admin_tenant_name = admin
>> admin_user = admin
>> admin_password = admin
>> delay_auth_decision = 0
>> [filter:keystone]
>> paste.filter_factory = keystone.middleware.swift_auth:filter_factory
>> operator_roles = admin, swiftoperator
>> is_admin = true
>>
>> On Horizon I get a Django error page and says [Errno 111] ECONNREFUSED
>>
>> From the Swift server I try this command:
>>
>> swift -v -V 2.0 -A http://10.17.12.163:5000/v2.0/ -U admin:admin -K
>> admin stat
>>
>> And I also get [Errno 111] ECONNREFUSED
>>
>>
>> Is there any way to debug this??? Is there any conf or packages that I'm
>> missing for this to work on a multi-node deployment? Can you help me?
>>
>> Regards!
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> +Hugo Kuo+
> tonyt...@gmail.com
> + <tonyt...@gmail.com>886 935004793
>
>
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to