RME 3.2 Inventory Collection Failure with error

Unanswered Question
Nov 3rd, 2009
User Badges:

Hi,

Inventory collection fails with error is "Timed out. Make sure that ICServer is running”. But the ICServer process is running. I enabled debug on could see the following in the IC_Server.log which I'm not sure if it indicates any issues.


I can find the devices in DCR and the devices are classified as Normal in RME.


Series of following message for all the devices


DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.Request,115,Removing device 181from request 1255347128972

DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,163,Removing, 175

DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,171,got device, 175

DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.Device,51,Removing request 1255347128972 for device 175

DEBUG,[Thread-26],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,177,Removed2 dev, 175from Priority of the ENUM is : 0


then,


DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,89,Adding Device :175

DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.Device,46,Adding request 1255347128973 for device 175

DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.PriorityQueue,142,Found dup device in queue: 175

DEBUG,[Thread-25],com.cisco.nm.rmeng.inventory.ics.core.Request,75,Adding device 175 to request 1255347128973


and then the below messages


DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called.

DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called.

DEBUG,[Timer-0],com.cisco.nm.rmeng.inventory.ics.threadpool.ThreadPool,69, Timer Tasks Run method is called


I highly appreciate any help on this. Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Tue, 11/03/2009 - 09:44
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The ICServer process could have locked up which means a full thread dump will be required to see why this is happening. Open a TAC service request, and they can walk you through getting this.

Actions

This Discussion