• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Unable to rotate task-manager logs

Hostinet SLU

New Pleskian
Hi,

Since a few days ago, we are getting the following error message:

Aug 25 01:17:17 0.1 sshost.exe The process cannot access the file because it is being used by another process. (Error code 32) at Rename file 'C:\Program Files (x86)\Plesk\admin\logs\task-manager.log' to 'C:\Program Files (x86)\Plesk\admin\logs\task-manager20210824.log'. Processes: PID(14140) 'C:\Program Files (x86)\Plesk\PleskTaskManager\task-manager.exe' at (renameFile line 758) at Failed to rotate non standard log(`anonymous-namespace'::rotateNonStandardsLog line 111) Execute file name: C:\Program Files (x86)\Plesk\admin\bin\sshost.exe

We have tried to fix the problem, stopping the task manager service, moving the log to another path and restarting the service, but we keep getting the same error daily, when the system rotates the logs.

We have also made use "Check components and folder permissions" tool, but it has not solved the problem either.

The latest Obsidian version, 18.0.37, is being used and the messages started to appear after the latest Windows updates were applied to the server:

KB5005030 (OS Build 17763.2114)
KB5004870 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows 10, version 1809 and Windows Server, version 2019

Thanks in advance,
 
It looks like this issue has been resolved in 18.0.38. We do not see any reference in the changelog, so we cannot confirm it 100%.

Please, mark this issue as Resolved because we cannot edit the thread.

Regards,
 
Back
Top