Article ID: 114204, created on Jun 26, 2012, last review on May 9, 2014

  • Applies to:
  • Operations Automation

Symptoms

APS Application instance cannot be installed with the error message Permission denied like shown below:
Task ID 8832654
Queue name domain_service414630
Task name Executing configuration script for APS application instance with id 85987
Task description Executing configuration script for APS application instance with id 85987
Queue status Failed
Start not earlier than Jun-14-2012 11:55
Method name taskExecuteInstanceControlCommand on SCREF:apache:0
Last execution output Script execution failed: executing 'env 'WEB___DIR=/usr/local/sitipersonali/sitipersonali12/NSP/ja/ar/jarretesting/webspace/siteapps/85987/htdocs' 'SETTINGS_title=My Joomla' 'SETTINGS_admin_email=usermail@domain.tld' 'SERVICE_ID=' 'PHP_VERSION=5.2.17' 'DB_main_VERSION=5.0.83' 'DB_main_TYPE=mysql' 'DB_main_PASSWORD=somepassword' 'DB_main_NAME=db174_sa136_main' 'DB_main_LOGIN=u174_sa136' 'DB_main_HOST=10.20.30.40' 'BASE_URL_SCHEME=http' 'BASE_URL_PATH=myuri/' 'BASE_URL_HOST=myjoomla.tld' 'BASE_IP_ADDRESS=64.131.89.6' /usr/libexec/php5-cgi/bin/php-cgi -d open_basedir= -q configure 'install'' for APS application instance with id 85987 returned value '255' with output '' and errors 'PHP Warning: require_once(env-parser.php): failed to open stream: Permission denied in /usr/local/sitipersonali/sitipersonali12/NSP/ja/ar/jarretesting/webspace/siteapps/85987/scripts/configure on line 4 PHP Fatal error: require_once(): Failed opening required 'env-parser.php' (include_path='.') in /usr/local/sitipersonali/sitipersonali12/NSP/ja/ar/jarretesting/webspace/siteapps/85987/scripts/configure on line 4 '

Cause


Most likely the system user of the webspace does not have enough permissions to access web application files or folders.

Resolution


  1. Log in to POA Provider CP and go to Top > System Director > Task Manager > Scheduled Tasks
  2. Click on the failed task in question
  3. Find the host_id, path and hd_user under Task Parameters:
  4. Log in to the host with the found host_id. Depending on hosting type of the webspace you may find the IP address of the host in the following locations:
    • Legacy (Linux Shared) Hosting on physical server: Top > Deployment Director > Server Manager > Hardware Nodes
    • Legacy (Linux Shared) Hosting on shared VPS: Top > Service Director > Virtuozzo Manager > VPSs
    • NG Hosting: Top > Deployment Director > Server Manager > Web Clusters > Web Cluster
  5. Check if the user is able to access webspace content found as path in p.3:
    su -s /bin/bash HD_USER
    ls -l /path/to/webspace
    NOTE: Replace HD_USER with actual user name found in p.3
  6. If the user does not have enough permissions (read and execute) add corresponding permissions as a root:chmod o+rx /path/to/webspace
  7. Re-run the task in POA Provider CP

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF