Network scan doesn't seem to start

With a fresh installation. How do we get network scan to start? I’ve added folders, entered in a simple network subnet of a /24 (since I’ve read already of time outs with larger subnets). Using SNMP for my hosts (as we are primarily a networking/ISP shop and have lots of switches and such). I have never seen this process or any other sign of it starting. Why? How do I fix, or check this?

We have hundreds of devices, in different subnets, that we NEED to be able to automatically scan and enter in to monitoring systems. This process seems quite cumbersome, and it doesn’t have to be…

Using latest RAW beta version. AFTER already trying the stable to no avail…

The scan is triggered by the crontab entry for your site.

# /omd/sites/test/etc/cron.d/cmk_multisite
# Run Multisite regular jobs, e.g. scheduled reports
* * * * * . $OMD_ROOT/etc/omd/site.conf ; curl http://localhost:$CONFIG_APACHE_TCP_PORT/test/check_mk/run_cron.py >/dev/null 2>&1

I checked on one of my test systems with a actual CMK. It is working without problem.

Is your system a distributed setup or a single standalone installation? Or better said if CMK sees your site as a slave then no scan will happen.

It was a single stand alone physical server and site…

I checked with RAW and EE booth with 1.6 and 2.0 beta. All versions where working.
Can you provide the screenshot of the scan settings of the folder?
If you increase the log level inside your site, you will see if the jobs are starting inside your site.

Example output from the “web.log”

2021-02-17 22:37:01,236 [10] [cmk.web 3040] Starting [execute_network_scan_job]
2021-02-17 22:37:01,237 [10] [cmk.store 3040] Try aquire lock on /omd/sites/testraw/etc/check_mk/multisite.mk
2021-02-17 22:37:01,238 [10] [cmk.store 3040] Got lock on /omd/sites/testraw/etc/check_mk/multisite.mk
2021-02-17 22:37:01,238 [10] [cmk.store 3040] Try aquire lock on /omd/sites/testraw/etc/check_mk/conf.d/wato/ip-scan/.wato
2021-02-17 22:37:01,238 [10] [cmk.store 3040] Got lock on /omd/sites/testraw/etc/check_mk/conf.d/wato/ip-scan/.wato
2021-02-17 22:37:01,238 [10] [cmk.store 3040] Releasing lock on /omd/sites/testraw/etc/check_mk/conf.d/wato/ip-scan/.wato
2021-02-17 22:37:01,238 [10] [cmk.store 3040] Released lock on /omd/sites/testraw/etc/check_mk/conf.d/wato/ip-scan/.wato
2021-02-17 22:37:01,239 [10] [cmk.store 3040] Releasing lock on /omd/sites/testraw/etc/check_mk/multisite.mk
2021-02-17 22:37:01,239 [10] [cmk.store 3040] Released lock on /omd/sites/testraw/etc/check_mk/multisite.mk
....
2021-02-17 22:37:16,453 [10] [cmk.store 3040] Try aquire lock on /omd/sites/testraw/etc/check_mk/multisite.mk
2021-02-17 22:37:16,453 [10] [cmk.store 3040] Got lock on /omd/sites/testraw/etc/check_mk/multisite.mk
2021-02-17 22:37:16,454 [10] [cmk.store 3040] Try aquire lock on /omd/sites/testraw/var/check_mk/wato/log/wato_audit.log
2021-02-17 22:37:16,454 [10] [cmk.store 3040] Got lock on /omd/sites/testraw/var/check_mk/wato/log/wato_audit.log
2021-02-17 22:37:16,464 [10] [cmk.store 3040] Releasing lock on /omd/sites/testraw/var/check_mk/wato/log/wato_audit.log
2021-02-17 22:37:16,464 [10] [cmk.store 3040] Released lock on /omd/sites/testraw/var/check_mk/wato/log/wato_audit.log
2021-02-17 22:37:16,464 [10] [cmk.store 3040] Try aquire lock on /omd/sites/testraw/var/check_mk/background_jobs/search_index/jobstatus.mk
2021-02-17 22:37:16,464 [10] [cmk.store 3040] Got lock on /omd/sites/testraw/var/check_mk/background_jobs/search_index/jobstatus.mk

This was the complete scan of a /24 network
Output inside WATO matches exactly this times from the log.
image

After you created the scan rule you can also monitor the number of Apache threads and you will see that there are many more for a short time of the scan.

I did a fresh install today, and so far scan is working with RAW and the latest beta. Maybe I had a setting goofed up initially on the first installation. Although, I’m pretty sure I did the same things last time… Oh well I suppose. Thanks.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.