PureEngage On-Premises

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

ConfigServer Not starting in DRC Platfrom

  • 1.  ConfigServer Not starting in DRC Platfrom

    Posted 20 days ago
    Edited by Vikram Singh 19 days ago
    image

    I have a problem with the PDC and DRC platforms. During the switchover to the DRC platform, I am using the standby database (to use ConfigDB) and DNS switching to use the DRC config server. The recent issue observed was that I stopped the config server application in PDC and tried to start the config server in DRC, but I was not able to start the application in DRC due to the given error. However, tnsping to the database was OK, and the DNS switch also looked fine.

    02:26:37.793 cfg_refresh DB server connection established
    02:26:37.793 SERVER STATE: Generated refresh value is 21376214
    02:26:37.894 Std 22913 Configuration database version is [8.5]
    02:26:37.894 Std 22918 Configuration tenancy model is: [SINGLE-TENANT]
    suspend handling of DB events on dbserver_source_context level
    02:26:37.894 Database schema is reading ...
     done
    resume handling of DB events on dbserver_source_context level
    02:26:38.022 Std 22910 Database schema [dbschema.xml] is loaded
    Open LCALayer on port=4999
    LCA Library version 8.5.100.33
    02:26:38.295 Std 22500 LCA is configured at [framework-p-pdc.ph.prod:4999]
    ************************************
    LCALayer: REventRegistered on LCA...
    ************************************
    LCALayer: The local host is under control of Management Layer. SCS 'mng_scserver_b_drc' has connected to the LCA from the host '' on the socket 9.
    02:26:38.493 Std 22911 Backup server [confserv_Backup] on [framework-b-pdc.ph.prod:2020] is set up in the configuration
    02:26:38.493 Trc 04500 Connecting to ConfigurationServer '' at host 'framework-b-pdc.ph.prod', port 2020
    addp-trace off
    (addp_xconfig) local 30000 msec, remote 60000 msec, trace off
    02:26:38.496 Std 04502 Cannot connect to ConfigurationServer '' at host 'framework-b-pdc.ph.prod', port 2020, reason 'Server not found or Server is busy'
    SERVER STATE: probe connection to peer failed, continue initialization
    02:26:38.496 Total number of clients: 0
    02:26:38.496 Number of GUI clients: 0
    continue (re)loading data from DBServer: main connection, phase:[BACKUP_PORT_READ]
    02:26:38.497 Std 22902 Objectset [main-cfgset] : read requests sent on DBServer

    #Implementation

    #GenesysEngage

    #GenesysEngagePremDev


    #ArchitectureandDesign

    ------------------------------
    Vikram Singh
    -
    ------------------------------



Related Content