ECS: Disabling Object-lock feature on ECS for IBM Content Manager

Summary: IBM Content Manager fails to start on ECS 3.6.2 after restart of services when bucket has object-lock disabled.

Acest articol se aplică pentru Acest articol nu se aplică pentru Acest articol nu este legat de un produs specific. Acest articol nu acoperă toate versiunile de produs existente.
Consultați alte resurse

Symptoms

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

Cause

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)

Resolution

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.

Proprietăți articol
Article Number: 000192958
Article Type: Solution
Ultima modificare: 06 Apr 2023
Version:  6
Găsiți răspunsuri la întrebările dvs. de la alți utilizatori Dell
Servicii de asistență
Verificați dacă dispozitivul dvs. este acoperit de serviciile de asistență.