Resolved Execution of Extensions scripts error "Permission Denied"

[EmilioO]

After panel upgrade extensions wont install correctly.

My system:

• OS: Ubuntu 16.04
• Plesk: Onyx 17.5.3 Update 4
• mod_fcgid: libapache2-mod-fcgid-psa 2.3.9.5-ubuntu16.04.17031614

Error:
Datagrid Extension

Error: Execution dgri-admin-info.sh has failed with exit code 126, stdout: , stderr: sh: /opt/psa/admin/bin/modules/dgri/dgri-admin-info.sh: Permission denied

KernelCare Extension

Execution of /opt/psa/admin/plib/modules/kernelcare-plesk/scripts/post-install.php failed with exit code 1 and the output:
[2017-05-09 19:26:45] ERR [panel] Execution silent_install_kcare.sh has failed with exit code 126, stdout: , stderr: sh: /opt/psa/admin/bin/modules/kernelcare-plesk/silent_install_kcare.sh: Permission denied
:
0: /opt/psa/admin/plib/pm/ApiCli.php:150
pm_ApiCli::_filterResult(string 'silent_install_kcare.sh', integer '126', string '', string 'sh: /opt/psa/admin/bin/modules/kernelcare-plesk/silent_install_kcare.sh: Permission denied
', integer '5')
1: /opt/psa/admin/plib/pm/ApiCli.php:143
pm_ApiCli::_execCommand(string 'silent_install_kcare.sh', string ''/opt/psa/admin/bin/modules/kernelcare-plesk/silent_install_kcare.sh' ', integer '5', array)
2: /opt/psa/admin/plib/pm/ApiCli.php:91
pm_ApiCli::callSbin(string 'silent_install_kcare.sh')
3: /opt/psa/admin/plib/modules/kernelcare-plesk/library/Detector.php:7
Modules_KernelcarePlesk_Detector::silentInstallKernelCare()
4: /opt/psa/admin/plib/modules/kernelcare-plesk/scripts/post-install.php:5
ERROR: pm_Exception_ResultException: Execution silent_install_kcare.sh has failed with exit code 126, stdout: , stderr: sh: /opt/psa/admin/bin/modules/kernelcare-plesk/silent_install_kcare.sh: Permission denied
(ApiCli.php:150)

I've tried with:

1. plesk repair fs
2. manually change folder permission from root:root to psaadmsaadm
3. reinstalling other extension from plesk installer (git, security advisor)

 

[UFHH01]

Hi EmilioO,

manually change folder permission from root:root to psaadm : psaadm

... bad idea. ALL extensions have the very same permissions: root : root

Pls. consider to repair your Plesk installations with the command:

plesk repair installation -y -v

followed by

plesk repair all -y -v

... and post the relevant depending logs ( repair / installation ) from "/var/log/plesk" if your experience further issues/errors/problems.

 

[EmilioO]

I've reverted modules folder ownership from psadm to root and exec both plesk repair commands but not fix module installation problems.


plesk repair installation -y -v OUTPUT LOGS:

/var/log/plesk/install/plesk_17.5.3_repair.log

START Bootstrapper 17.5.3 repair AT Wed May 10 12:18:44 CEST 2017
Started bootstrapper repair procedure (fast mode). This may take a while.
Certain actions may be skipped if not applicable.

/usr/sbin/mysqld (pid 19838) is running...
 Finishing up upgrade procedures and rerunning previously failed upgrade actions...
 Trying to allow INNODB engine... done
Restarting mysql Trying to restart service mysql... done

**** Turn mysql-innodb VPS optimized aspect off: completed successfully.

===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
 Reconfiguring Apache web server...
 Reconfiguring ProFTPD FTP server...
 Reconfiguring AWStats web statistics...
 Reconfiguring WatchDog...
 Restoring SELinux contexts...
 Reconfiguring SSL ciphers and protocols...
 Trying to reload service courier-imapd... done
 Trying to reload service courier-imaps... done
 Trying to reload service courier-pop3d... done
 Trying to reload service courier-pop3s... done
 Trying to reload service sw-cp-server... done
 Trying to reload service apache2... done
 Trying to reload service postfix... done
 Trying to reload service courier-imapd... done
 Trying to reload service courier-imaps... done
 Trying to reload service courier-pop3d... done
 Trying to reload service courier-pop3s... done
 Cleaning active Panel sessions...

Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_17.5.3_repair.log' and '/var/log/plesk/install/plesk_17.5.3_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Parallels support.
STOP Bootstrapper 17.5.3 repair AT Wed May 10 12:19:20 CEST 2017

/var/log/plesk/repair-20170510-121920

[2017-05-10 12:18:44]
[2017-05-10 12:18:44] Reconfiguring the Plesk installation
[2017-05-10 12:18:44] Reconfiguring the Plesk installation ............................
[2017-05-10 12:19:20] [OK]

plesk repair all -y -v output (I've omitted vhosts fs verbose for privacy reasons)

Attached file.

Thanks.

 

[UFHH01]

plesk repair all -y -v output (I've omitted vhosts fs verbose for privacy reasons)

... well, you have 42 Warnings in your log, which can't be investigated because of your cuts at the log - file. Pls. don't expect us to guess, what could be wrong, because this is only time - consuming and mostly leads to suggestions, where your answer could be be: "Not relevant for me" or "I already tried that".

 

[EmilioO]

All the cuts logs and warnings are related to vhosts domain file permissions issues ..
I've repaired file permissions a rerun plesk repair all -y -v

Full Log is attached.

thanks.

 

[EmilioO]

I've fixed !.

Problem was permission and ownership of /opt/psa/admin/sbin/mod_wrapper

Runing:

# chown root:psaadm /opt/psa/admin/sbin/mod_wrapper
# chmod 4110 /opt/psa/admin/sbin/mod_wrapper

Do the trick.

Find the solution here: https://github.com/plesk/letsencrypt-plesk/issues/22

Maybe plesk repair script must be upgraded checking this file.

Thanks