- 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?
PrevNext
How to reboot the Virtual Machine (VM) successfully to apply security updates?
Solution: Ensure that you perform the following steps to stop the Site Collector instance, then reboot the operating system (OS) on your VM. It is recommended to not to reboot the VM while the Site Collector instance is running.
Log in to Site Collector and stop the service through user interface. Alternatively, run the following command via CLI:
$ sudo /opt/exabeam/bin/ngsccli sitecollector stop
After running the above command, if you see a message No such file or directory which indicates that the ngsccli file does not exist, use the following command to stop the service:
cd /opt/exabeam/bin && sudo curl -o ngsccli https://storage.googleapis.com/ngsc_update/exa-cloud-prod/exa-ngsc/ngsccli && sudo chmod +x ngsccli && sudo ./ngsccli sitecollector stop
To validate that the service is stopped, run the following command:
$ sudo systemctl status exabeam-ngsc
Reboot your virtual machine (VM).
Start the services using the following command.
sudo /opt/exabeam/bin/ngsccli sitecollector start
Validate that the service is running by using the following command.
sudo systemctl status exabeam-ngsc