In case of SSYNC replication error, the body of the error is not logged, which does not help to diagnose the issue. Example:
object-server: ssync subrequest failed with 500: POST /disk-00-001/34159/AUTH_***/***/***
It should log body to provid emore informations. In this case:
object-server: ssync subrequest failed with 500: POST /disk-00-001/34159/AUTH_***/***/*** (Traceback (most recent call last):#012 File "/opt/swift-2.18.0-ovh398/local/lib/python2.7/site-packages/swift/obj/server.py", line 1242, in __call__#012 res = getattr(self, req.method)(req)#012 File "/opt/swift-2.18.0-ovh398/local/lib/python2.7/site-packages/swift/common/utils.py", line 1796, in _timing_stats#012 resp = func(ctrl, *args, **kwargs)#012 File "/opt/swift-2.18.0-ovh398/local/lib/python2.7/site-packages/swift/obj/server.py", line 602, in POST#012 if new_delete_at and new_delete_at < req_timestamp:#012 File "/usr/lib/python2.7/functools.py", line 56, in <lambda>#012 '__lt__': [('__gt__', lambda self, other: not (self < other or self == other)),#012 File "/opt/swift-2.18.0-ovh398/local/lib/python2.7/site-packages/swift/common/utils.py", line 1180, in __lt__#012 other = Timestamp(other)#012 File "/opt/swift-2.18.0-ovh398/local/lib/python2.7/site-packages/swift/common/utils.py", line 1092, in __init__#012 raise ValueError('timestamp too large')#012ValueError: timestamp too large#012)
Just to be clear you're thinking the ssync_reciever might be able to grab the subrequest response error and log it in the source replicator/ reconstructor logs?