Handling Method When "add sem proc lock failed" Is Printed by the CLI

Symptom

When AI-VAULT is running and processes a request, "add sem proc lock failed" is printed on the CLI.

Figure 1 "add sem proc lock failed" printed on the CLI

Possible Causes

The default permission on the lock semaphore of the KMC key file is 600. Common users do not have the permission to access the semaphore whose owner is the root user. In normal cases, the owner is the user process that runs AI-VAULT. If the semaphore of a common user is occupied by the root user, the common user does not have the permission to access the semaphore and "add sem proc lock failed" is reported.

Figure 2 A common user as the owner of the semaphore in normal cases

Figure 3 Semaphore occupied by the root user in exception cases

Solution

Run the ipcs -s command to check the semaphore and run the ipcrm -S command to delete the semaphore (0x2016****) preempted by the root user.

Figure 4 Run the ipcs -s command to check the semaphore.

Figure 5 Run the ipcrm -S command to delete the semaphore.