Plesk server log maintenance
The multiple-hard-links error is a server-level log rotation problem, not a website content error
Shared-hosting customers should report it rather than changing files. Log rotation refuses to rename or remove a file with unexpected hard links because doing so could affect another path to the same data. Include the domain, time and complete message in a support ticket so the server team can inspect ownership and links safely.
What does the error mean?
A hard link gives more than one directory entry access to the same underlying file data. Log-rotation tools normally expect a log file to have one path. When they find several hard links, they stop rather than rotate a file whose other references may still be in use.
What can be affected?
The current access or error log may continue growing because the scheduled rotation did not complete.
Is the website down?
Usually not. Website traffic may continue normally, although growing logs can eventually consume storage if the cause is ignored.
Is it malware?
The message alone does not prove malicious activity. It describes the file-link state and still requires investigation.
Can I delete the log?
Do not do so on shared hosting. Deletion can remove useful evidence, interrupt logging or affect the other linked path.
What should a hosting customer do?
- 1Copy the full message
Include the complete file path if it is shown, but remove passwords or private customer data.
- 2Record the domain and time
State which website or subscription was involved and when the warning appeared.
- 3Check available storage
Note whether the hosting account reports unusually high log or disk use. Do not purge files to make the warning disappear.
- 4Open a ticket
Send the evidence to UKC. Server-impacting reports are triaged promptly because other services may also be affected.
What should a Plesk administrator verify?
| Check | Purpose |
|---|---|
| Exact inode and link count | Identify every path pointing to the same log data before making a change |
| Ownership and permissions | Confirm the file belongs to the intended subscription and logging process |
| Plesk and system rotation rules | Find duplicate or conflicting jobs and confirm the expected log path |
| Disk use and recent changes | Assess urgency and whether migration, restore or manual linking created the condition |
| Post-fix rotation | Run the supported rotation or repair process and confirm a fresh log is written |
Log rotation questions
Will changing WordPress fix this?
No. The error is raised by server log handling, not by WordPress content, plugins or themes.
Can a customer run the repair?
Not on UKC shared hosting. The server team has the access and context needed to inspect all affected paths.
What happens after correction?
The administrator should verify that rotation completes, the active service writes to the new log and disk use returns to a normal pattern.
Preserve the evidence
Send the complete warning to UKC support
Include the domain, timestamp and file path, and leave the server logs unchanged until they have been reviewed.