Open Stack

Of course.

# cat /etc/swift/proxy-server.conf
[DEFAULT]
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port = 8888
bind_ip = <host>
workers = 8
user = swift
log_facility = LOG_LOCAL1
log_level = DEBUG

[pipeline:main]
pipeline = catch_errors healthcheck cache authtoken keystone proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

[filter:keystone]
paste.filter_factory = keystone.middleware.swift_auth:filter_factory
operator_roles = admin, swift

[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = 0
auth_protocol = http
service_port = 5000
service_host = <host>
auth_port = 35357
auth_host = <host>
auth_uri = http://<host>:5000/
auth_token = 6bde76d029582066e4ee2edcf0d1c212
admin_token = 6bde76d029582066e4ee2edcf0d1c212
admin_tenant_name = service
admin_user = swift
admin_password = swiftpass
signing_dir = /etc/swift

[filter:healthcheck]
use = egg:swift#healthcheck

[filter:cache]
use = egg:swift#memcache
memcache_servers = <host>:11211

[filter:catch_errors]
use = egg:swift#catch_errors


2013/2/2 Chmouel Boudjnah <chmouel at chmouel.com>

> You probably want to past your proxy-server.conf this may be helpful for
> us to help you.
>
> Chmouel.
>
>
> On Fri, Feb 1, 2013 at 8:49 PM, David Goetz <david.goetz at rackspace.com>wrote:
>
>> I'm sorry- I didn't read that part about the proxy restart :)  The proxy
>> may not log if it gets hung up in some middleware. What middleware do you
>> have running?  You can try adding in some log messages into the middleware
>> you have running to find out where.
>>
>>
>> On Feb 1, 2013, at 1:37 PM, David Goetz wrote:
>>
>> > Sounds like swift isn't listening on that port. What is the bind_port
>> in your proxy-server.conf?
>> >
>> >
>> > On Feb 1, 2013, at 12:53 PM, Andrey V. Romanchev wrote:
>> >
>> >> Hello!
>> >> I've installed swift + keystone and have incomprehensible problem
>> >>
>> >> First of all I get auth tokens
>> >> curl -d '{"auth": {"tenantName": "service",
>> "passwordCredentials":{"username": "swift", "password": "swiftpass"}}}' -H
>> "Content-type: application/json" http://<host>:5000/v2.0/tokens | python
>> -mjson.tool
>> >>
>> >> This command works fine, I get token id and publicURL
>> >>
>> >> Then
>> >> curl -H "X-AUTH-TOKEN: cf1d44080a184e6c8f94e3fe52e89d48" http://
>> <host>:8888/v1/AUTH_b74d4d57b1f5473bb2d8ffe5110a3d5a
>> >>
>> >> This command just hangs and that's all. No swift logs, no response.
>> >> If I restart proxy server, I get on client side
>> >> curl: (56) Recv failure: Connection reset by peer
>> >>
>> >> I've completely stuck here. I even turned on debug logs in swift-proxy
>> - no result as well.
>> >> Is there any possibility to understand what's wrong?
>> >> _______________________________________________
>> >> Mailing list: https://launchpad.net/~openstack
>> >> Post to     : openstack at lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~openstack
>> >> More help   : https://help.launchpad.net/ListHelp
>> >
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to     : openstack at lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130204/d63cd84d/attachment.html>