Update 5.5.0 CA or 5.5.x to 5.5.5

This page describes how to update Service Impact 5.5.0 CA or 5.5.x to 5.5.5.

The following list outlines recommended best practices:

Verify that Resource Manager is running normally. The update procedures stop, start, or restart specific services, but the required starting point is Resource Manager running normally.
Export service models. Exporting before an update provides a quick restore option if the update fails. If necessary, you can uninstall, remove the ZenPack, install the working version, and then import the service models.
Review the release notes for this release before proceeding. The latest information is provided there.
Use screen, tmux, or a similar program to establish sessions on the Control Center master host. If you become disconnected, the commands you initiate will continue to run.
Review the procedures in this section before performing them. Every effort is made to avoid mistakes and anticipate needs; nevertheless, the instructions may be incorrect or inadequate for some requirements or environments.

Update DynamicView ZenPack

Update DynamicView to v1.7.1 or a more recent version.

Download required files

To perform this procedure, you need:

A workstation with internet access.
Permission to download files from delivery.zenoss.io. To request permission, file a ticket at the Zenoss Support site.
A secure network copy program.

Follow these steps:

In a web browser, navigate to delivery.zenoss.io, and then log in.
Download the Docker image file for Service Impact.
- install-zenoss-impact_VERSION.run
Replace Version with the most recent version number available on the download page. 3. Download the Service Impact ZenPack files. - ZenPacks.zenoss.ImpactServer-VERSION-py2.7.egg - ZenPacks.zenoss.Impact-VERSION-py2.7.egg

Replace Version with the most recent version number available on the download page. 4. Use a secure copy program to copy the Docker image file and the ZenPack files to the Control Center master host.

Stage required files on the master host

To perform this procedure, you need permission to log in to the Control Center master host as root, or as a user with superuser privileges. Use this procedure to install the Docker image and to prepare the ZenPack files for installation.

Log in to the Control Center master host as root or as a user with superuser privileges.
Stage the Docker image file and ZenPack files in /tmp.
1. Create a directory in /tmp for the files. The directory must be local (not mounted) and must be readable, writable, and executable by all users. For example, /tmp/impact.
```
mkdir /tmp/impact
```
2. Copy or move the Docker image file and ZenPack files to /tmp/impact.
  
  Do not change the file names during the move or copy.
3. Change the file permissions. The files must have the same permissions as their parent directory.
```
chmod -R 777 /tmp/impact
```
Install the Service Impact image.
1. Change to the directory in which the Service Impact image is located.
```
cd /tmp/impact
```
2. Install the image.
```
yes | ./install-zenoss-impact_*.run
```

Update both Service Impact ZenPacks

Perform this procedure to update both Zenpacks, ZenPacks.zenoss.Impact and ZenPacks.zenoss.ImpactServer.

Log in to the Control Center browser interface.
In the Application column of the Applications table, click Resource Manager.
Scroll down to the Services table, and then locate the Impact service in the Infrastructure section.
Click Impact, and then locate the State Change Queue Length graph.
Log in to the Control Center master host as a user with serviced CLI privileges.
Stop the zenimpactstate service, and then verify that it stopped.
1. Stop the zenimpactstate service.
```
serviced service stop zenimpactstate
```
2. Verify that the service is stopped.
```
watch serviced service status zenimpactstate
```
In the Control Center browser interface, monitor the length of the state change queue. When the queue length is 0 (zero), proceed to the next step.
Stop the Infrastructure/Impact service, and then verify that it stopped.
1. Stop the Infrastructure/Impact service.
```
serviced service stop Infrastructure/Impact
```
2. Verify that the service is stopped.
```
watch serviced service status Infrastructure/Impact
```
Extract the upgrade script from the ZenPacks.zenoss.ImpactServer ZenPack, make the script executable, and start the upgrade script.
1. Change to the directory in which the Service Impact ZenPack egg file is located.For example, the /tmp/impact directory:
```
cd /tmp/impact
```
2. Extract the upgrade script from the ZenPacks.zenoss.ImpactServer egg file.Replace VERSION with the ZenPack version number:
```
unzip -p ZenPacks.zenoss.ImpactServer-VERSION-py2.7.egg ZenPacks/zenoss/ImpactServer/upgrade/upgrade.sh > upgrade.sh
```
3. Make the script executable.
```
chmod +x upgrade.sh
```
4. Start the upgrade script.
```
./upgrade.sh
```
  Note: The upgrade script might display CRITICAL warning messages, which can be ignored.
Start the Infrastructure/Impact service, and then verify that it started.
1. Start the Infrastructure/Impact service.
```
serviced service start Infrastructure/Impact
```
2. Verify that the service is started.
```
watch serviced service status Infrastructure/Impact
```

Install the ZenPacks.zenoss.Impact ZenPackReplace VERSION with the ZenPack version number:

serviced service run zope zenpack-manager install ZenPacks.zenoss.Impact-VERSION-py2.7.egg

Restart Zenoss services.
```
serviced service restart Zenoss.resmgr/Zenoss
```
Alternatively, restart the Zenoss services by using the Control Center browser interface.

Rebuild the graph database

Perform these steps:

Log in to the Control Center master host as root or as a user with superuser privileges.
Stop the Zenoss services, and then verify that the services are stopped.
1. Stop Resource Manager.
```
serviced service stop Zenoss.resmgr/Zenoss
```
2. Wait until all services are stopped. Use the watch command to monitor the status.
```
watch serviced service status Zenoss.resmgr/Zenoss
```
Start the Zenoss service that is needed to perform the graph rebuild.
1. Start the zeneventserver service.
```
serviced service start zeneventserver
```
2. Wait until the service is started. Use the watch command to monitor the status.
```
watch serviced service status zeneventserver
```
Identify the delegate hosts where Resource Manager is running.
```
serviced host list --show-fields=Pool,Name
```
The name of the resource pool where Resource Manager is running is not standardized.
Log in to a delegate host, and then start a Zope container.

The rebuild process requires approximately 1GB to 2GB per CPU core. If the delegate host does not have adequate main memory, the host may become unstable.
1. Log in to a delegate host in the Resource Manager pool as root or as a user with serviced CLI privileges.
2. Start a Zope container on the host.
```
serviced service shell zope
```
3. In the container, log in as user zenoss.
```
su - zenoss
```
Update the catalog and then initialize the server.
1. Update the catalog.
```
zenimpactgraph run -x catclean
```
2. Update the Service Impact graph in ZODB and Neo4j.
```
zenimpactgraph run --update
```
  For more information about the update process, see Graph update tips.
3. Exit the zenoss user account.
```
exit
```
4. Exit the Zope container.
```
exit
```

Restart all Zenoss services:

serviced service restart Zenoss.resmgr/Zenoss

Refresh the cache in your browser. The procedure varies by browser.