Community FAQ
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
chogan201
Engaged Sweeper III

Since upgrading to 12.3.2.3 this week, scanning has been an issue. 

I currently have over 500 devices in the queue and it is increasing.  I have on prem devices that haven't been scanned since the update.  LSAgent devices are reporting in normally.

I tried clearing the queue, restarting the service, and restarted the server.

Anyone else having this problem?

1 ACCEPTED SOLUTION
Mister_Nobody
Honored Sweeper II

LS 12.3 has hidden firewall rules scanner. 

Disable it via scan interval settings. 

View solution in original post

9 REPLIES 9
chogan201
Engaged Sweeper III

Support has registered the firewall rule scanning issue as a bug to fixed in a future release.  It is tracked as (LAN-17222).

Thank you Mr_Nobody!

chogan201
Engaged Sweeper III

With firewall rule scanning really disabled, scheduled scans are running normally.

A manual scan (Rescan Asset from the asset page) still takes about 20 minutes, whereas prior to updating it was only a few minutes.  

chogan201
Engaged Sweeper III

Ok, so back to the Firewall rules scanning.  

Checking again I found I didn't actually disable it when I thought I did before (not sure what happened).

Looking at the scan times on a PC, firewall rules is taking 37,538.42 seconds.  That's over 10 hours!  That would explain why the queue is backed up.

Now that firewall rule scanning is really disabled, I will see if we are back to normal.

 

ScanTime.JPG

chogan201
Engaged Sweeper III

I'm going to open a support case.

Mister_Nobody
Honored Sweeper II

LS 12.3 has hidden firewall rules scanner. 

Disable it via scan interval settings. 

I disabled the firewall rules scanning.  I'll let the run today and see if it has any impact.  

chogan201
Engaged Sweeper III

I don't think that was it.  The queue shows it has been scanning the same 12 computers for the last 55 minutes.  

Total scans counter has gone up 28 in that time.  

chogan201
Engaged Sweeper III

An update as I look into this more.  Scanning is working, however much slower than before the update causing the queue to back up.  

CPU and Memory on the server are within normal range and the web interface is responding normally.  

I scaled back the scan intervals and will see if the queue eventually clears.  

Try this report:

Select Top 1000000 tblassets.AssetID,
  tblassets.AssetName,
  tblassets.IPAddress,
  tblassets.Userdomain,
  tblassets.Username,
  tblassets.oscode,
  tblassets.memory,
  tblassets.Processor,
  TsysWaittime.CFGname,
  TsysLastscan.Scantime,
  TsysLastscan.Lasttime,
  TsysWaittime.Waitdays
From tblassets
  Inner Join TsysLastscan On tblassets.AssetID = TsysLastscan.AssetID And
      TsysLastscan.Scantime > 5 And TsysLastscan.Lasttime > GetDate() - 7
  Inner Join TsysWaittime On TsysLastscan.CFGcode = TsysWaittime.CFGCode
Order By TsysLastscan.Scantime Desc

General Discussions

Find answers to technical questions about Lansweeper.

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now