Just upgraded to Spiceworks 7 - Scanning is taking forever

wrx7m · 2013-09-10T16:56:20.000Z

I upgraded about 24 hours ago and the scanning seems to keep running. Also, the web UI is much slower (probably as a result of the scanning).

I also have some weird glitches where some devices show up as not being able to be scanned due to lack of correct credentials and when I try to select certain devices it keeps trying to apply them to all the devices listed and still won’t work despite having correct credentials. It is quite inconsistent.

Will this settle down or should I stop the scan and restart the services or reboot the server?

Ben-B-Spiceworks · 2013-09-11T02:30:45.000Z

You might see Spiceworks running scans more often, now, with 7.0. The new scan system runs different types of scans, and some scans run fairly often. You can adjust the scan schedules in Settings > Network Scan to reduce the scan frequency, or change which types of devices are scanned/how often they are scanned.

Also, note the “Show Additional Settings” area at the bottom of the page has a hidden scan option that allows you to control how often “discovery” scans run. Discovery scans run hourly by default, and will pick up any new devices and fully scan them.

Are the scan credentials problems you describe something you’re seeing in the new “Scan” page?

If you test the same credentials using WMIC, do they work?

http://community.spiceworks.com/help/Resolving_Unknown_Devices#Windows

wrx7m · 2013-09-11T15:14:27.000Z

Thanks for the information on the changes in the scanning levels and frequency. The interface is still very slow while a scan is in progress. Sometimes it takes 30 seconds for the next page to load.

I was able to get some of the issues ironed out with regards to the credentials, although I kind of stumbled through it. I think there are some issues with the way it is handling multiple devices, as described in the OP.

I am still having issues with my Barracuda SVF 300. It doesn’t want to scan as HTTP or SNMPv2C, despite known good credentials.

wrx7m · 2013-09-11T17:37:31.000Z

OK so now my scan won’t let me exclude a range of IP addresses.

I have a range of 192.168.0-3.1-254 and want to exclude 192.168.3.201-230 but it just disappears when I try to exclude it. I can add a single IP address but not a range. How do I exclude a range?

Ben-B-Spiceworks · 2013-09-11T18:19:49.000Z

Could you send me log package after running a “Rescan” on that Barracuda, from Inventory > group > find device > Tools > Rescan? Here’s how to send the logs: http://community.spiceworks.com/help/Contact_Support#Log

Right now you can’t exclude IP ranges, just single IPs. You’d have to build ranges around it. This should work:

192.168.0-2.1-254
192.168.3.1-200,231-254

wrx7m · 2013-09-11T18:21:34.000Z

Thanks, Ben.

Interesting way to do it. Let me get that barracuda log for you.

Ben-B-Spiceworks · 2013-09-11T19:20:26.000Z

You bet! Thanks for creating/sending the logs.

davidgray9550 · 2013-09-11T22:48:10.000Z

Ben,

Is there a way to disable Discovery Scans? I’d rather only search for new devices during my scheduled daily scan. Also, it might be nice if in a future update you could have the scanning progress page show exactly what particular scan is currently in progress.

Ben-B-Spiceworks · 2013-09-11T22:52:01.000Z

There isn’t a way to disable discovery, but you could configure it to run infrequently (every 12 hr.).

martinpheiffer · 2014-01-23T11:02:10.000Z

I’m having the same issue on SW 7.1, my scanning takes forever, even after making the scanning intervals midnight and early morning. scanning one pc with login error takes about 2 hours

Ben-B-Spiceworks · 2014-01-24T23:37:21.000Z

Hi GrapGat, send us your logs - we can look at why the scans aren’t working properly:

http://community.spiceworks.com/help/Contact_Support#Log