DUX fails to get keystone job status troubleshooting

Products

• CA Automic Dollar Universe

Issue/Introduction

We observed that for some of the UPROC's mapped as keystone jobs in DUX (Explorer) Applications are not getting execution status. How can we troubleshoot the same?

 

Environment

Release : 6.x

Component : DOLLAR UNIVERSE

Resolution

Below mentioned configurations are suggested to troubleshoot communication/data loss issue between DU and DUX.

• In node settings set logging - main log level: 0,IOSERV and save the updated setting. This configuration will write additional trace lines in universe.log
  

Administration -> Nodes -> Selected Node -> Node Settings -> Logging

          The additional traces in universe.log

|2021-09-27 03:49:02 |INFO |X|IO  |pid=p.t| o_refresh_log_level       | Log theme is: 0,IOSERV
| 2021-09-27 03:54:57 |TRACE|A|IO |pid=p.t| u_io_thread_trt           | Waiting for client 1844 authentication...
| 2021-09-27 03:54:57 |TRACE|A|IO |pid=p.t| u_io_thread_trt           | Waiting for client 1828 authentication...

| 2021-09-27 10:04:18 |TRACE|X|IO |pid=p.t| _rawdata_to_o_json        | Get data to send to DUA: (numlanc: 3585) => status: T
| 2021-09-27 10:04:29 |TRACE|X|IO |pid=p.t| trigger_sb                | SB trigger: set date (20380408000000) for LAN
| 2021-09-27 10:05:01 |TRACE|X|IO |pid=p.t| trigger_sb                | SB trigger: set date (20380408000000) for LAN
| 2021-09-27 10:05:33 |TRACE|X|IO |pid=p.t| trigger_sb                | SB trigger: set date (20380408000000) for LAN
| 2021-09-27 10:06:05 |TRACE|X|IO |pid=p.t| trigger_sb                | SB trigger: set date (20380408000000) for LAN
| 2021-09-27 10:06:09 |TRACE|X|IO |pid=p.t| u_io_thread_trt           | Waiting for client 300 authentication...

Note: As soon as the issue is reproduced, set back the main log level to 0 to stop tracing.

• Additionally, for troubleshooting DUX, we suggest to install in a chrome browser the extension Elasticsearch HEAD and then connect to the Elasticsearch URL of DUX ( in port 9200 by default). It let you explore the index  Job_v2 which has executions contained in the DUX database