Knowledge Base

Ask A Question



SCCM Silent Install

Has anyone had success deploying the Insight Agent via SCCM. I am experiencing issues while trying to install from the script that was provided on the site. When using a simple script locally on workstations, the install seems to fail. When looking at the log, there is nothing that stands out to me. The scripts used are below: msiexec.exe /i agentinstaller-x86_x64.msi /qn msiexec.exe /i agentinstaller-x86_x64.msi /quiet msiexec.exe /i agentinstaller-x86_x64.msi /L*V "C:\temp\rapid7.log" /qn /norestart The output from the log file is below: === Verbose logging started: 4/30/2018 10:11:27 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\WINDOWS\system32\msiexec.exe === MSI (c) (FC:FC) [10:11:27:137]: Resetting cached policy values MSI (c) (FC:FC) [10:11:27:137]: Machine policy value 'Debug' is 0 MSI (c) (FC:FC) [10:11:27:137]: ******* RunEngine: ******* Product: agentinstaller-x86_x64.msi ******* Action: ******* CommandLine: ********** MSI (c) (FC:FC) [10:11:27:138]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (FC:FC) [10:11:27:138]: Grabbed execution mutex. MSI (c) (FC:FC) [10:11:27:169]: Cloaking enabled. MSI (c) (FC:FC) [10:11:27:169]: Attempting to enable all disabled privileges before calling Install on Server MSI (c) (FC:FC) [10:11:27:170]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (28:84) [10:11:27:179]: Running installation inside multi-package transaction C:\Users\jmmiller\Desktop\Rapid7\agentinstaller-x86_x64.msi MSI (s) (28:84) [10:11:27:179]: Grabbed execution mutex. MSI (s) (28:B0) [10:11:27:182]: Resetting cached policy values MSI (s) (28:B0) [10:11:27:182]: Machine policy value 'Debug' is 0 MSI (s) (28:B0) [10:11:27:182]: ******* RunEngine: ******* Product: C:\Users\jmmiller\Desktop\Rapid7\agentinstaller-x86_x64.msi ******* Action: ******* CommandLine: ********** MSI (s) (28:B0) [10:11:27:183]: Note: 1: 2203 2: C:\Users\jmmiller\Desktop\Rapid7\agentinstaller-x86_x64.msi 3: -2147287038 MSI (s) (28:B0) [10:11:27:184]: MainEngineThread is returning 2 MSI (s) (28:84) [10:11:27:188]: User policy value 'DisableRollback' is 0 MSI (s) (28:84) [10:11:27:188]: Machine policy value 'DisableRollback' is 0 MSI (s) (28:84) [10:11:27:188]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (28:84) [10:11:27:188]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (28:84) [10:11:27:189]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (28:84) [10:11:27:189]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (FC:FC) [10:11:27:190]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (FC:FC) [10:11:27:191]: MainEngineThread is returning 2 === Verbose logging stopped: 4/30/2018 10:11:27 ===

Posted by Jeff Miller 9 months ago


Nexpose failing to start on ubuntu

hey guys, I am having a major issue getting nexpose to run. I keep getting the error of: Critical error during initialization: Could not get JDBC Connection; nested exception is org.postgresql.util.PSQLException: FATAL: the database system is in recovery mode When I manually start with ./ I get this. 2018-04-26T12:50:39 [INFO] Initializing console... 2018-04-26T12:50:39 [INFO] Product Version: 6.5.16 2018-04-26T12:50:39 [INFO] Current directory: /opt/rapid7/nexpose/nsc 2018-04-26T12:50:39 [INFO] User name: root 2018-04-26T12:50:39 [INFO] Super user: Yes 2018-04-26T12:50:39 [INFO] Computer name: kevin-Aspire-A517-51G 2018-04-26T12:50:39 [INFO] Host Address: 2018-04-26T12:50:39 [INFO] Host FQDN: kevin-Aspire-A517-51G 2018-04-26T12:50:39 [INFO] Operating system: Ubuntu Linux 17.10 2018-04-26T12:50:39 [INFO] CPU speed: 3175MHz 2018-04-26T12:50:39 [INFO] Number of CPUs: 8 2018-04-26T12:50:39 [INFO] Total memory: 11.6 GB 2018-04-26T12:50:39 [INFO] Available memory: 508.8 MB 2018-04-26T12:50:39 [INFO] Total disk space: 456.4 GB 2018-04-26T12:50:39 [INFO] Available disk space: 169.1 GB 2018-04-26T12:50:39 [INFO] Disk space used by installation: 1.5 GB 2018-04-26T12:50:39 [INFO] Disk space used by scans: 0 bytes 2018-04-26T12:50:39 [INFO] Disk space used by database: 68.4 MB 2018-04-26T12:50:39 [INFO] Disk space used by reports: 0 bytes 2018-04-26T12:50:39 [INFO] Disk space used by backups: 0 bytes 2018-04-26T12:50:39 [INFO] JVM name: OpenJDK 64-Bit Server VM 2018-04-26T12:50:39 [INFO] JVM vendor: Azul Systems, Inc. 2018-04-26T12:50:39 [INFO] JVM version: 25.162-b01 2018-04-26T12:50:39 [INFO] JVM started: 2018-04-26 19:50 GMT 2018-04-26T12:50:39 [INFO] Running interactively under super-user: root. 2018-04-26T12:50:39 [WARN] System is running low on memory: 11883MB total (508MB free) 2018-04-26T12:50:39 [INFO] Initializing JDBC drivers. 2018-04-26T12:50:39 [INFO] Loading configuration... 2018-04-26T12:50:39 [INFO] Initializing license manager... 2018-04-26T12:50:40 [WARN] No valid licenses were found. This will prevent site modification and the running of scans. 2018-04-26T12:50:40 [INFO] Initializing maintenance manager... 2018-04-26T12:50:40 [INFO] Renamed /opt/rapid7/nexpose/nsc/maintenance.xml to /opt/rapid7/nexpose/nsc/maintenance.bak 2018-04-26T12:50:40 [INFO] Initializing crypto subsystem... 2018-04-26T12:50:40 [INFO] Initializing plugins... 2018-04-26T12:50:40 [INFO] Initializing authentication services... 2018-04-26T12:50:40 [INFO] Initializing web server... 2018-04-26T12:50:40 [INFO] Configuring web server. 2018-04-26T12:50:40 [INFO] Generating skin: /opt/rapid7/nexpose/nsc/htroot/scripts/nexpose-skin.js 2018-04-26T12:50:40 [INFO] Generating feature set: /opt/rapid7/nexpose/nsc/htroot/scripts/nexpose-features.js 2018-04-26T12:50:40 [INFO] Context loader config file is jar:file:/opt/rapid7/nexpose/nsc/lib/nsc.jar!/META-INF/context.xml 2018-04-26T12:50:40 [INFO] Initializing ProtocolHandler ["http-nio-3780"] 2018-04-26T12:50:40 [ERROR] Failed to initialize end point associated with ProtocolHandler ["http-nio-3780"] 2018-04-26T12:50:40 [ERROR] Failed to initialize connector [Connector[HTTP/1.1-3780]] 2018-04-26T12:50:40 [ERROR] A critical error occured during initialization 2018-04-26T12:50:40 [INFO] Adding maintenance task NexposeRecovery 2018-04-26T12:50:40 [INFO] Reinitializing web server for maintenance mode... 2018-04-26T12:50:40 [INFO] Stopping ProtocolHandler ["http-nio-3780"] 2018-04-26T12:50:40 [INFO] Destroying ProtocolHandler ["http-nio-3780"] 2018-04-26T12:50:40 [INFO] Accepting web server logins. 2018-04-26T12:50:40 [INFO] Found a pending maintenance task: NexposeRecovery 2018-04-26T12:50:40 [INFO] Entering maintenance mode, only administrator logins permitted. 2018-04-26T12:50:40 [INFO] Maintenance Task Started 2018-04-26T12:50:40 [INFO] Accepting console commands. > 2018-04-26T12:50:40 [ERROR] Error during server initialization. 2018-04-26T12:50:40 [INFO] Shutting down immediately 2018-04-26T12:50:40 [WARN] Error stopping quartz schedulers. 2018-04-26T12:50:40 [INFO] Shutting down web server... 2018-04-26T12:50:40 [INFO] Pausing ProtocolHandler ["http-nio-3780"] 2018-04-26T12:50:40 [INFO] Stopping service Tomcat 2018-04-26T12:50:40 [ERROR] Problem shutting down Tomcat 2018-04-26T12:50:40 [INFO] Web server stopped 2018-04-26T12:50:40 [INFO] removing scheduled risk and history updater jobs 2018-04-26T12:50:40 [INFO] Shutting down extension manager 2018-04-26T12:50:40 [INFO] Extension manager shutdown successful. 2018-04-26T12:50:40 [INFO] Shutting down config manager 2018-04-26T12:50:40 [INFO] Shutting down crypto system 2018-04-26T12:50:40 [WARN] Error stopping connection scheduler. 2018-04-26T12:50:40 [INFO] Shutting down daemon manager 2018-04-26T12:50:40 [WARN] Error shutting down database. 2018-04-26T12:50:40 [INFO] Shutting down command console 2018-04-26T12:50:40 [INFO] Shutting down web server... NeXpose security console exited with code 0 What is going wrong here? Thanks!

Posted by Kevin Humphrey 10 months ago


Legtitamate False Positive claim?

As a security person, the InsightVM picked up these two vulnerabilities as an example: Obsolete Version of PHP PHP versions prior to 5.6 are no longer supported. General support for PHP 5.5.37 has been discontinued since July 10, 2016. It is strongly recommended to upgrade to PHP 5.6 or later. and PHP CGI Argument Injection The response I have back is that the version of Apache and PHP is fully supported. Can someone reconcile those two statements? Just want to have a sanity check before approve the exception. Here is the explaination: What version of httpd is supported on RHEL? Is the community version of Apache httpd supported? Which versions of Apache httpd are supported? How can I install Apache 2.4/2.5? Is Apache httpd 2.4/2.5 supported? Does Redhat support self compiled apache installations? What are supported install methods for apache 2.4(e.g. rpm and yum only etc.)? Support for apache installation. We need to update the httpd version from 2.4.9 to 2.4.12 . we are unable to find the same on portal. Please provide Apache executable file for this. Which is the latest version of httpd(Apache) server available from RHEL. Apache HTTPD Upgrade I am aware that the Apache HTTPD version supplied for RHEL7.1 is version 2.4.6.Will Redhat upgrade this to 2.5 in future for RHEL7? I also have RHEL6.6 OS. Will there be plans to upgrade the Apache Httpd package in future? Apache Prior to 2.4.4 and 2.2.24 Multiple Vulnerabilities Apache HTTP Server Prior to 2.2.25 Multiple Vulnerabilities httpd vulnerabilty on port 443 We patched httpd packages to latest (available on RHEL6 repository) to solve below vulnerabilties, but seems there is still vulnerability that Qualys is reporting What is the latest version of httpd supported on RHEL It looks like the latest is 2.2.3 but this is quite old. Does RHEL 7 supports Apache version 2.2.31?Else which Apache Version does RHEL 7 supports? Which versions of Apache are available for my version of Red Hat Enterprise Linux? It is necessary to install a specific version of Apache, does the installed version of Red Hat Enterprise Linux supports it? We need to know which is latest Apache (httpd) version that Redhat support? Does Apache/2.2.31 (Unix) supported in RHEL6 or RHEL7? Upstream is discussing EOL dates for PHP 5.3. Can you verify that RHEL6 will support PHP 5.3.x for the entire lifespan of RHEL6? Or is it possible that PHP 5.3.x will also become EOL for RHEL6? Please suggest how and where I can get the PHP 5.3.25 or above to install using Yum in RHEL6? Resolution At the time of this writing, we have following default versions of php packages available for RHEL5, RHEL6 and RHEL7 RHEL5 :- php-5.1 (latest RHEL provides php-5.3 in php53 package) RHEL6 :- php-5.3 RHEL7 :- php-5.4 The major version for php will remain as above for its whole life cycle. Please check below paragraph on how are RHEL packages managed. Red Hat Software Collections provides support for php-5.4, php-5.5, php-5.6, and php-7.0 for RHEL6 as well RHEL7 (as Software Collections follows a different naming convention, these packages are named as php54, php55, rh-php56, rh-php70 respectively). Please visit How to use Red Hat Software Collections for more information. Red Hat Enterprise Linux is a maintained collection of many different components, which are drawn from the wider open source software community. At the time our product is released we have a particular version of each of the software components, selected for features and stability. During the life cycle of our product we backport any relevant bug fixes and security enhancements created by the upstream maintainers to the packages that we maintain, as well as contributing any fixes that we do. We have our own version numbering scheme for the packages that we create based on these backported changes. We do not change the version of any of the software components based on the release of a new version by an upstream project. For example, if PHP releases a new version of PHP. we will not update our package to that new version. This is in order to maintain compatibility and stability. We will backport any bug fixes or security errata that are relevant to the version of PHP that is part of Red Hat Enterprise Linux. For more information about Red Hat's policy on the backporting of security updates, visit the following; What is Red Hat's security patch and backport policy


Posted by Al Wilson 10 months ago