SOP for Restart required in Websub in need basis in order to get the Print transaction flow continuously.

Owned by Chandra Keshav Mishra, created
Oct 27, 2021
1 min read

As of now we don't have persistence there in Websub and healthcheck URL so, due to this in between Websub stops responding to credentials issued by idrepo and hence Print records will not go after that.
So In order to keep the print records transaction coming continuously we need to follow below steps in every 2 to 3 hours:

 Instructions

Below are the steps to check and ensure Print records are going..

  1. check in websub DB subscription table if we have an entry for msp-printers.
    Query: select * from subscription

     

  2. If entry for msp-printer is there than it is fine.. though you can cross verify the same by checking in CPMS DB.

  3. If entry is not there in websub subscription table then we need to restart the websub pod there in dmz cluster using below command:
    kc2 delete pod <websub pod name>

  4. Once restarted check for step 1 and 2 once again.

Highlight important information in a panel like this one. To edit this panel's color or style, select one of the options in the menu.