Thanks Clay that was exactly right!! I did the strings on the object.gz
file and saw that port 6003 was in there - kinda weird since when I did
swift-ring-builder object.builder I didnt show up?! In any case the
containers seem now work via command line but now I when try using the
Dashboard I get
oic, the proxy is on a different machine, and the storage node doesn't have
a proxy-server.conf - so the fact the proxy isn't starting on the storage
node is expected. That's probably fine.
But the thing with the port is... it *has* to be coming from a ring, the
ring on the proxy actually, specif
Thanks Clay. Yeah this is swift version 2.1.0. Ive done write_wring and
copied the new .gz files to the object node still getting same error. I
have no clue where port 6003 is coming from its driving me crazy :-)
On Thu, Oct 30, 2014 at 1:11 PM, Clay Gerrard
wrote:
> Well the device ports can
Well the device ports can only come from the rings. There is no default.
You're right the backend request is for an object - but maybe it's a
policy-1 ring? You said icehouse though so maybe this isn't swift 2.0?
The swift-init error for proxy is troubling - you should figure out if
maybe the prox
