FS System: fspmd UNABLE_TO_ACQUIRE_LOCK

Asset ID:	1-72-2033603.1
Update Date:	2018-01-03
Keywords:

Solution Type Problem Resolution Sure

Solution 2033603.1 : FS System: fspmd UNABLE_TO_ACQUIRE_LOCK_ERROR

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

UNABLE_TO_ACQUIRE_LOCK_ERROR recorded in hosts messages file

Jul 10 11:28:17 hostname fspmd[378]: response from AK87654321 reports parameter error: <UNABLE_TO_ACQUIRE_LOCK_ERROR>
Jul 10 11:28:17 hostname fspmd[378]: Received Response to MGMTILIB_PERFORM_CONFIGURE_SAN_HOST_V2 from AK87654321 with Status -2
Jul 10 11:28:17 hostname fspmd[378]: Resetting Connection to AK87654321 after Error in Response
Jul 10 11:28:17 hostname fspmd[378]: SSL_read failed: returned 0, SSL_ERROR_SYSCALL; socket error 0, Error 0
Jul 10 11:28:17 hostname fspmd[378]: Connection to Pilot AK87654321 from Host xxx.yyy.abc.de state 2 Reset
Jul 10 11:28:17 hostname fspmd[378]: SSL read from AK87654321 failed
Jul 10 11:28:17 hostname fspmd[378]: recvMsg AK87654321 failed MGMTILIB_SSL_ERROR
Jul 10 11:28:17 hostname fspmd[378]: response from AK12345678 reports invalid parameter: </Message/Request/ApmPerformConfigureSanHost/Name>
Jul 10 11:28:17 hostname fspmd[378]: response from AK12345678 reports parameter error: <UNABLE_TO_ACQUIRE_LOCK_ERROR>
Jul 10 11:28:17 hostname fspmd[378]: Received Response to MGMTILIB_PERFORM_CONFIGURE_SAN_HOST_V2 from AK12345678 with Status -2
Jul 10 11:28:17 hostname fspmd[378]: Resetting Connection to AK12345678 after Error in Response
Jul 10 11:28:17 hostname fspmd[378]: Connection to Pilot AK12345678 from Host xxx.yyy.abc.de state 2 Reset
Jul 10 11:28:17 hostname fspmd[378]: SSL_read failed: returned 0, SSL_ERROR_SYSCALL; socket error 0, Error 0
Jul 10 11:28:17 hostname fspmd[378]: SSL read from AK12345678 failed
Jul 10 11:28:17 hostname fspmd[378]: recvMsg AK12345678 failed MGMTILIB_SSL_ERROR

Cause

UNABLE_TO_ACQUIRE_LOCK_ERROR can be observed when two administrative actions occur at the same time.

The lock is removed when the administration action has completed.

A host with FSPM installed (fspmd daemon) may log such a message if there is an ongoing administration action on the array. This indicates there is an array config change that requires the use of a lock occurring over a period of time.

In the above instance, one array was performing a System (COD) reset and the other performing QoS rebalancing.

The messages stopped once the COD reset was completed along with the rebalance.

Solution

The lock will automatically be removed when the administration action completes. Retry operation if required on host.

Attachments

This solution has no attachment