{"id":1658,"date":"2023-07-31T12:14:01","date_gmt":"2023-07-31T11:14:01","guid":{"rendered":"https:\/\/hoganhost.com.ng\/blog\/?p=1658"},"modified":"2024-08-12T13:25:28","modified_gmt":"2024-08-12T12:25:28","slug":"node-js-selector-not-working-with-an-error-cant-acquire-lock-for-app-in-cpanel","status":"publish","type":"post","link":"https:\/\/hoganhost.com.ng\/blog\/node-js\/node-js-selector-not-working-with-an-error-cant-acquire-lock-for-app-in-cpanel\/","title":{"rendered":"Node.JS Selector not Working with an Error “Can’t acquire lock for app” in cPanel"},"content":{"rendered":"

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

If you encounter the error message “Can’t acquire lock for an app<\/strong>” it is likely because some processes are utilizing the “.lock<\/strong>” file of your NodeJS application.<\/p>\n

This typically occurs when a daemon script was initiated using the Node.JS Selector -> Run NPM Script feature. Unfortunately, scripts started this way cannot be stopped via the UI and will continue running in the background, holding a lock for the application. Consequently, any attempts to perform actions on the app after launching such a daemon script will result in the “Can’t acquire lock for app” error.<\/p>\n

To resolve this issue, follow these steps:<\/p>\n

As the root user, run the lsof command: lsof -u username | grep lock<\/p>\n

This will display a list of lock processes that you need to terminate. To kill a specific process (where XXXXXX is the process number), use the following command: kill -9 XXXXXX<\/p>\n

If you have multiple processes, you can list their IDs.<\/p>\n

To avoid encountering this problem in the future, avoid launching daemon scripts via the NodeJS Selector UI.<\/p>\n

 <\/p>\n

 
\n