IBM Support

Cloud Pak for Security: How to increase time out in UDI-UDIWORKERS pods

Troubleshooting


Problem

The CP4S default connection timeout for stix-shifter is 2 seconds.

Cause

Connectors can experience unstable connections, causing timeouts that may lead to issues such as missing or incomplete data and failed responses due to connection timeouts.

Diagnosing The Problem

STIX-Shifter's default connection timeout is 2 seconds, which might be insufficient depending on network latency or service response times. You can override this timeout by setting the STIXSHIFTER_CONNECT_TIMEOUT environment variable in the udi-worker deployment. So, you can increase the timeout by 20 seconds.

Resolving The Problem

Steps: Attempt to Update the Default Connection Timeout

1.Edit the deployment:

oc edit deploy udi-udiworkers

2.Navigate to the following section in the YAML:

spec-> template ->spec->containers under the -"env" add the following 2 lines with the correct indentation:

spec:
  template:
    spec:
      containers:
          - env:

3. Under the env section, add the following two lines with the correct indentation:

  - name: STIXSHIFTER_CONNECT_TIMEOUT
          value: "20"

4. Save the file using:

:wq!

5. Verify if pods restart automatically. If not, manually delete each pod to trigger a restart:

oc get pods -l name=udi-udiworkers

oc delete pod <POD_NAME>

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTDPP","label":"IBM Cloud Pak for Security"},"ARM Category":[{"code":"a8m3p000000F8yvAAC","label":"Cloud Pak for Security (CP4S)"}],"ARM Case Number":"TS018645932","Platform":[{"code":"PF118","label":"Red Hat OpenShift Platform"}],"Version":"1.10.0;1.11.0"}]

Document Information

Modified date:
27 June 2025

UID

ibm17238151