Skip to content


  1. Lee
    July 9, 2018 @ 1:14 pm

    Any reason why the lights out service is constantly using CPU i.e. more than 20%? Every time I look in task manager it’s hogging the processor.


    • Martin Rothschink
      July 9, 2018 @ 1:35 pm

      Hi Lee,
      do you see a constant 20% load? The actual load depends on the cpu speed, number of cores and the number of monitored items. A peak every 10s is expected, but not all the time.
      To analyze that further, please open a ticket to share log files and additional information.



  2. Lee
    July 9, 2018 @ 2:11 pm

    Constantly above 20% despite a re-install. CPU is a XEON E3-1225 so pretty capable.


    • Martin Rothschink
      July 9, 2018 @ 2:14 pm

      Then please open a ticket here and attach your server logs. Simply zip the whole folder c:\programdata\LightsOut2\Logs (via right click, send to compressed folder) and attach the archive to the ticket. If you do not see a folder c:\programdata, then open explorer options and enable “show hidden files and folders”. Please attach a screen shot of taskmanager also.


  3. Lee
    July 9, 2018 @ 2:26 pm

    Doing it now, quick look shows this constantly:

    2018-07-09 13:04:49:048 [1136] ERROR EssentialsBackupMonitor: Timer and monitoring stopped, too many errors
    2018-07-09 13:04:53:560 [ 3] WARN Evaluation of Backup/Client computer backup needed more than 2.7954341 seconds!
    2018-07-09 13:06:28:756 [1253] ERROR EssentialsBackupMonitor: Exception in TimerCallback GetIoLoad System.ComponentModel.Win32Exception (0x80004005): The requested resource is in use
    at System.Diagnostics.PerformanceMonitor.GetData(String item)
    at System.Diagnostics.PerformanceCounterLib.GetPerformanceData(String item)
    at System.Diagnostics.PerformanceCounterLib.GetCategorySample(String category)
    at System.Diagnostics.PerformanceCounterLib.GetCategorySample(String machine, String category)
    at System.Diagnostics.PerformanceCounter.NextSample()
    at System.Diagnostics.PerformanceCounter.NextValue()
    at AxoNet.LightsOut2.Activity.Essentials.EssentialsBackupMonitor.GetIoLoad()


  4. Lee
    July 9, 2018 @ 3:45 pm

    That solved that error, cpu usage still high. I’ve submitted a ticket.



    • Martin Rothschink
      July 19, 2018 @ 3:28 pm

      Problem has been fixed. Lee told me “Found an error in the events logs to do with usbperf performance counter. I repaired this from the Winsxs folder and lights out CPU usage dropped dramatically (less than 1%).”


Leave a Reply

Your email address will not be published. Required fields are marked *