THE SECURITY CONSOLE IS INITIALIZING, PLEASE WAIT

Hello folks,

I am trying to start the NSC the first time, but the initialization is stuck at 24%, please help me out. I am using the " Virtual Appliance".

THE SECURITY CONSOLE IS INITIALIZING, PLEASE WAIT…
Security Console Startup Progress
5/29/2022, 7:52:32 PM : 24% : Initializing update processor…

tail -f /opt/rapid7/nexpose/nsc/logs/nsc.log is as follows:

2022-05-29T14:22:28 [INFO] [Thread: http-nio-3780-exec-5=/data/startupMessage] Scheduler meta-data: Quartz Scheduler (v2.2.1) ‘sysScheduler’ with instanceId ‘NON_CLUSTERED’
Scheduler class: ‘org.quartz.core.QuartzScheduler’ - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool ‘org.quartz.simpl.SimpleThreadPool’ - with 1 threads.
Using job-store ‘org.springframework.scheduling.quartz.LocalDataSourceJobStore’ - which supports persistence. and is not clustered.

2022-05-29T14:22:28 [INFO] [Thread: http-nio-3780-exec-5=/data/startupMessage] Quartz scheduler ‘sysScheduler’ initialized from an externally provided properties instance.
2022-05-29T14:22:28 [INFO] [Thread: http-nio-3780-exec-5=/data/startupMessage] Quartz scheduler version: 2.2.1
2022-05-29T14:22:28 [INFO] [Thread: http-nio-3780-exec-5=/data/startupMessage] JobFactory set to: org.springframework.scheduling.quartz.AdaptableJobFactory@464ecea3
2022-05-29T14:22:28 [INFO] [Thread: http-nio-3780-exec-5=/data/startupMessage] ProductNotificationService registered for events

Hello vfotro,

The Virtual Appliance is for Proof of Concept purposes and is NOT built for enterprise or production deployments.

Please spin up a new machine, matching the system requirements outlined here:

And then install the console onto that machine.

Also, do not forget to Deactivate this console, wait 24hrs for your platform information to clear, then spin up the new console machine.

Administration > Console Administer > Insight Platform > Deactivate Console

what apears to be stuck is actually doing updates - watch the /opt/rapid7/nexpose/nsc/logs/update.log file. you will see slow rate of updates.

it is because the update process is unable to fully use available resources (bandwidth, cpu, memory, disk).

see it in action being lazy on a 18 cpu NVME 12GB ram 1gigabit internet vm (toggle HD, enter full screen)