• 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.

Resolved Run cron with user 'psacln' && can't modify when created

dariusju

Basic Pleskian
Server operating system version
Ubuntu 23
Plesk version and microupdate number
Latest
I don't see to chose this kind of user when creating cron job.

psacln

Also, after creation I can't edit user.
 

Attachments

  • Screenshot_2023-10-03-22-32-04-938_com.vivaldi.browser-edit.jpg
    Screenshot_2023-10-03-22-32-04-938_com.vivaldi.browser-edit.jpg
    331.6 KB · Views: 6
psacln is the default group name, not the user name. The file owner (user) is the one you've scratched out in your screenshot. All cronjobs are run as the domains system user. For security reasons each webspace runs with it own user, to prevent other (system) users from accessing their webspace.

Why would want to change the file owner/user?
 
psacln is the default group name, not the user name. The file owner (user) is the one you've scratched out in your screenshot. All cronjobs are run as the domains system user. For security reasons each webspace runs with it own user, to prevent other (system) users from accessing their webspace.

Why would want to change the file owner/user?
What you suggest to chose? I choosed root so it created file with root ownership.

It so because cron running makes log file it was not before, so ownership is broken when website try to access that log file.
 
What you suggest to chose? I choosed root so it created file with root ownership.

It so because cron running makes log file it was not before, so ownership is broken when website try to access that log file.
I found that I need create schedule tasks from websites n domains, not from tools n settings.
 
Back
Top