Mission Control 2.x

Using Mission Control 3.x ?
JFrog Mission Control 3.x User Guide

Need help with other JFrog products ?

JFrog Enterprise+ User Guide
JFrog Artifactory User Guide
JFrog Xray User Guide
JFrog Distribution User Guide
JFrog Bintray User Guide
JFrog Access User Guide
JFrog CLI User Guide

Expand all   Collapse all

Have a question? Want to report an issue? Contact JFrog support

Skip to end of metadata
Go to start of metadata

Installation

 There is no standalone ZIP installtion for OSX or Windows.
Cause
From version 2.0 standalone ZIP installations have been deprecated from Mission Control.
Resolution
For a full list of installation options, please refer Installation and Upgrade

Disaster Recovery

 DR fails when the DR master Artifactory service uses Master Key Encryption.
Cause
The DR target is not able to decrypt passwords since it does not have the same Master Key as the DR Master service.
Resolution
Sync over the Artifactory Master Key from the DR Master to your Target Artifactory service. This will allow all passwords to he properly decrypted once your security settings are replicated to the Target.

For details, please refer to Master Key Encryption in the JFrog Artifactory User Guide. 

Scripting

 Configuration scripts are not working at all.
Cause
 In version 2.0, Mission Control made significant changes in how configuration scripts are written. These changes are not backwards compatible, so any scripts written for Mission Control version 1.x will not work. For details, please refer to Configuration Scripts. <TBD update link>.
Resolution
 You need to migrate your scripts to work with Mission Control 2.0 and above. While the migration process is not automatic, it is quite simple. For details please refer to Migrating Scripts from Version 1.x to Version 2.x. <TBD update link>
 Writing a script that implements a Star Topology has changed.
Cause
Previous to Mission Control version 2.0,  implementing a Star Toplogy was very complex, cumbersome and error-prone.
Resolution
A new configuration block was introduced in Mission Control version 2.0 to make implementing a Star Toplogy, using either push or pull replication, very simple. For details, please refer to Star Toplogy. <TBD update link>  
 Writing a script that implements a Full Mesh Topology has changed.
Cause
Previous to Mission Control version 2.0,  implementing a Full Mesh Toplogy was very complex, cumbersome and error-prone.
Resolution

A new configuration block was introduced in Mission Control version 2.0 to make implementing a Star Toplogy, using either push or pull replication, very simple. It is now much easier to implement a Full Mesh by configuring each node with its own Star Topology.

For details, please refer to Star Toplogy. <TBD update link>  

 Any repository created with a script uses the Maven default layout even when it's not a Maven repository
Cause
 The default layout for any new repository is maven-2-default.
Resolution
When creating a new repository in a script, modify the repoLayoutRef field to the correct layout for your repository type.
 When updating a repository using a script, some parameters that are not specified in the script are modified.
Cause
When updating a repository using a script, any parameter that is not explicitly specified is updated to the default value of that parameter. 
Resolution
 When updating a repository using a script, specify all the parameter for that repository that don't take the default value, even those that shouldn't change.
 You can't find any scripts in the Mission Control installation structure.
Cause
 Mission Control scripts are maintained in one of its internal databases which cannot be accessed form outside of Mission Control.
Resolution
To access Mission Control scripts, configure a Git repository to which Mission Control will synchronize all its scripts as described under Git Integration <TBD update link>. This also allows you to create and modify your scripts using any external editor.

Graphs

 You can't see any historical data for a newly added service.
Cause
 After adding a service to the system, it can take up to 15 minutes before Mission Control displays any data samples.
Resolution
 Just wait up to 15 minutes, and you should then see data for the new added service.
 You still see data for deleted services
Cause
 To preserve historical data for deleted services, Mission Control stores the data under a fictitious service named <deleted_service_name>_old_xx (e.g. art1_old_01, art1_old_02. XX will be incremented if you delete and re-add a service with the same name.
Resolution
 When viewing graphs for all services, these deleted will still appear, however, you may also focus on a specific service.

Groups

 You cannot create Groups in Mission Control.
Cause
 From version 2.0, Groups have been deprecated in Mission Control.
Resolution
Previous to version 2.0, creating Groups was a convenient way to run scripts on a number of Artifactory services at once since each script could only perform one action at a time. From version 2.0, scripting is much more flexible and you can specify any number of services on which a script should act.

REST API

 The REST API is not working at all.
Cause
In version 2.0, Mission Control implemented a major upgrade of the REST API which is not backwards compatible with previous versions. 
Resolution
You need to update your scripts to use the new REST API. For details, please refer to the updated Mission Control REST API <TBD update link> page, especially the Version Mappings <TBD update link>section that describes how to map endopints from previous versions to version 2.0 and above.

Services

 There is no storage summary information in the Services screen.
Cause
Mission Control extracts storage information about managed Artifactory services using a REST API call.
Resolution
In some cases, the REST API call may take time to return. Wait a few moments and refresh the screen. 

 



  • No labels