Wasp probe of OC return error "(1) error, Received status (1) on response (for sendRcv) for cmd = 'subscribe' "
search cancel

Wasp probe of OC return error "(1) error, Received status (1) on response (for sendRcv) for cmd = 'subscribe' "

book

Article ID: 251784

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Wasp probe of OC takes a long time to start and shows the below errors in wasp.log

Oct 10 18:36:15:110 ERROR [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] subscribe error: Received status (1) on response (for sendRcv) for cmd = 'subscribe' 
Oct 10 18:36:15:110 ERROR [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] (1) error, Received status (1) on response (for sendRcv) for cmd = 'subscribe' 

 

Environment

Release : All UIM supported versions

Cause

In a load balanced environment with multiple policy_management_ws nodes, the policy_processing should happen in a HA mode. 

webapps/adminconsoleapp/custom/uncrypted/ha_mode should be set to HA and all the policy_management_ws nodes should not have policy_processing flag. Then, nodes will be selected

dynamically and work in HA mode.

Resolution

Part 1 wasp probe of primary hub

 

  1. Via IM or AC
  2. Select the primary hub then raw configure wasp probe 
  3. Verify the following are set under webapps/adminconsoleapp/custom/uncrypted  (case sensitive)

ha_mode = HA
heartbeat_interval_min = 5
no_failed_attempts = 3

 

 

Part2: wasp probe of each OC 

Do the following on each OC robot:

  1. Via Im or AC
  2. raw configure wasp
  3. add the following key under webapps/policy_management_ws/custom/uncrypted

controller_url = http(s)://<system.domain_name>/adminconsoleapp/

where system.domain.name is the primary hub  (e.g. the same URL you use to access admin console).

 delete the policy_processing key if it is present in webapps/policy_management_ws/custom/uncrypted

Monitor the wasp.log for both OCs and you will notice the below message in the node that handles the policy processing

Oct 10 18:39:30:526 WARN  [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] Establishing connection to queue 'MCS_Profile_Event'. 
Oct 10 18:39:30:526 INFO  [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] subscribe policy_management to subject: MCS_Profile_Event 

Additional Information

Policy Management in High Availability Mode