Quantcast
Channel: Intel Communities : Discussion List - Intel® vPro™ Platform
Viewing all articles
Browse latest Browse all 632

LMS service high CPU, stuck in stopping state

$
0
0

Hello,

 

Yesterday an auto-update occurred and I saw a flash of a CMD window show it was updating Intel ME.  Since then the LMS service will work start running continually at around 35%. In searching the forums I found mention of the gms.log file and opened it.  It show that the LMS service seems to be working fine and at the time it starts using high CPU and the service shows a status of stopping.

 

Below is a sample from the log that shows the sequence of events that occur.  Once it breaks I have to force an End Task or restart.  Any ideas as to how to fix this?

 

(2476)[2017-11-07 14:52:16.367395] [LM_DEBUG]  LMS:_acceptConnection(AF_INET)

(2476)[2017-11-07 14:52:16.367395] [LM_DEBUG]  LMS:Sending channel open request to LME. Address: 127.0.0.1, requested port: 16992.

(2476)[2017-11-07 14:52:16.368398] [LM_DEBUG]  LMS:Send channel open request to LME. Sender 2324. addr:127.0.0.1 port:59749

(2476)[2017-11-07 14:52:16.385451] [LM_DEBUG]  LMS:Received 499 bytes from socket 2324. Sending to LME

(2476)[2017-11-07 14:52:16.385451] [LM_DEBUG]  LMS:Sending 499 bytes to recipient channel 1.

(2476)[2017-11-07 14:52:16.389965] [LM_DEBUG]  LMS:Received 499 bytes from socket 2324. Sending to LME

(2476)[2017-11-07 14:52:16.389965] [LM_DEBUG]  LMS:Sending 499 bytes to recipient channel 1.

(2476)[2017-11-07 14:52:16.393978] [LM_DEBUG]  LMS:Received 499 bytes from socket 2324. Sending to LME

(2476)[2017-11-07 14:52:16.394481] [LM_DEBUG]  LMS:Sending 499 bytes to recipient channel 1.

(2476)[2017-11-07 14:52:16.396486] [LM_DEBUG]  LMS:Received 401 bytes from socket 2324. Sending to LME

(2476)[2017-11-07 14:52:16.396987] [LM_DEBUG]  LMS:Sending 401 bytes to recipient channel 1.

(2476)[2017-11-07 14:52:16.446317] [LM_DEBUG]  LMS:Received 0 bytes from socket 2324.

(2476)[2017-11-07 14:52:16.446317] [LM_DEBUG]  LMS:Sending channel close to LME. Recipient: 1.

(11356)[2017-11-07 15:48:49.264961] [LM_DEBUG]  HostChangesNotificationService service handle timeout

(11356)[2017-11-07 15:48:49.264961] [LM_DEBUG]  GMSC: --> handle_output

(11356)[2017-11-07 15:48:49.264961] [LM_DEBUG]  HostChangesNotificationService

(11356)[2017-11-07 15:48:49.264961] [LM_DEBUG]  HostChangesNotificationService::HandleAceMessage

(11356)[2017-11-07 15:48:49.264961] [LM_DEBUG]  GMSC: <-- handle_output

(11356)[2017-11-07 16:48:49.134016] [LM_DEBUG]  HostChangesNotificationService service handle timeout

(11356)[2017-11-07 16:48:49.134016] [LM_DEBUG]  GMSC: --> handle_output

(11356)[2017-11-07 16:48:49.134016] [LM_DEBUG]  HostChangesNotificationService

(11356)[2017-11-07 16:48:49.134016] [LM_DEBUG]  HostChangesNotificationService::HandleAceMessage

(11356)[2017-11-07 16:48:49.134016] [LM_DEBUG]  GMSC: <-- handle_output

(11356)[2017-11-07 17:48:49.133035] [LM_DEBUG]  HostChangesNotificationService service handle timeout

(11356)[2017-11-07 17:48:49.133035] [LM_DEBUG]  GMSC: --> handle_output

(11356)[2017-11-07 17:48:49.133035] [LM_DEBUG]  HostChangesNotificationService

(11356)[2017-11-07 17:48:49.133035] [LM_DEBUG]  HostChangesNotificationService::HandleAceMessage

(11356)[2017-11-07 17:48:49.133035] [LM_DEBUG]  GMSC: <-- handle_output


Viewing all articles
Browse latest Browse all 632

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>