Talend Remote Engine logs filled with message: org.apache.karaf.main.lock.SimpleFileLock lock INFO: Lock failed

[wei_guo]

After the Talend Remote Engine goes down, the Remote Engine logs repeatedly show the same message in TalendRemoteEngine/data/log/karaf.log:

org.apache.karaf.main.lock.SimpleFileLock lock INFO: Lock failed

Resolution

To resolve this, verify ownership and permissions of the application files, remove stale lock files, and restart the Talend Remote Engine:

1. Ensure that the dedicated Talend user and group have full recursive ownership over the application files to prevent any permission-related runtime errors:
   

   sudo chown talenduser:talendgroup /opt/talend/TalendRemoteEngine -R

   Adjust the absolute path `/opt/talend/` if your installation directory differs.
   
   
2. Stop the Talend Remote Engine Service: 

   sudo systemctl stop talend-remote-engine.service

3. Manually purge the stale or unsynced lock file that is blocking the engine startup:

   rm /opt/talend/TalendRemoteEngine/lock

4. Restart the Talend Remote Engine Service. The engine will automatically generate a fresh, synced lock file upon a successful boot.

   sudo systemctl start talend-remote-engine.service

Cause

An unexpected downtime or sudden disconnection of the Talend Remote Engine (RE) left the application's file lock (TalendRemoteEngine/lock) in an unsynced or stale state. Because the container detected this pre-existing lock file upon recovery, it assumed another process was already running, subsequently blocking all other dependent modules and services from initializing.

Environment

• Talend Remote Engine