Thanks Matthew for your reply
Problem is resolved now both object and container ring was using same port.
Changing the port in ring configuration fixed the issue and we are able to
upload the files now.
Aravind M D
On Tue, Feb 13, 2018 at 3:59 AM, Matthew Oliver wrote:
> Hi Aravind,
>
> There
Hi Aravind,
There only seems to be container-server logs in your reply. So you have any
from the object server?
Also what ports are your object-server and container-servers listening on?
Your ring is saying the object-servers are listening on 6201. Just making
sure the port numbers aren't confused
Hi Clay, Hi All,
Configured my cluster from ground up with one proxy node and one storage
node.
Now I am getting two types of errors.
Large files:
Feb 3 18:12:33 centos7-swift-proxy1 swift-proxy-server: ERROR with Object
server 192.168.47.128:6201/sda re: Trying to write to /AUTH_admin/ara1
One replica is a little strange. Do the uploads *always* fail - in the
same way? Or is this just one example of a PUT that returned 503? Are you
doing a lot of concurrent PUTs to the same object/name/disk?
The error from the log (EPIPE) means the object-server closed the
connection as the proxy
