×
Rolling back the Netprobe
The RollbackNetprobe.yaml
CloudFormation template rolls back the Netprobe on existing EC2 instances using the AWS Systems Manager (SSM) by restoring the most recent backup archive created under <NetprobeInstallDirectory>/backup/netprobe/
and restarting the netprobe.service
.
Prerequisites Copied
- The target EC2 instances must have an SSM Agent installed and running.
- Target instances must have an IAM instance profile attached with the following permissions:
AmazonSSMManagedInstanceCore
(for SSM communication)
- The
netprobe.service
systemd unit must exist on the instances. - A backup archive must exist at
<NetprobeInstallDirectory>/backup/netprobe/netprobe-*.tar.gz
. This is created by the update process.
Input parameters Copied
Target EC2 configuration Copied
Parameter | Description | Default | Required |
---|---|---|---|
InstanceIds |
Comma-separated list of existing EC2 Instance IDs | Yes |
Netprobe configuration Copied
Parameter | Description | Default | Required |
---|---|---|---|
NetprobeInstallDirectory |
Directory where Netprobe is installed | ~/geneos | No |
Verification and debugging Copied
Run the following commands if you need to verify or debug your deployment.
View template execution logs Copied
ssh -i <privatekey> <user>@<host> "sudo cat /var/log/amazon/ssm/amazon-ssm-agent.log"
Check the service status Copied
ssh -i <privatekey> <user>@<host> "systemctl is-active <service>.service"
Download the logs Copied
ssh -i <privatekey> <user>@<host> "sudo tar -cvz -C "cd <install_dir> && find <service> -type f -name '*.log' -print0 | sudo tar --null -czf - --files-from -" > <service>-logs.tar.gz
["Geneos"]
["Geneos > Netprobe"]
["User Guide"]