Agent and the audit service are not running.
Solution
Follow the Prerequisites section to know the steps to check the status and logs of the agent and the audit service
The service status will be reviewed from the Rancher Web UI
Prerequisites
List of prerequisites that need to be fulfilled to ensure the working of all the features of the synergy product.
Firewall Whitelisting
The list of the endpoints need to be accessible from GV Management Server to keep the system updated.
*.k3s.getvisibility.com
git.rancher.io
docker.io
quay.io
gcr.io
registry.opensource.zalan.do
github.co
storage.googleapis.com
*.k3s.io
github.com
*.amazonaws.com
Following firewall rules should be set. Firewall Port Opening Matrix:
Sn | Source | Destination | Port | Protocol | Direction | Comments |
1 | User’s Windows Machine | Getvisibility Management Server | 443,80 | TCP | Bi-direction | Source machine will have Synergy Agent installed on it and will communicate with the Focus Server |
2 | Windows machine with Browser,ssh,scp enabled | Getvisibility Management Server | 443,80,22 | TCP | Single direction from source to destination |
To access the Focus machine via ssh and its services via browser. |
3 | Getvisibility Management Server | File Server | 137,139,445 | TCP/UDP | Single direction from source to destination | To access the file server from the GV server during the File/AD scan |
Supporting Services
Below services are involved in supporting the Getvisibility Platform. They need to be up and running
Kafka
Postgresql
Consul
K3s
K3 service is running as systemd service and its status can be known by running “systemctl status k3s” on the CLI of the Getvisibility Management Server.
If the service is not running then execute “sudo systemctl start k3s.service”
The basic level of health checkup of the remaining services can be performed by using the Rancher Web UI.
Status of individual services by following the steps mentioned below
Login to Rancher UI dashboard > Select Cluster Node > Workload > Search for the service in the “Filter” search box |
The keyword “Active” is the current status of the service, which means the service is up.
Note: The rancher Web UI link will be shared by the Getvisibility team
Collecting Logs
The logs of the service can be accessed by selecting the service and clicking on it
Click on the triple dot sign present on the right most end of the service and click on the “view logs”
Note: The rancher Web UI link will be shared by the Getvisibility team
Agent’s Service Logs
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\GVClient.Service\Logs
Agent Service logs
%appdata%\GVClient.Service
%appdata%\GVClient.Plugins
%appdata%\GVClient.UIWPF