GWAVA 5 (any build) Linux Cluster Update
GWAVA4 on a cluster needs to be updated to GWAVA 5. Are there any special steps to take to do this?
Yes. There are some important steps to consider when updating a GWAVA 4 Cluster to a GWAVA 5 cluster. Follow these steps to make the appropriate changes
1) Modify the directory path for the GWAVA start script.
GWAVA 42) Modify services.conf.
Open the /mnt/data/gwava/assets/bin/gwava4 file in your favorite editor and change the G4_LOCATION variable (found approximately on line 16) to reflect the path where you moved GWAVA. If you moved GWAVA to /mnt/data/gwava the variable would look like the following:GWAVA 5G4_LOCATION="/mnt/data/gwava/"
Open the /mnt/data/gwava/assets/bin/gwava5 file in your favorite editor and change the GWAVA_LOCATION variable (found approximately on line 16) to reflect the path where you moved GWAVA. If you moved GWAVA to /mnt/data/gwava the variable would look like the following:GWAVA_LOCATION="/mnt/data/gwava/"
In GWAVA 5 there is a new module that is added (GWVSTATS). Add the gmanaddress to gwvstats similar to the other modules.3) Update Load Script.
program ! gwvstats
arguments ! /gmanaddress=10.1.1.58
GWAVA 5 uses a new version of Kaspersky. Remove the GWAVA 4 part and add the GWAVA 5 section.4) Update Unload Script.
#start GWAVA5(Optional): If you want to start and stop GWAVA5 from any location within a shell on the node that has GWAVA5 loaded you can add another symbolic link for the GWAVA5 startup script in /usr/sbin. This will make it so you can type 'gwava5 stop/start/restart/status' from within the terminal without having to be in the assets/bin directory or add the full path. Add the following line after the KAV line in your cluster load script.
ignore_error ln -sf /mnt/data/gwava/services/kav/kavlx/bin/updatekav.sh /etc/cron.hourly/
ignore_error /mnt/data/gwava/assets/bin/gwava5 start
GWAVA 5: ignore_error ln -sf /mnt/data/gwava/assets/bin/gwava5 /usr/sbin/gwava5Remove the GWAVA 4 line:
GWAVA 4: ignore_error ln -sf /mnt/data/gwava/assets/bin/gwava4 /usr/sbin/gwava4
Remove the section for GWAVA 4 and add a new section for GWAVA 5.
#stop GWAVA5(Optional): If you added a symbolic link for the gwava4 start/stop script, you will need to remove the symbolic link. Add the following line to your cluster unload script before the KAV line.
ignore_error unlink /etc/cron.hourly/updatekav.sh
ignore_error /mnt/data/gwava/assets/bin/gwava5 stop
GWAVA5: ignore_error unlink /usr/sbin/gwava5
This article was originally published in the GWAVA knowledgebase as article ID 1920.