Discussion Forums/PDQ Inventory/Inventory - Questions

Answered

Scan Status

Kris Da San Martino
asked this on November 01, 2011 08:46

What does it mean when your scan status show pending?    Reports show that it's been this way for 17 hrs.
 

Comments

User photo
Shane Corellian
Admin Arsenal

Pending, during a scan, means that the target is in the queue to receive a scan. The queue is determined by a few factors.

  1. PDQ Inventory service. Is this service running?If the service isn't running then you should see a hyperlink in the bottom status field of the PDQ Inventory console showing "Service is not running". If the PDQ Inventory service isn't running, any submitted scan will have the status of Pending until the service is started and the scan requests can be processed.
  2. The Concurrent Scans value under the Performance panel in Preferences. The default value is 32. If you submit a scan to 32 computers then they should, in theory, only be in the Pending state for a few seconds.

A target will leave the Pending state and go to "Connecting" when the actual scan is initiated on the target. 

17 hrs is way too long. Here are a few questions:

  1. Is the PDQ InventoryService running?
  2. What is the value of the Concurrent Scans in Preferences (under Performance panel)?
  3. How many targets were set to receive this particular scan?
  4. How many of those targets actually were scanned and how many were stuck in Pending?
  5. In PDQ Inventory, open up one of the target computers that is stuck in Pending. Go the Scans panel. How many scans are in there? Were any of them successful? What is the status of the scan that preceded the "stuck" scan?
  6. Abort the stuck scan and try again on one of the target computers that was stuck earlier. What is the status?
November 01, 2011 09:53
User photo
Kris Da San Martino

thanks for you speedy response.

1.  the PDQ inventory service is running

2. Concurrent scans are at 32

3. the count at the bottom of PDQ Inventory screen says 8163.

4. as I watch the inventory screen the number 8136 listed at the bottom is getting smaller so I guess it's working through the request.

5.  there are three 10/20, 10/26 and 10/31

6. I started another scan on two computers. Both showed pending but scans finished after 3 min accourding to log.

 

I noticed that my cpu usage is at or near 100% just about all of the time. Even when no scannings are going on.   I'm running PDInventory & Deployment on a server that has no other function.

2 Ghx processor 4 gb memory  743 mb free on the C drive where app is loaded.  if I stop the pdq inventory service and close the console the cpu drops way down.  Is this high cpu activity normal? Have I configured the app wrong? 

 

thanks for your help

November 01, 2011 10:49
User photo
Shane Corellian
Admin Arsenal

Oh, I see. You were scanning about 8100 systems... I'll have to do the math. In chunks of 32 systems that would definitely take a while.

As far as the high cpu utilization, this is probably due to 2 factors:

  1. You are scanning 32 systems at a time and the database is inserting, deleting and updating a lot of records, pretty much non-stop. When your initial scan is finished the CPU should relax a little.
  2. With that many computers you are going to want to have your Heartbeat set to a value higher than 300 seconds (the default). Basically, with the default you are trying to ping 8100+ computers. This means that the system is constantly pinging. I would raise that value to 3600 seconds or so. Maybe even higher. You can change this value in Preferences under the Heartbeat panel
November 01, 2011 12:51
User photo
Kris Da San Martino

Ok, so may be I was asking a bit much of the server. :-)    I have set it to 7200 and will see how it looks in a day or two.

 

thanks.

November 01, 2011 14:53
User photo
Adam Ruth
Admin Arsenal

Kris,

As mentined in another thread, the current version of the software has had most of the performance tuning geared to around 500 computers. It certainly works with larger numbers, but there are some bottlenecks that we still need to smooth out once you get up in the thousands.

Do you notice the high CPU utilization in the PDQInventoryService.exe or PDQInventoryConsole.exe process?  Most likely it's in Console as it's constantly grabbing the new scan data and working with it.  We are currently working on a number of optimizations to make this work much better for larget number of computers. We're also going to be pushing many operations into the Service from the Console so that it can be set with a different priority in order to not affect other running processing.

November 01, 2011 15:47
Add a comment