Adding CHROOTSH=/usr/local/psa/bin/chrootsh to /etc/cagefs/proxy.commands changes the error to:
unable to determine user name, will use first found by uid=10002
Im not sure if I should add a fixed user, because it would be a different user everytime the cronjob runs, right?
Announcement
Collapse
No announcement yet.
Scheduled Tasks not working with CageFS and Plesk
Collapse
X
-
I believe you have to implement it over proxyexec technology, more here: http://docs.cloudlinux.com/executing_by_proxy.html
I worry this single binary will not be enough, however let start from here.
Leave a comment:
-
Scheduled Tasks not working with CageFS and Plesk
When i set up a scheduled task in plesk, i get this error when the job is running:
execl: couldnt exec `/usr/local/psa/bin/chrootsh
execl: No such file or directory
The site is enabled in CageFS. If I disable CageFS for the site, it works.
Is it because the file /usr/local/psa/bin/chrootsh is missing in the skeleton?
I have created /etc/cagefs/conf.d/pleskcron.cfg
[pleskcron]
comment=Pleskcron
paths=/usr/local/psa/bin/chrootsh
And after that i ran /usr/sbin/cagefsctl --force-update
That did change something, because now the error is:
setreuid() to root failed
system error: Operation not permitted
What is the correct way to get Scheduled Tasks to work with Plesk with CageFS?Tags: None
Leave a comment: