How to Fix Deployment Agent issues

sk92488   -  Installation service is not running. Package actions disabled
sk109466 -  Please wait while updating the Deployment Agent
sk92449   -  Upgrade CPuse to 1298

1. Connect to command line on Gaia machine.
2. Log in to Clish.
3. Run this command:
   HostName:0> show installer status build
   

   Example output:
   Build number: 974 (agent build is up to date)

(3-C) How to manually install the CPUSE Agent package

Notes:

• Updating of CPUSE (Gaia Software Updates) Agent from build 839 and above does not cause traffic outage, or cluster failover.
• Updating of CPUSE (Gaia Software Updates) Agent from build 822 and lower might cause short traffic outage, or cluster failover. For details, refer to sk106696.

Procedure:

1. Transfer the CPUSE Agent package (DeploymentAgent_<build>.tgz) to the machine (into some directory - e.g., /some_path_to_CPUSE/).
2. Unpack the CPUSE Agent package:
   [Expert@HostName:0]# cd /some_path_to_CPUSE/
   [Expert@HostName:0]# tar -zxvf DeploymentAgent_<build>.tgz
3. Install the CPUSE Agent RPM:
   [Expert@HostName:0]# rpm -Uhv --force CPda-00-00.i386.rpm
   Notes:
   
   • During the installation, you will see the "Waiting for DAService to stop..." message.
     The preinstall script tries 60 times to stop the DAService executable (by issuing the "dbget installer:stop" command).
     If the script does not succeed to stop the DAService, then it kills it and the installation continues.
   • Related solution: sk119954 - "error: Failed dependencies" during manual installation of CPUSE Agent package
4. [Optional] Restart all Clish daemons and ConfD daemon:
   To improve CPUSE Agent, new CPUSE commands are added to Clish from time to time.
   It is necessary to restart all Clish daemons for new CPUSE Clish commands to become available, and to restart ConfD daemon.
   
   1. If your default shell is CLISH (/etc/cli.sh), then log in to Expert mode.
      If your default shell is BASH (/bin/bash), then log out from all Clish sessions.
   2. Kill all running Clish daemons (they will be restarted automatically):
      [Expert@HostName:0]# killall -v clish clishd
      Important Note: If your default shell is CLISH (/etc/cli.sh), then after issuing this command, you will be disconnected / logged out from all active sessions.
   3. Restart the ConfD daemon:
      
      1. [Expert@HostName:0]# tellpm process:confd
      2. [Expert@HostName:0]# tellpm process:confd t
      Maintenance window is required:
      
      • When confd daemon is starting, by design, it restarts any currently running routed daemons (by sending a TERM signal). It is done to avoid possible issues in Gaia Clish (e.g., returning invalid results for routing-related commands like "show route").
      • Since routed daemon is responsible for all the routing in Gaia OS, short traffic outage will occur while routed daemon is being restarted.
      • Since routed daemon is a Critical Device in Check Point cluster (since R76), cluster fail-over might occur while routed daemon is being restarted (refer to sk92878).
5. Start the CPUSE Agent manually:
   [Expert@HostName:0]# $DADIR/bin/dastart

Note: For details about Clish commands, refer to section "(4-D) How to work with CPUSE - "How to ..." (Gaia Clish commands, Gaia Portal actions, configuration, etc.)".

1. Connect to command line on the target Gaia OS.
2. Log in to Clish.
3. Acquire the lock over Gaia configuration database:
   HostName:0> lock database override
4. Show the relevant packages:
   HostName:0> show installer packages {available-for-download | downloaded | imported | recommended}
   

   Specific commands:
   HostName:0> show installer packages available-for-download
   HostName:0> show installer packages downloaded
   HostName:0> show installer packages imported
   HostName:0> show installer packages recommended

5. Verify the package - check whether this package can be installed without conflicts:
   HostName:0> installer verify[press Space key][press Tab key]
   HostName:0> installer verify <Package_Number>
   Result of this test should be:
• For Hotfix package:
  Result: Installation is allowed
Status: Available for Install
• For Minor / Major Version:
  Result: Verifier results: Clean Install: Installation is allowed. Upgrade: Upgrade is allowed.
Status: Available for Install 

Note: For details about Clish commands, refer to section "(4-D) How to work with CPUSE - "How to ..." (Gaia Clish commands, Gaia Portal actions, configuration, etc.)".

1. Transfer the CPUSE offline package (TGZ) / exported package (TAR) to the target Gaia machine (into some directory, e.g., /some_path_to_package/).
2. Connect to command line on the target Gaia OS.
3. Log in to Clish.
4. Acquire the lock over Gaia configuration database:
   HostName:0> lock database override
5. Import the package from the hard disk:
   Note: When import completes, this package is deleted from the original location.
   HostName:0> installer import local <Full_Path>/<Package_File_Name>.<TGZ_or_TAR>
   Example:
   HostName:0> installer import local /var/log/path_to_pkg/Check_Point_Hotfix_R77.tgz
6. Show the imported packages:
   HostName:0> show installer packages imported