On Mar 1, 2013, at 8:05 AM, Paras pradhan wrote:
> Can somebody check if my endpoints are correct. 192.168.122.25 is my
> proxy node in which port is on with self signed certs.
>
> --
> public: http://192.168.122.25:/v1/AUTH_%(tenant_id)s
> internal: http://192.168.122.25:/v1/AUTH_
Ok it looks like a ssl issue. If I disable
#cert_file = /etc/swift/cert.crt
#key_file = /etc/swift/cert.key
it is working.
Do I need to change my endpoint to use ssl?
Thanks
Paras.
On Fri, Mar 1, 2013 at 10:05 AM, Paras pradhan wrote:
> Can somebody check if my endpoints are correct. 192.168
Can somebody check if my endpoints are correct. 192.168.122.25 is my
proxy node in which port is on with self signed certs.
--
public: http://192.168.122.25:/v1/AUTH_%(tenant_id)s
internal: http://192.168.122.25:/v1/AUTH_%(tenant_id)s
admin: http://192.168.122.25:/v1
-
Thanks,
Pa
That "goes infinite" seems like waiting connection. You should check
connection first.
To use "curl any_url" is ok. Any response depends on successful connection.
On Fri, Mar 1, 2013 at 5:41 AM, Paras pradhan wrote:
> Hi,
>
> I have a swift proxy node and a storage node. Also keystone resides i
Hi,
I have a swift proxy node and a storage node. Also keystone resides in
another server. Swift is from ubuntu cloud archive i.e 1.7.4. I am
using private keys in swift proxy if it matters.The below command is
returning nothing and goes infinite.192.168.122.20 is my keystone
server.
--
root@cont
5 matches
Mail list logo