UIM - jdbc_response fails to gather QOS, error: "Unable to open a client session for :48001: Connection refused (Connection refused)"

book

Article ID: 220984

calendar_today

Updated On:

Products

DX Infrastructure Management

Issue/Introduction

This article documents an issue faced on Linux robots when strict_ip_binding is set to yes at robot level.

This problem results in the probe failing to connect or fetch any QoS metrics. Log level 5 probe logs will display the following errors: 

[Thread-9, jdbc_response] returning result
[Thread-9, jdbc_response] Profile (postgres-hits) Execution Time : 76 ms
[Thread-9, jdbc_response] Got 0 alarms from profile postgres-hits
[Thread-9, jdbc_response] Got 1 QOS messages from profile postgres-hits
[Thread-9, jdbc_response] profile sending QOS 0 postgres-hits postgres, type = QOS_JDBC_RESPONSE, value is 46.0
[Thread-9, jdbc_response] Caught exception while sending Qos for profile: postgres-hits(80) Session error, Unable to open a client session for :48001: Connection refused (Connection refused)

 

Environment

Release : 20.3
Component : UIM JDBC RESPONSE
postgresql_mcs_templates package (version 2.90)
jdbc_response probe (version 1.25)
Robot v9.33HF2 
Robots in proxy mode with strict_ip_binding set to yes (in robot.cfg)

Resolution

1. Access the IM Archive and select edit for the jdbc_response probe package. 

2. Go to the LINUX section for probe properties. 

3. Remove the following from the "Arguments" field: 

-DNIMV_CONTIP=$NIMV_CONTIP

4. Apply and save the changes. 

5. Redeploy the probe to the robots in question. 

Notes:
- If strict_ip_binding can be set to "no" this will also resolve the issue. 
- For each new jdbc_response package release, you must apply this change. 

Attachments