Installation troubleshooting (on-prem)

See the following information to troubleshoot on-prem installation issues.

Missing DASH Agile Service Manager integrations

The DASH integrations are not present, and the UI logs do not show any errors.

After installing the Hybrid Kit and running set-dash-config.sh, the Agile Service Manager UI attempts to create the DASH integrations. If the integrations are not present in the Dashboard Application Services Hub console (that is, from the Navigation bar > Console Settings (Cog icon) > Console Integration), and there are no console errors in the ui.log file, the most likely cause is that the DASHFEDERATION__ENABLED parameter in the $ASM_HOME/etc/nasm-ui.yml file is set to False, and that therefore the DASH integration will not be built.

Workaround: Set the DASHFEDERATION__ENABLED option in the $ASM_HOME/etc/nasm-ui.yml file to True, and then restart DASH.

License issues

During a first installation of Netcool Agile Service manager, or when the license terms change, you will be prompted to accept the software license. If you do not complete this step, the software will not start and this error will occur:

ERROR: Couldn't find env file: /opt/ibm/netcool/asm/licenses/.accept_license

Workaround

To review and accept the license terms, use the following command:

/opt/ibm/netcool/asm/bin/license-review.sh

ASM_HOME variable warnings and errors

When running any docker-compose commands, such as starting or stopping Agile Service Manager, the docker-compose service needs to load the .env and docker-compose.yml files located in ASM_HOME. If you do not run the docker-compose command from the ASM_HOME directory, warnings and errors like the following may occur:

WARNING: The ASM_HOME variable is not set. Defaulting to a blank string.

ERROR: .IOError: [Errno 2] No such file or directory: u'/etc/nasm-docker-observer.yml'

ERROR: Can't find a suitable configuration file in this directory or any parent. Are you in the right directory? Supported filenames: docker-compose.yml, docker-compose.yaml

Workaround

You must run docker-compose commands from the ASM_HOME directory.

To ensure that your present working directory is ASM_HOME, you can take the following steps:

Change your current directory

To change your current directory to the ASM_HOME directory, use the cd command, as in the following example:

$ cd /opt/ibm/netcool/asm

Check your current directory

To verify that your current directory is the ASM_HOME directory, use the pwd command, as in the following example:

$ pwd
/opt/ibm/netcool/asm

Apply Elasticsearch patch during upgrade

During an upgrade, once the statefulsets are upgraded, the Elasticsearch pods may crash.

Workaround: To prevent this, apply the following patch:

kubectl patch statefulset ${RELEASE_NAME}-elasticsearch -p '{"spec":{"template":{"spec":{"securityContext":{"runAsUser":1000}}}}}'

where ${RELEASE_NAME} = the Agile Service Manager instance name being deployed.