Knowledge Base

Ask A Question

Questions

0

Nexpose - Scheduled Backup caused failure in Security Console

A routine backup maintenance initiated a restart, but did not complete the restart which produced a hung state. The last few log logs and then the error line: [INFO] [Thread: CPU Memory monitor] The CPU and memory monitor thread was interrupted : sleep interrupted. [INFO] [Thread: Security Console Restart] Shutting down. [INFO] [Thread: Security Console Restart] Shutting down scan manager. [INFO] [Thread: Security Console Restart] Shutting down local scan engine. [ERROR] [Thread: Security Console Restart] Engine update thread pool still running. After that are Java exceptions on a 10 minute interval: Caused by: java.lang.ClassNotFoundException: Illegal access: this web application instance has been stopped already. Could not load [com.rapid7.nex.domain.user.RequestUserProvider]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access. Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.rapid7.nex.system.user.IRequestUserProvider com.rapid7.nexpose.nsc.web.config.DatabaseConfig.m_requestUserProvider; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [com.rapid7.nex.domain.user.RequestUserProvider] for bean with name 'requestUserProvider' defined in URL [jar:file:/opt/rapid7/nexpose/shared/lib/managed/domain-13.0.1.jar!/com/rapid7/nex/domain/user/RequestUserProvider.class]; nested exception is java.lang.ClassNotFoundException: Illegal access: this web application instance has been stopped already. Could not load [com.rapid7.nex.domain.user.RequestUserProvider]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access. Any insight into how/why this occurred and how to prevent?

nexpose
insightvm

Posted by William Shoemaker 18 days ago