• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved System Health Monitor Service crashes on Windows

burakoner

New Pleskian
Server operating system version
Windows Server 2016
Plesk version and microupdate number
Plesk Obsidian 18.0.47
Hi,

I'm using Plesk Obsidian on Windows and System Health Monitor Service (C:\Program Files (x86)\Plesk\admin\bin\Parallels.MonitorSrv.exe)
crashes ALWAYS when it runs. There is error log in below but you 'll understand problem when I explain it.

I have two disks (C, D). My primary disk is C, and I use D for only backup purpose. I backup files to D Disk locally, then I upload them to Google Drive automatically. So Yes I have Google Drive application on machine. Google Drive applications creates a virtual disk (generally G:\). When system health monitor service try to read this disk it crashes. I tried many thing to solve it. I tried to change permissions, security settings on G disk, b ut I failed because it if a virtual disk and you cant change many thing on that drive.

There is crash log in below. As you can imagine, this logs are very old because It's impossible to start this service on my machine.
You just need to add a try-catch block for reading Disks (specially with G letter). I think it will solve this problem.

Logs from C:\Program Files (x86)\Plesk\admin\logs\HealthMonitoring20221025.log

2022-10-26 00:13:03,981 [5] INFO Parallels.Diagnostics.Counters.ProcessMonitor [(null)] - Initializing ...
2022-10-26 00:13:04,261 [5] INFO Parallels.Diagnostics.Counters.WmiEventWatcher [(null)] - Starting ...
2022-10-26 00:13:04,496 [5] INFO Parallels.Diagnostics.Counters.WmiEventWatcher [(null)] - Started
2022-10-26 00:13:04,496 [5] INFO Parallels.Diagnostics.Counters.WmiEventWatcher [(null)] - Starting ...
2022-10-26 00:13:04,716 [5] INFO Parallels.Diagnostics.Counters.WmiEventWatcher [(null)] - Started
2022-10-26 00:13:04,732 [5] INFO Parallels.Diagnostics.Counters.ProcessMonitor [(null)] - Initialized
2022-10-26 00:13:04,732 [5] INFO Parallels.Diagnostics.Counters.ProcessPerfDataCollector [(null)] - Initializing ...
2022-10-26 00:13:04,732 [5] INFO Parallels.Diagnostics.Counters.ProcessPerfDataCollector [(null)] - Initialized
2022-10-26 00:13:04,747 [5] INFO Parallels.Diagnostics.PerformanceMonitor [(null)] - Initialized.
2022-10-26 00:13:04,747 [5] INFO Parallels.Diagnostics.PerformanceMonitor [(null)] - Starting ...
2022-10-26 00:13:04,747 [5] INFO Parallels.Diagnostics.PerformanceMonitor [(null)] - Started
2022-10-26 00:13:14,534 [4] FATAL Parallels.Diagnostics.HealthMonitoringService [(null)] - System.UnauthorizedAccessException: Access to the path 'G:\' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__Error.WinIODriveError(String driveName, Int32 errorCode)
at System.IO.DriveInfo.get_TotalSize()
at Parallels.Diagnostics.Counters.DiskUsedSpaceCounter.get_Value()
at Parallels.Diagnostics.CounterSet.OnTimerCallBack(Object state)
at System.Threading.TimerQueueTimer.CallCallbackInContext(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireQueuedTimerCompletion(Object state)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Have a nice day
 
Back
Top