Azure connected object store unavailable due to internal server error
Applies to
- ONTAP 9
- Microsoft Azure
- FabricPool
Issue
Azure connected object store continuously becomes unavailable and available due to an internal server error
Mon May 01 00:33:21 0100 [cluster-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp1" from node bd9550df-40e1-11ec-89a0-d039ea3ad3eb. Reason: Internal server error.
Mon May 01 00:33:24 0100 [cluster-01: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "fp1" from node bd9550df-40e1-11ec-89a0-d039ea3ad3eb.
Mon May 01 00:40:06 0100 [cluster-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp1" from node bd9550df-40e1-11ec-89a0-d039ea3ad3eb. Reason: Internal server error.
Mon May 01 00:40:07 0100 [cluster-01: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "fp1" from node bd9550df-40e1-11ec-89a0-d039ea3ad3eb.
Mon May 01 00:56:32 0100 [cluster-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "fp1" from node bd9550df-40e1-11ec-89a0-d039ea3ad3eb. Reason: Internal server error.
Mon May 01 00:56:36 0100 [cluster-01: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "fp1" from node bd9550df-40e1-11ec-89a0-d039ea3ad3eb.