• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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: 4
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