• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

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