Unable to install or access Imunify360 after the Imunify360 Extension was installed, the page is constantly reloading and refreshing on its own

Symptoms

• Unable to install or access Imunify360 after the Imunify360 Extension was installed, the page is constantly reloading and refreshing on its own

• The following error can be found in /var/log/i360deploy.log:

  Installation daemon created pid file /usr/local/psa/var/modules/imunify360/installation.pid Installation daemon forked first time Installation daemon forked second time Installation daemon initialized Starting i360deploy.sh
  [2023-10-07 11:27:15] Checking for an update to i360deploy.sh
  [2023-10-07 11:27:15] Downloading i360deploy.sh.repo_version (please wait)
  [2023-10-07 11:27:16] i360deploy.sh is already the latest version (2.82) - continuing Detecting ostype... centos In a few moments the script will install latest imunify360-firewall package (w/dependencies)... (Ctrl-C to cancel)
  [2023-10-07 11:27:25] Failed to get package version

• The following error can be found in the Plesk debug log:

  [2023-10-07 12:12:25.694] 2319039:65212f09a4e02 DEBUG [util_exec] [212f5c49c2b1a43ea68f0983e19b86c8-0] Starting: filemng root list files /usr/local/psa/var/modules/imunify360/tmp-executeWxAaUh --in-bytes --allow-root, stdin:
  [2023-10-07 12:12:25.695] 2319023:65212f0996444 DEBUG [extension/imunify360] [65212f09a7327] Finished in 0.01018s, Error code: 1, stdout: execute.py: execve failed for /usr/local/psa/admin/sbin/modules//imunify360/execute.py: No such file or directory
  System error 2: No such file or directory
  , stderr: execute.py: execve failed for /usr/local/psa/admin/sbin/modules//imunify360/execute.py: No such file or directory
  System error 2: No such file or directory

• The following error occurs when executing the deployment script /usr/local/psa/admin/sbin/modules/imunify360/i360deploy.sh manually:

  # /usr/local/psa/admin/sbin/modules/imunify360/i360deploy.sh
  Checking for an update to i360deploy.sh
  Downloading i360deploy.sh.repo_version (please wait)
  New version (2.82) of i360deploy.sh detected
  Do you want to run i360deploy.sh 2.82 now (y/n) ?
  y
  OK, executing i360deploy.sh.repo_version
  Download of i360deploy.sh 2.82 successful
  Run /usr/local/psa/admin/sbin/modules/imunify360/i360deploy.sh
  Skipping check version
  Detecting ostype... centos
  In a few moments the script will install latest imunify360-firewall package (w/dependencies)... (Ctrl-C to cancel)
  [2023-10-07 12:15:58] Failed to get package version

• Repository error occurs when executing package update or repository reload, e.g.:

  # yum update
  ...
  Errors during downloading metadata for repository 'mariadb-main':
  - Status code: 404 for https://dlm.mariadb.com/repo/mariadb-server/10.7/yum/rhel/8/x86_64/repodata/e3833871afca2d811714f593ca811a49aa164403fe90dce8fa162127d4accbaa-updateinfo.xml.gz 
  - Status code: 404 for https://dlm.mariadb.com/repo/mariadb-server/10.7/yum/rhel/8/x86_64/repodata/87f4cced936ba0b45379e14a9a76e20837bdffcfff567065bc344e9af1fb6e4c-filelists.xml.gz 
  - Status code: 404 for https://dlm.mariadb.com/repo/mariadb-server/10.7/yum/rhel/8/x86_64/repodata/222709914d36d4a0fd607616111adc273a0822b3d990597747cb4aac88c80396-primary.xml.gz 
  Error: Failed to download metadata for repo 'mariadb-main': Yum repo downloading error: Downloading error(s): repodata/87f4cced936ba0b45379e14a9a76e20837bdffcfff567065bc344e9af1fb6e4c-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/e3833871afca2d811714f593ca811a49aa164403fe90dce8fa162127d4accbaa-updateinfo.xml.gz - Cannot download, all mirrors were already tried without success; repodata/222709914d36d4a0fd607616111adc273a0822b3d990597747cb4aac88c80396-primary.xml.gz - Cannot download, all mirrors were already tried without success

Cause

Broken/unavailable repository preventing yum from the correct deployment of the Imunify360.

Resolution

1. Connect to the server via SSH

2. Comment out the broken repository from the error message or rename the repository file. In this particular case /etc/yum.repos.d/mariadb.repo:

   # mv /etc/yum.repos.d/mariadb.repo /etc/yum.repos.d/mariadb.repo.old

3. Reinstall the Imunify360 extension and deploy it again via the extension interface