SCC Initialize Locking File Failed

Symptom

A task checked by the sonarqube engine fails, and the log contains "scc initialize locking file failed".

Cause Analysis

No lock is available. The disk does not support lock, or the nfslock service is not enabled.

Solution

1. Log in to the executor where the check task is executed as the root user.
2. Run the following commands to ensure that the rpcbind service is running:

   bash
   systemctl start rpcbind
   systemctl enable rpcbind

3. Run the following commands to start the nfslock service:

   bash
   systemctl start nfs-server
   systemctl enable nfs-server

   If the system displays a message indicating that the nfslock service does not exist, use nfs-server or nfs-kernel-server to start the NFS service.

4. Run the following commands to check whether the nfslock service is started successfully. If not, go to 3 to restart the service.

   bash
   systemctl status nfs-server

5. Ensure that the shared directory is configured in the /etc/exports file and that the /etc/sysconfig/nfs configuration file of the nfslock service is correctly set.
6. If the NFS configuration file is modified, run the following commands to restart the NFS service for the modification to take effect:

   bash
   systemctl restart nfs-server

7. Check the firewall settings to ensure that the firewall does not block the ports required by the NFS service. If the ports are blocked, add rules to allow NFS traffic to pass through.