Avid Interplay Central Services Version Hot Fix ReadMe

Transcription

1 Avid Interplay Central Services Version Hot Fix ReadMe Document Version: The Interplay Central Services hot fix resolves a key issue reported from the field. For more information, see Fixed on page 11. Note: The hot fix installation package is available as an update installer only. It can only be installed on systems already running ICS 1.8 or ICS Note: The hot fix is cumulative. It includes all the fixes in If you have not already installed you can go directly to Document History Date Revised Version Changes Made May 15, First publication. Important Information Avid recommends that you read all the information in this ReadMe file thoroughly before installing or using any new software release. Important: Search the Avid Knowledge Base at for the most upto-date ReadMe file, which contains the latest information that might have become available after the documentation was published. The ICS 1.8.x documentation can be found here: Documentation.

2 Contents Document History... 1 Important Information... 1 Contents... 2 Compatibility Notes and Issues... 3 Obtaining the Software... 3 Update Installation versus Full Installation... 3 Installing ICS Using the Update Package... 3 Mounting the USB Key... 4 Unmounting and Removing the USB Key... 5 Single Node Installation... 5 Cluster Installation... 7 Fixed Fixed in Fixed in Copyright and Disclaimer

3 Compatibility Notes and Issues This document is a release note for the Interplay Central Services (ICS) hot fix for use with Interplay Central 1.8, Interplay Pulse, Interplay Sphere, and Interplay MAM. The following table indicates compatibility in this release: Component Interplay Central 1.8 Interplay MAM Interplay Sphere Version Supported 4.3.x Interplay Pulse 1.2, 1.3 Latest plug-in for Media Composer 6.5.x and 7.0.x and corresponding NewsCutter version. ICDS and later. Supported by Interplay Engine 2.5 and later. Note: For details on compatibility and the latest information on the Interplay Central Services, see the documentation available from the Interplay Central Services page of the Avid Knowledge Base: Documentation Obtaining the Software The ICS hot fix release is available directly on the Avid Download Center. Update Installation versus Full Installation As noted, the ICS release is a hot fix and can only be installed on systems that are already running ICS 1.8 or It is not available as a full installation. Installing ICS Using the Update Package The update package installation is for systems where ICS 1.8 (or ) is already installed. No backing up or restoring of system or other settings is required. However, the hot fix requires a restart of the Interplay Central service, so end-users will be kicked off without warning and will need to log in once the system is running again. Note the following: Alert end-users to save their work and log out of Interplay Central. The hot fix update process terminates the service. Unsaved work might be lost. Expected downtime is 10 minutes for the first server, and 5 minutes for subsequent servers. 3

4 For a cluster, note that the entire cluster must be taken off-line to perform the hot fix. Avid recommends that you install the hot fix during a maintenance window. After upgrading from ICS 1.8 to you must manually restart certain services (as indicated in this document). Mounting the USB Key To mount the USB key as a device: 1. Log in as root and insert the USB key into the ICS server. 2. Verify the name of the USB device. dmesg Linux information relating to hardware appears on the screen. Information for the USB key will appear near the end of the output, near the list of SCSI devices. The name of the USB key is found inside square brackets (e.g. [sdc]). This is the name you use to mount the key. 3. Create a mount point for the USB key and mount it. For example: mkdir /media/usb mount /dev/sdc1 /media/usb For a hot fix update, the /media/usb directory might already exist, dating from the initial install. Note: The name of the USB key, sdc (in this example), takes a 1 (one) in the mount command. This simply indicates a partition exists on the USB key. Formatting the USB key in Windows, when you prepared the USB key, created the partition. The USB key is now mounted and available for use. 4. Verify the success of mounting by listing the contents of the USB key. ls /media/usb 5. The system outputs the contents of the USB key, including the following: Interplay_Central_Services_Update_ _Linux.tar.gz This compressed Linux tar ball file contains the Linux package(s), installation script, etc., needed for the upgrade. 6. Alternately, verify the USB key has been mounted using the Linux df command. df -h Information is displayed about all mounted filesystems and devices, and should include information about the USB key, similar to the following (other output has been omitted, for clarity): Filesystem /dev/sdc1 Size Used Avail Use% Mounted on 7.5G 4.5G 3.0G 61% /media/usb 4

5 Unmounting and Removing the USB Key Once you have installed the hot fix, unmount and remove the USB key from the server. To unmount the USB key: 1. Ensure you are not currently on the USB key by changing directories: cd Note: In Linux the cd command without any arguments takes you directly to the user s home directory. If you are logged in as root, it takes you to the /root directory. You must be off the USB key to unmount it. 2. Unmount the USB key: umount /media/usb The USB key is now available for use in another server. If you receive an error message that the USB device is busy, unmount the USB key using the lazy ( -l ) option: umount l /media/usb Linux unmounts the filesystem, even when in use. 3. Remove the USB key from the server. Single Node Installation Before you begin: Alert end-users to save their work and log out of Interplay Central. The hot fix update terminates the service. Unsaved work might be lost. To install the hot fix using the update package on a single node: Note: This hot fix is available as an update package only. There is no full installation package. 1. Mount the USB key. 2. Change to the mount point. cd /media/usb 3. Unzip the installation package. tar -zxovf Interplay_Central_Services_Update_ _Linux.tar.gz 4. Change to the hot fix directory. cd Interplay_Central_Services_Update_ _Linux 5

6 5. Start the installation script../update-ics.sh Note: Be sure to use the dot-slash (./ ) notation, which tells Linux to look for the update-ics script in the current directory. Otherwise you will receive the following error message: -bash: update-ics.sh: command not found For security, Linux does not include the current directory (. ) in its PATH variable. You must specify the path, even when you are in the directory where the script or command is located. During the installation process, progress is displayed (details have been omitted, for clarity): Cleaning repos: ics_1_8_0_2 Cleaning up Everything Those familiar with Linux yum updates process will recognize the pattern of the output. The update completes with an indication of success: Complete! 6. Once the installation script has completed, verify version information for the installed ICS components. sh ics_version.sh Version information similar to the following is output: UMS Version: IPC Version: ICPS Version: ICPS manager Version: ACS Version: ICS installer: (Build 6) 7. Restart the Interplay Central service: service avid-interplay-central restart The service is restarted: Avid Interplay Central process has been started. Wait for Interplay Central web interface... Avid Interplay Central has been started successfully (12 seconds) 8. Restart the AAF Generator service: service avid-aaf-gen restart The service is restarted: Stopping the avid-aaf-gen_5 process [ OK ] Stopping the avid-aaf-gen_4 process [ OK ] Stopping the avid-aaf-gen_3 process [ OK ] 6

7 Stopping the avid-aaf-gen_2 process [ OK ] Stopping the avid-aaf-gen_1 process [ OK ] Starting process avid-aaf-gen_1 - Stat: [ OK ] Starting process avid-aaf-gen_2 - Stat: 0 [ OK ] Starting process avid-aaf-gen_3 - Stat: 0 [ OK ] Starting process avid-aaf-gen_4 - Stat: 0 [ OK ] Starting process avid-aaf-gen_5 - Stat: 0 [ OK ] 9. Unmount the USB key. Cluster Installation Installing the hot fix on a cluster is a simple automated update of the affected package(s). All ICS 1.8 system settings are preserved. There is no need to manually back up and/or restore any ICS system settings. All nodes in the cluster must be brought off-line to perform the update. Before you begin: Alert end-users to save their work and log out of Interplay Central. The hot fix update terminates the service. Unsaved work might be lost. Identify the master, slave, and load-balancing nodes Bring the cluster off-line by putting all nodes into standby To identify the master, slave, and load-balancing nodes: Recall that there are three types of nodes in a cluster: master, slave, and load-balancing. The master owns the cluster IP address. The slave assumes the role of master in the event of a failover. Any extra nodes play a load-balancing role, but can never take on the role of master. 1. Identify the master node of the cluster. Log into any machine in the cluster as root and type: crm_mon 2. In the output of that command, look for the line containing AvidClusterIP this service runs on the master server. For example, if the crm_mon command output contains the line: AvidClusterIP (ocf::heartbeat:ipaddr2): the master server is ics To identify the slave, look for the line containing Master/Slave Set. For example, if the crm_mon command output contains the lines: Started ics-1 Master/Slave Set: ms_drbd_postgres [drbd_postgres] Masters: [ ics-1 ] Slaves: [ ics-2 ] the slave server is ics To identify the extra nodes, look for the line containing Clone Set. For example, if the crm_mon command output contains the lines: 7

8 Clone Set: AvidAllEverywhere [AvidAll] Started: [ ics-1 ics-2 ics-3] the extra server in this case is ics-3. To bring the cluster off-line: 1. Alert all end-users to save their work and log out of Interplay Central (if you have not already done so). 2. Bring the cluster off-line by putting the load-balancing nodes into standby mode: crm node standby <node name> 3. Next, put the slave node into standby mode: crm node standby <node name> 4. Finally, put the master node into standby mode: crm node standby <node name> 5. The hot fix can now be installed on the cluster. To install the hot fix using the update package on the cluster: Note: This hot fix is available as an update package only. There is no full installation package. 1. On any node in the cluster, mount the USB key. 2. Change to the mount point. cd /media/usb 3. Unzip the installation package. tar -zxovf Interplay_Central_Services_Update_ _Linux.tar.gz 4. Change to the hot fix directory. cd Interplay_Central_Services_Update_ _Linux 5. Start the installation script../update-ics.sh Note: Be sure to use the dot-slash (./ ) notation, which tells Linux to look for the update-ics script in the current directory. Otherwise you will receive the following error message: -bash: update-ics.sh: command not found For security, Linux does not include the current directory (. ) in its PATH variable. You must specify the path, even when you are in the directory where the script or command is located. 8

9 During the installation process, progress is displayed (details have been omitted, for clarity): Cleaning repos: ics_1_8_0_1 Cleaning up Everything Those familiar with Linux yum updates process will recognize the pattern of the output: The update completes with an indication of success: Complete! 6. Once the installation script has completed, verify version information for the installed ICS components. sh ics_version.sh Version information similar to the following is output: UMS Version: IPC Version: ICPS Version: ICPS manager Version: ACS Version: ICS installer: (Build 6) 7. Unmount the USB key, proceed to the next node and follow the same pattern: a. Mount the USB key. b. Run the installation script. c. Unmount the USB key. 8. When all nodes have been updated, bring the master node back online: crm node online <node name> Bringing the master node back online starts the Avid Interplay Central service (which was stopped when you put the node into standby). 9. On the master node and slave node, restart the AAF Generator service: service avid-aaf-gen restart Note: The avid-aaf-gen service runs on all nodes, but is only used on the master and slave nodes. The service is restarted: Stopping the avid-aaf-gen_5 process [ OK ] Stopping the avid-aaf-gen_4 process [ OK ] Stopping the avid-aaf-gen_3 process [ OK ] Stopping the avid-aaf-gen_2 process [ OK ] Stopping the avid-aaf-gen_1 process [ OK ] Starting process avid-aaf-gen_1 - Stat: [ OK ] Starting process avid-aaf-gen_2 - Stat: 0 [ OK ] Starting process avid-aaf-gen_3 - Stat: 0 [ OK ] Starting process avid-aaf-gen_4 - Stat: 0 [ OK ] Starting process avid-aaf-gen_5 - Stat: 0 [ OK ] 9

10 10. Next, bring the slave node back online: crm node online <node name> 11. Finally, bring the load-balancing nodes back online: crm node online <node name> 12. Verify the cluster status and cluster failover status crm_mon crm_mon -f Verify the master, slave, and load-balancing nodes have rejoined the cluster, as expected. Verify the fail counts for the following resources (at a minimum): AvidIPC, AvidUMS, AvidACS, pgsqldb. Verify the cluster status. 13. If there are fail counts listed, run the cluster resource manager cleanup command to reset them: crm resource cleanup <rsc> [<node>] <rsc> is the resource name of interest: AvidIPC, AvidUMS, AvidACS, pgsqldb (or another) <node> (optional) is the node of interest. Note: If you receive an object/attribute does not exist error message, it indicates the resource is active on more than one node. Repeat the command using the group name for the resource (the everywhere form). For example, for the AvidAll resource, use AvidAllEverywhere. For AvidConnectivityMon, use AvidConnectivityMonEverywhere. Note: You can address the services contained in the postgres resource group (postgres_fs, AvidClusterIP and pgsqldb) individually, or as a group. For example, to reset the fail count for AvidALL resource, issue the following command: crm resource cleanup AvidAllEverywhere 10

11 Fixed The bug fixes listed in this section pertain to Interplay Central and/or Interplay MAM, as indicated. Note: For bugs fixed in ICS 1.8 see the Interplay Central Services 1.8 ReadMe. Fixed in MPLAY-1056 (Interplay MAM) Some proxies created by Mog Speedrail ingest devices would not play. MPLAY-1173 (Interplay MAM) Video Analysis failed for some MPG files. MPLAY-1223 (Interplay MAM) Some Harmonic media would how off-line or cause an ICS service to crash. MPLAY-1227 (Interplay MAM) Under certain conditions video analysis could result in excessive memory usage, resulting in server crash. MPLAY-1332 (Interplay MAM) Audio dropout could be heard during playback of some WMV media formats. MPLAY-1336 (Interplay Central) Some XDCAM media showed as offline when loaded into the player even though it was available. MPLAY-1338 (Interplay MAM) Load times for MPG media could be very slow. MPLAY-1339 (Interplay Central) Some Op1a media originating from an AirSpeed 5000 was substandard in quality. MPLAY-1402 (Interplay Central) For some MXF media transcoded by a Mog device, the first frame appeared online but the rest displayed as media offline. 11

12 MPLAY-1403 (Interplay Central) Some MXF media originating from a Mog devices showed visual artifacts in the player MPLAY-1417 (Interplay MAM) Playback of file-based formats that cannot be natively loaded in the player (e.g. MPEG-1, Sony XDCAM, WMV, Harmonic MXF) could fail after performing a seek. Seeking now works as expected. OS-1676 (Interplay Central) Audio channel settings for Natural Sound (NAT) and Sound on Tape (SOT) made using the Interplay Administration application were treated incorrectly in Interplay Central. Script sequences in Interplay Central showed 2 NAT or 2 SOT channels, although NAT or SOT were set to 1-Channel in the Interplay Administration application (via Application Database settings). Audio channel settings for NAT and SOT are now displayed and handled correctly in Interplay Central. Fixed in EA-2035 (Interplay Central) In some cases audio and video would fall out of sync during playback of groups clips containing audio-only clips. In addition, the sequence would display the incorrect frame rate. 12

13 Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting the Avid Web site at The terms of that license are also available in the product in the same directory as the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Avid Technology, Inc. Copyright 2014 Avid Technology, Inc. and its licensors. All rights reserved. Attn. Government User(s). Restricted Rights Legend U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are commercial computer software or commercial computer software documentation. In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR (a) and/or DFARS (a), as applicable. This product may be protected by one or more U.S. and non-u.s patents. Details are available at Trademarks Adrenaline, AirSpeed, ALEX, Alienbrain, Archive, Archive II, Assistant Avid, Avid Unity, Avid Unity ISIS, Avid VideoRAID, CaptureManager, CountDown, Deko, DekoCast, FastBreak, Flexevent, FXDeko, inews, inews Assign, inews ControlAir, Instinct, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, Interplay, ISIS, IsoSync, LaunchPad, LeaderPlus, ListSync, MachineControl, make manage move media, Media Composer, NewsCutter, NewsView, OMF, OMF Interchange, Open Media Framework, Open Media Management, SIDON, SimulPlay, SimulRecord, SPACE, SPACEShift, Sundance Digital, Sundance, Symphony, Thunder, Titansync, Titan, UnityRAID, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, and Xdeck are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners. Interplay Central Services v Hot Fix ReadMe 15 May 2014 This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form. 13