Skip to main content
Delphix

CLI Message "management service is currently unavailable" Causes Application to Fail when VDB Job Completes (KBA6253)

 

KBA

KBA# 6253

 

Issue

When using the CLI in 6.0 engine prior to the 6.0.3.0 release, there is a possibility that CLI jobs can throw this message when an HTTP 404 response is encountered:

---Removing database vchild ---
    Dispatched job JOB-2743
    DB_DELETE job started for "mssql/vchild".
    Validating that this dataset is managed by Delphix.
    Stopping virtual database.
    Unmounting datasets.
    Unexporting storage containers.
    Metadata for dSource "vchild" successfully deleted.
The operation could not be completed because the management service is currently unavailable. If the system is starting up, 
please log out and try again at a later point. Otherwise, run "system restart" as a system user and try to reconnect at a 
later point. If the problem persists, please contact Delphix support.

  • In this specific example, a VDB is deleted and the error can cause some applications to fail. 
  • For example, if the CLI calls are passed from a Windows Powershell application using a utility that can pass commands to the Delphix engine via SSH, such as PLINK.exe, the Powershell script can interpret the message as an error and decide to fail the application. 
  • With the VDB job completing on Delphix engine, such an application disruption can cause downstream operations to halt leading to manual intervention with the application workflow to resolve other issues.
  • In this case the Delete VDB leads to a SYNC on parent VDB, and a Provision of the deleted VDB.  If the Powershell script indicates the delete failure, confusion can ensue when the developer checks the GUI for the status of the datasets. They will find the job completed but now their application workflow has been disrupted.

 

Prerequisites

Issue only occurs with 6.0 engines prior to 6.0.3.0 release.

Applicable Delphix Versions

Major Release All Sub Releases
6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0
 
 
 
Major Release All Sub Releases
6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0

5.3

5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0

5.2

5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1

5.1

5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0

5.0

5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1 ,5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

4.3

4.3.1.0, 4.3.2.0, 4.3.2.1, 4.3.3.0, 4.3.4.0, 4.3.4.1, 4.3.5.0

4.2

4.2.0.0, 4.2.0.3, 4.2.1.0, 4.2.1.1, 4.2.2.0, 4.2.2.1, 4.2.3.0, 4.2.4.0 , 4.2.5.0, 4.2.5.1

4.1

4.1.0.0, 4.1.2.0, 4.1.3.0, 4.1.3.1, 4.1.3.2, 4.1.4.0, 4.1.5.0, 4.1.6.0

Resolution

Issue is resolved in 6.0.3.0 release.  After upgrading to this version no changes are required with the CLI application(s).

 

Related Articles

The following articles may provide more information or related information to this article:

  • link
  • link
  • link