Hi, You won't need the default_swift_cluster setting usually comment it and your swift cluster should start. if you really do then the format specified is incorrect, look at the commented config file here :
https://github.com/gholt/swauth/blob/master/etc/proxy-server.conf-sample#L43 Cheers, Chmouel. On Tue, Jan 3, 2012 at 3:40 AM, Asghar, Jonathan Edward (HP Cloud Services NOC) <jonathan.asg...@hp.com> wrote: > Hi, I was attempting to start up a swift proxy on a test environment and > it seems I’m running into a wall. My object-nodes are working fine from > what I can see but it seems that my proxy won’t start at all. **** > > ** ** > > The error I get starting it up is this:**** > > ** ** > > root@proxy:~# swift-init proxy start**** > > Starting proxy-server...(/etc/swift/proxy-server.conf)**** > > Traceback (most recent call last):**** > > File "/usr/bin/swift-proxy-server", line 22, in <module>**** > > run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)**** > > File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 123, > in run_wsgi**** > > loadapp('config:%s' % conf_file, global_conf={'log_name': log_name})** > ** > > File "/usr/lib/pymodules/python2.7/paste/deploy/loadwsgi.py", line 204, > in loadapp**** > > return loadobj(APP, uri, name=name, **kw)**** > > File "/usr/lib/pymodules/python2.7/paste/deploy/loadwsgi.py", line 225, > in loadobj**** > > return context.create()**** > > File "/usr/lib/pymodules/python2.7/paste/deploy/loadwsgi.py", line 625, > in create**** > > return self.object_type.invoke(self)**** > > File "/usr/lib/pymodules/python2.7/paste/deploy/loadwsgi.py", line 168, > in invoke**** > > app = filter(app)**** > > File "/usr/lib/pymodules/python2.7/swauth/middleware.py", line 1463, in > auth_filter**** > > return Swauth(app, conf)**** > > File "/usr/lib/pymodules/python2.7/swauth/middleware.py", line 123, in > __init__**** > > raise Exception('Invalid cluster format')**** > > Exception: Invalid cluster format**** > > ** ** > > ** ** > > My *proxy-server.conf* is as follows:**** > > ** ** > > root@proxy:~# cat /etc/swift/proxy-server.conf **** > > [DEFAULT]**** > > bind_port = 443**** > > cert_file = /etc/swift/cert.crt**** > > key_file = /etc/swift/cert.key**** > > workers = 8**** > > user = swift**** > > ** ** > > [pipeline:main]**** > > pipeline = healthcheck cache swauth proxy-server**** > > #pipeline = healthcheck cache auth proxy-server**** > > ** ** > > [app:proxy-server]**** > > use = egg:swift#proxy**** > > allow_account_management = true**** > > ** ** > > [filter:swauth]**** > > use = egg:swauth#swauth**** > > set log_name = swauth**** > > super_admin_key = swauthkey**** > > default_swift_cluster = https://10.0.0.2:443/v1**** > > ** ** > > #[filter:auth]**** > > #use = egg:swift#auth**** > > #ssl = true **** > > ** ** > > [filter:healthcheck]**** > > use = egg:swift#healthcheck**** > > ** ** > > [filter:cache]**** > > use = egg:swift#memcache**** > > memcache_servers = 10.7.11.9:11211**** > > root@proxy:~#**** > > ** ** > > I’ve done the googling on this, and it looks like most people have trouble > with the auth part, it’s either “uth” or “sauth” or “wauth” when it should > be “swauth.” As you can see I’ve tried both (the commented line) but my > goal is swauth so I’m asking with this configuration.**** > > Any advice or direction would be greatly appreciated! Thanks!**** > > ** ** > > ** ** > > --**** > > Best Regards,**** > > JJ Asghar**** > > HP Cloud Services**** > > 512-619-0722 - Cell**** > > [image: Description: signature_5]**** > > ** ** > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
