Troubleshooting
Problem
After deploying Db2 in a db2ucluster, the ping command fails. This applies to IBM Cloud Pak for Data 4.5.1 and 4.5.2 on Red Hat OpenShift Kubernetes Service (ROKS). Addition of a kernel parameter might be required.
Symptom
- A Db2 pod remains in a 0/1 Ready state.
- After running the oc logs -f <db2u_pod> command on a Db2 pod with a -db2u-0 suffix, or -db2u-0, -db2u-1, -db2u-(n+1) suffixes in Db2 Warehouse MPP, the following ping: socket: Operation not permitted message is found in the pod log:
+ echo 'Command failed. Attempt 120/120:'
Command failed. Attempt 120/120:
+ sleep 5
+ true
+ timeout 1 ping -c 1 c-db2oltp-db2u-0.c-db2oltp-db2u-internal
ping: socket: Operation not permitted
+ [[ 120 -lt 120 ]]
+ fail 'The command has failed after 120 attempts.'
+ echo The command has failed after 120 attempts.
The command has failed after 120 attempts.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSHGYS","label":"IBM Cloud Pak for Data"},"ARM Category":[{"code":"a8m0z000000GoylAAC","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF040","label":"Red Hat OpenShift"}],"Version":"4.5.0"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
31 August 2022
UID
ibm16613853