PureEngage On-Premises

Discussion Thread View
Expand all | Collapse all

Steps to reboot Config Server

  • 1.  Steps to reboot Config Server

    Posted 10-31-2019 00:20
    Hi,
    Can someone please share the proper process or steps to reboot Config Server?

    I would greatly appreciate it.

    Thanks!
    #PlatformAdministration

    ------------------------------
    Maryam

    ------------------------------


  • 2.  RE: Steps to reboot Config Server

    Posted 11-02-2019 02:34
    Hi,

    From GAX/GA/SCI you can stop the primary node , wait for 3-5 minutes till backup node get running in primary state.

    or using command line (which i don't prefer)
    Windows - search for task using Task Manager then kill it
    Linux - type below commands which also going to kill your process

    ps -ef|grep confsrv -- this will print the confsrv process id (PID)
    kill -9 (PID)       -- kill the process with no mercy :)
    ​


    ------------------------------
    Mohammed Adel
    IST Networks - Saudi Arabia
    ------------------------------



  • 3.  RE: Steps to reboot Config Server

    GENESYS
    Posted 11-04-2019 02:38

    Hello Maryam,

    I have mentioned below the best practice for Warm and Cold reboot of Config Server to avoid synchronization issues during the switch over.
    Warm Reboot:
    1. Stop CS-P (in Primary mode) via SCI/GA/GAX/Host Services. CS-B (in Backup mode) should be taking over as Primary after reading the History Log details from the Config DB written by the CS-P before shutdown.

    2. Wait for the CS-B to fully initialize as Primary. The below message will be printed in the CS-B log when it is fully initialized as primary.

    11:49:16.610 Std 22171 Master Configuration Server is fully operational in primary mode

    3. Start the CS-P via SCI/GA/GAX/Host Services. Now the CS-P should be starting up in Backup mode.

    4. Wait for CS-P to fully synchronize as Backup CS. You will see the below message in the log.

    11:27:40.068 Std 22172 Master Configuration Server is fully syncronized in backup mode

    5. A complete CS-P restart is now done. If you wish to restart CS-B as well, follow steps 1-3 for CS-B.


    Cold Restart:
    1. Stop CS-B running in Backup mode via SCI/GA/GAX/Host-Services.

    2. Ensure the below trace event is printed in the CS-B log. This is to confirm that the CS-B is fully stopped.

    12:21:39.049 Trc 04109 Logging service stopped

    3. Now restart CS-P.

    4. Wait for the CS-P logs to print the below message indicating it is fully synchronized as Primary.

    11:49:16.610 Std 22171 Master Configuration Server is fully operational in primary mode

    5. Start up CS-B.



    ------------------------------
    Vinod Balan
    Genesys - Employees
    ------------------------------