Restore

[peterv]

Hi @ all.
I´m logged in as Client an when I restore I get this error from the Server:

Failed deployment of domain test.xxxxxx.de

Execution of /usr/local/psa/admin/plib/api-cli/domain.php --update test.microplan.de -status enabled failed with return code 1.
Stderr is
An error occured during domain update: error in hosting updating: Unable to update hosting: permission denied

But in the Top of the message it wrote:
Details
Domain test.xxxxx.de has been restored

The Backup run succesful.

What is the Problem?
Anybody an idea?
Thats
Best regards.
Peter

 

[Amin Taheri]

If you use SELinux try turning it off with setenforce 0 and try again.

 

[peterv]

Thanks.
Where have i do that. At the VPS? Or at the SLES 9 where Virtuzzo is installed?
Best Regards.
Peter

 

[peterv]

At the VPS is:
setenforce: SELinux is disabled

And at the SLES 9:
usage: setenforce value

 

[[QT]bender@]

Have same issue, tried disable SELinux as you suggested without any luck.

Logged into Plesk as admin everything is OK, but logged in as a client receiving following error:

error log
client client1



Failed deployment of domain client1.domain.com



Execution of /usr/local/psa/admin/plib/api-cli/domain.php --update client1.domain.com -status enabled failed with return code 1.
Stderr is
An error occured during domain update: error in hosting updating: Unable to update hosting: permission denied

Do someone have any idea on how to fix/debug this?

 

[Amin Taheri]

One thing to look at is if this is a plesk error denied, or a system error denied.

Check the system logs in /var/log/dmesg (for selinux problems), /var/log/messages (for other system problems) or the plesk logs at /usr/local/psa/admin/logs/httpsd_error_log

Depending on where the error is listed should help determine at what level the error is occuring at.

Also some times just setting setenforce 0 doesnt actually "turn off" SeLinux.

If you find it is SeLinux, then in order to really disable it you actually have to go to /etc/selinux/config and edit the file, change the line SELINUX=enforcing to SELINUX=disabled then reboot.

Or you can take the line(s) from dmesg that are about the selinux problem and run them in audit2allow and go manually update the selinux policy.

Like for example say the line in dmesg was "audit: kernel : aaaa" (yours will not be like that, but you get the idea)

Then you could do this:
echo "audit: kernel : aaaa" >> ~/selinux-message
audit2allow -i ~/selinux-message

it will then output something like
allow user_rbject_r:file_t { getiocl }

Or something that otherwise doesnt make much sense.

Then you take that and go to /etc/selinux/targeted/src/policy/domains/program/ and edit the TE file for what ever application it is, be it plesk, apache, etc.

Just add the line to the bottom, and the rebuild the policy by using this command:

make -C /etc/selinux/targeted/src/policy reload

(note you need to have selinux enabled to reload, but you can leave at setenforce 0 for the entire thing)

I know this wasnt supposed to be a quick primer on selinux, but in case you need it, there it is