• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

No permissons after restore?

F

FranzP

Guest
hi, i restored my hole system after a rootkit attack and now my plesk is total crashed. it can't access any files and im getting one excption after another on the website.

the plesk webserver runs as psaadm, the files are all chown'ed as root (as it was before and should be). the first failure appears right after the start:

Code:
/etc/init.d/psa restart
Processing config directory: /usr/local/psa/admin/conf/httpsd.*.include
Syntax OK
/usr/local/psa/admin/bin/httpsdctl restart: httpd restarted
packagemng: Unable to create 'dirty' flag (/usr/local/psa/tmp/components_dirty_flag): Permission denied
System error 13: Permission denied
packagemng: Unable to create 'dirty' flag (/usr/local/psa/tmp/components_dirty_flag): Permission denied
System error 13: Permission denied
if i chown the files to psaadm the failure go's away - but i can't chown all files to psaadm (/etc/passwd for example) so what should i do? how did plesk manage to read root files with the psaadm? im thinking of suexec but i didn't see any error there.

any ideas how to fix this?
 
Back
Top