Troubleshooting Secure Coder installation

Edit online

Use the following information to diagnose common installation and configuration issues for Concert Secure Coder.

Secure Coder installation fails

Symptoms

The Concert installation fails while deploying Secure Coder.

Resolution

  1. Verify that Secure Coder installation is enabled in the params.ini file. 
    INSTALL_CONCERT=true
INSTALL_SECURECODER=true
  2. Verify that Concert installation is also enabled.

    Secure Coder cannot be installed independently of IBM Concert.

  3. Review the installation log for additional error details. 
    ibm-concert/localstorage/logs/product_install_logs_<timestamp>.log

Required Secure Coder parameters are missing

Symptoms

The installer reports missing Secure Coder configuration parameters.

Resolution

  1. Verify that all required Secure Coder parameters are configured in the params.ini file.
  2. Required parameters vary depending on whether optional scanning and AI remediation capabilities are enabled.
  3. Review the installation documentation and ensure that all required configuration values are provided.

Missing credentials for optional scanning or AI capabilities

Symptoms

Validation fails before deployment or optional Secure Coder capabilities are unavailable after installation.

Resolution

  1. Verify that all required credentials are configured and available to the installation process.
  2. Review the installation documentation and confirm that the required credentials for enabled scanning and AI capabilities are provided.

SAST and SCA capabilities are unavailable after installation

Symptoms

SAST and SCA scan options appear in the IDE but are unavailable.

Resolution

  1. Verify that the required scanning capabilities are enabled for your Secure Coder installation.
  2. Scan options can remain visible in the IDE even when the corresponding capability is disabled.
  3. Review the installation configuration and verify that all required integrations and credentials are configured.

For more information, see the installation documentation.

Registry authentication fails

Symptoms

The installer cannot download required container images.

Resolution

  1. Verify that your IBM entitlement key is valid.
  2. Verify the registry configuration parameters.
  3. Confirm that registry credentials are correctly exported before running the installer.
  4. Authenticate to the registry and retry the installation.

Secure Coder deployment pods are not ready

Symptoms

Secure Coder pods remain in a non-ready state after installation.

Examples include:
  • CrashLoopBackOff
  • ImagePullBackOff
  • Readiness probe failures

Resolution

  1. Verify that required container images were downloaded successfully.
  2. Verify that registry credentials and image pull secrets are configured correctly.
  3. Review Secure Coder deployment logs and pod events.
  4. Verify that Secure Coder configuration values and secrets were created successfully.
  5. Correct any reported deployment issues and restart the affected pods.

Secure Coder service does not start

Symptoms

The installation completes, but Secure Coder is unavailable.

Resolution

  1. Verify that the Secure Coder deployment completed successfully.
  2. Review Secure Coder deployment logs.
  3. Verify that all required configuration values and credentials are available.
  4. Verify that required integrations are configured correctly.

SAST, SCA, or AI-assisted remediation capabilities remain unavailable

Symptoms

SAST, SCA, or AI-assisted remediation capabilities remain unavailable after configuration changes.

Resolution

  1. Verify that all required integrations and credentials are configured.
  2. Verify that the scanner management script completed successfully.
  3. Check the current scanner status.
  4. Verify that the Secure Coder deployment restarted successfully after the configuration change.

Scanner configuration changes are not applied

Symptoms

SAST, SCA, or AI-assisted remediation capabilities do not reflect recent configuration changes.

Resolution

If scanning capabilities were enabled or disabled after installation:

  1. Verify that the scanner management script completed successfully.
  2. Verify that the Secure Coder deployment restarted successfully.
  3. Check the current scanner status.
  4. Retry authentication from the IDE extension.
  5. If the issue persists, review the Secure Coder deployment logs.

Secure Coder remediation workflows time out in OCP environments

Symptoms

Remediation workflows do not complete successfully in OpenShift Container Platform (OCP) environments.

Resolution
  1. Verify that your environment is running a supported IBM Concert with Secure Coder OCP support.
  2. Review Secure Coder deployment and remediation workflow logs.
  3. If the issue persists, collect diagnostic information and contact IBM Support.

Container runtime validation fails

Symptoms

Installation prerequisite validation fails for the container runtime.

Resolution

  1. Verify that a supported container runtime is installed.
  2. Ensure that the DOCKER_EXE parameter matches the installed runtime:
    • docker
    • podman
  3. Rerun prerequisite validation before installing Secure Coder.

VM prerequisites validation fails

Symptoms

Prerequisite validation fails before installation starts.

Resolution

  1. Run the VM prerequisite installation and validation utilities.
  2. Verify that all required prerequisites are installed before rerunning the installation.

Collect installation logs

Collect the following information before contacting IBM Support:

Installation logs

ibm-concert/localstorage/logs/product_install_logs_<timestamp>.log

VM prerequisite logs

ibm-concert/localstorage/logs/manage-prereqs-vm-<timestamp>.log

When to contact IBM Support

Contact IBM Support if:
  • Installation continues to fail after configuration issues are corrected.
  • Secure Coder services remain unavailable after installation completes.
  • SAST, SCA, or AI-assisted remediation capabilities remain unavailable after verification.
  • Deployment logs indicate errors that cannot be resolved through the documented procedures.
Before opening a support case, collect:
  • Installation logs
  • VM prerequisite logs
  • Relevant deployment logs
  • Configuration details with sensitive values removed