Xray 3.111.9 Fails to Start After Installation

[megha1906]

Issue
While installing Xray version 3.111.9, there is a known issue that may prevent Xray from starting successfully. If you encounter this issue, you may see the following stack trace in the logs:

TASK [xray : Restart xray] ***********************************************************************************************************************************************
task path: /Users/ubuntu/platform/platform/products/ansible/ansible_collections/jfrog/platform/roles/xray/tasks/install.yml:181
NOTIFIED HANDLER xray : Restart xray for xray-1
META: triggered running handlers for xray-1

RUNNING HANDLER [xray : Restart xray] ************************************************************************************************************************************
task path: /Users/ubuntu/platform/platform/products/ansible/ansible_collections/jfrog/platform/roles/xray/handlers/main.yml:3
fatal: [xray-1]: FAILED! => {
    "changed": false
}

MSG:

Unable to start service xray: Job for xray.service failed because the control process exited with error code.
See "systemctl status xray.service" and "journalctl -xeu xray.service" for details.


PLAY RECAP ***************************************************************************************************************************************************************
artifactory-1              : ok=39   changed=22   unreachable=0    failed=0    skipped=9    rescued=0    ignored=0
postgres-1                 : ok=23   changed=12   unreachable=0    failed=0    skipped=0    rescued=0    ignored=1
xray-1                     : ok=37   changed=16   unreachable=0    failed=1    skipped=19   rescued=0    ignored=0

Solution
To resolve this issue, please follow these steps:

1. Navigate to /opt/jfrog/xray/var/etc and create a new file named installerState.yaml with the following content:

installation_method: all

2. Re-run the Ansible playbook to complete the installation.

[megha1906]

We at JFrog are actively working on a fix for this issue. Meanwhile, you can apply the above workaround to resolve it.