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

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

本文章適用於 本文章不適用於 本文無關於任何特定產品。 本文未識別所有產品版本。
查看其他資源

症狀

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

原因

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)

解析度

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.

文章屬性
文章編號: 000192958
文章類型: Solution
上次修改時間: 06 4月 2023
版本:  6
向其他 Dell 使用者尋求您問題的答案
支援服務
檢查您的裝置是否在支援服務的涵蓋範圍內。