- Site Collector Overview
- Get Started with Site Collectors
- Install Site Collector
- Set Up Collectors
- Manage Site Collectors
- Site Collector Monitoring
- Troubleshoot the Site Collector
- Pre-checks failed during Site Collector installation and upgrade
- Site Collector UI shows the status INSTALLATION_ERROR
- Download Support Packages for Troubleshooting
- How to reboot the Virtual Machine (VM) successfully to apply security updates?
- What information must be added while creating a support ticket to resolve an issue?
- Site Collector UI is not displaying the heartbeats
- Splunk Collector can't be set up
- Splunk Collector is set up however, logs are not reaching DL/AA
- Only a few of the installed Splunk Collectors are processing logs or EPS has dropped by 50% as compared to last hour
- The Windows Active Directory Collector (formerly known as LDAP Collector) is set up, however, the context data is not reaching DL/AA
- The Windows Active Directory Collector (formerly known as LDAP Collector) is stuck in the ‘Update’ mode after deployment
- Installation is initiated; however, the collector shows the status as ‘Setting Up’ for some time
- Data Lake and Advanced Analytics Does Not Show Context Data
- Context Data from Windows Active Directory Collector is Segmented
- Minifi Permission Denied - Logback.xml File Missing and Config File Update - Failed Error Occurred while Installing the Windows Event Log Collector
- Where should I upload proxy certificates if I am running proxy with TLS interception?
- How to upgrade Linux collector instance?
Installation is initiated; however, the collector shows the status as ‘Setting Up’ for some time
Solution: While setting up the collector, Site Collector Core management script adds, and configures the LDAP processor and runs the configured collector twice. The collector shows the status as ‘SETTING UP’ while the connection check is running, until the runs are finished for the first pull and for the subsequent incremental pull. The processing time depends on the amount of context data to be pulled and the sync frequency. The collector takes some time to pull data for the first time because the first data pull is equivalent to the full snapshot. After the first two pulls, the collector displays the status as ‘RUNNING’. This is also true for your full snapshot request via Site Collector UI. You must check the context volume to be initially pulled from AD and calculate time before the connection check is finished.