Unable To Preview Project Status Report With ERROR: EACCES

Products

• Clarity PPM On Premise

Issue/Introduction

On Linux implementation, unable to Preview Project > Status > Status Report instance

The APP shows error:

Caused by: com.microsoft.playwright.impl.DriverException: Error { message='Failed to launch: Error: spawn /opt/niku/clarity/playwright/chromium-1117/chrome-linux/chrome EACCES name='Error stack='Error: Failed to launch: Error: spawn /opt/niku/clarity/playwright/chromium-1117/chrome-linux/chrome EACCES at ChildProcess.<anonymous> (/opt/niku/clarity/tomcat-app-deploy/temp/playwright-java-13096669462612315277/package/lib/utils/processLauncher.js:132:14) at Object.onceWrapper (node:events:633:26) at ChildProcess.emit (node:events:530:35) at ChildProcess._handle.onexit (node:internal/child_process:292:12) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) }

 

Cause

EACCES essentially means "Permission denied."
If the Linux user does not have the necessary execute permissions for the Chromium executable located at /opt/niku/clarity/playwright/chromium-1117/chrome-linux/chrome, 
the EACCES will be thrown.

Ensure permissions are granted for the user running Clarity

 

Resolution

Here is an example, given the following:
CLARITY_INSTALL = /opt/niku/clarity

1. Run the following command to find out user running Clarity:

ps aux | grep tomcat

2. Run the following commands to check the folder/file permissions on the chrome executable

a.
cd /opt/niku/clarity/playwright/chromium-1117/chrome-linux

b.
ls -l chrome

If the output is:
-rwxrwxr-x 1 clarity clarity 346021984 Jun 11 14:13 chrome

This means the write permission is missing.
The solution is to: 

Review each directory path leading to the the last folder, will need the execute (x) permission.

Perform the command: ls -ld 
for each folder, i.e.

ls -ld /opt
ls -ld /opt/niku
ls -ld /opt/niku/clarity
ls -ld /opt/niku/clarity/playwright
ls -ld /opt/niku/clarity/playwright/chromium-1117
ls -ld /opt/niku/clarity/playwright/chromium-1117/chrome-linux

Look for the x permission for the user, group, or others for the clarity user/clarity group.

If any of these parent directories lack the x bit for the relevant user/group, then the chrome executable cannot be accessed.

Run the [chmod +x] command to give write permissions to the Chrome executable folder path