ECS: Disabling Object-lock feature on ECS for IBM Content Manager
Resumen: IBM Content Manager fails to start on ECS 3.6.2 after restart of services when bucket has object-lock disabled.
Este artículo se aplica a
Este artículo no se aplica a
Este artículo no está vinculado a ningún producto específico.
No se identifican todas las versiones del producto en este artículo.
Síntomas
Application impacted by 501 errors. Below is observed from dataheadsvc.log on ECS:
dataheadsvc.log.20211016-013228.gz:2021-10-16T01:04:12,908 [qtp911357121-41701] INFO RequestLog.java (line 83) 1x.xx.1xx.xx GET //test-bucket/?object-lock= HTTP/1.1 501 3 – 160
Causa
ECS code version 3.6.2 Introduced the Object-lock feature, but there are two preconditions to enable the Object-lock for buckets on ECS:
- Object-lock does not work with ADO enabled bucket. This is addressed in 3.7.1.
- Object-lock does not work with Legacy users. (Non-IAM users)
Resolución
This limitation is known to affect applications like IBM Content Manager which checks for "?object-lock" after startup. Before 3.6.2, ECS was designed to ignore object-lock. Post 3.6.2 403, or 404 return codes are returned.
From 3.6.2.1 release and later, object-lock can be disabled if required using a patch. In 3.7 object lock can be disabled globally or enabled or disabled for specific buckets.
Contact Dell Technologies ECS support to have object-lock disabled if that is needed.
Propiedades del artículo
Número del artículo: 000192958
Tipo de artículo: Solution
Última modificación: 06 abr 2023
Versión: 6
Encuentre respuestas a sus preguntas de otros usuarios de Dell
Servicios de soporte
Compruebe si el dispositivo está cubierto por los servicios de soporte.