• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Rotation of files with multiple hard links is not allowed

Maz

New Pleskian
Server operating system version
CloudLinux 8.5 (Vladimir Shatalov) (Based Alma Linux 8.5)
Plesk version and microupdate number
Obsidian v18.0.43_build1800220414.18 os_RedHat el8
Hi, I have a problem with log rotation, related to the bug PPP-56387 (I think). The logs are not rotated, if I try with:
/usr/local/psa/logrotate/sbin/logrotate -v -f /usr/local/psa/etc/logrotate.d/mydomain.com I get: log xxx has multiple (2) hard links. Rotating files with multiple hard links is not allowed. I tried the solution listed here and here but none worked.
I applied the workaround shown here and it only works the first time, the next day the log is no longer rotated.
Plesk already updated to 18.0.43 # 1.

Plesk: Obsidian v18.0.43_build1800220414.18 os_RedHat el8
OS: CloudLinux 8.5 (Vladimir Shatalov) (Based Alma Linux 8.5) .

Thanks to all.
 
I can suggest you contact Plesk Support Team if no one solution didn't work for you.
Experienced supporters will check and fix the issue directly on your server.
 
Back
Top