Genesys Engage on-premises

 View Only

Discussion Thread View
  • 1.  Config server not able to connect to DB server

    Posted 12-20-2020 07:40

    we are facing an issue where config server is not able to connect to DB server on the 4040 port. when we are starting the config server the default port 8888(configured for config server ) is not openining.

    Config server logs:

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

    (addp_xconfig) local 11000 msec, remote 11000 msec, trace local
    05:58:23.681 dbserver_manager with alias main-dbserver has being registered for the socket 7, reference counter 3
    05:58:23.681 Trc 04500 Connecting to DBServer '' at host 'dev2-win-ctc-dBServer1.ms.ds.uhc.com', port 4040
    05:58:23.686 dbserver_manager with alias main-dbserver is about to unregister form socket 7, reference counter 3 (reason - exception)
    05:58:23.686 Std 04502 Cannot connect to DBServer 'DBServer' at host 'dev2-win-ctc-dBServer1.ms.ds.uhc.com', port 4040, reason 'Server not found'
    addp-trace on

    $ sudo netstat -ntpl
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 127.0.0.1:40523 0.0.0.0:* LISTEN 1823/ovcd
    tcp 0 0 0.0.0.0:5227 0.0.0.0:* LISTEN 1833/perfd
    tcp 0 0 127.0.0.1:36496 0.0.0.0:* LISTEN 2716/opcle
    tcp 0 0 127.0.0.1:50000 0.0.0.0:* LISTEN 1246/oneagentwatchd
    tcp 0 0 0.0.0.0:24146 0.0.0.0:* LISTEN 1413/xinetd
    tcp 0 0 0.0.0.0:47860 0.0.0.0:* LISTEN 2061/genesys.d
    tcp 0 0 0.0.0.0:43221 0.0.0.0:* LISTEN 2579/hpsensor
    tcp 0 0 127.0.0.1:38646 0.0.0.0:* LISTEN 2069/oacore
    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1235/sshd
    tcp 0 0 127.0.0.1:41817 0.0.0.0:* LISTEN 2069/oacore
    tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1785/master
    tcp 0 0 127.0.0.1:41788 0.0.0.0:* LISTEN 2635/opcacta
    tcp 0 0 127.0.0.1:38908 0.0.0.0:* LISTEN 2635/opcacta
    tcp 0 0 127.0.0.1:46268 0.0.0.0:* LISTEN 2587/opcmsga
    tcp 0 0 0.0.0.0:7260 0.0.0.0:* LISTEN 2055/./lmgrd
    tcp 0 0 127.0.0.1:39005 0.0.0.0:* LISTEN 2698/opcmsgi
    tcp 0 0 127.0.0.1:381 0.0.0.0:* LISTEN 2069/oacore
    tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN 2116/csshst
    tcp 0 0 0.0.0.0:383 0.0.0.0:* LISTEN 1939/ovbbccb
    tcp 0 0 127.0.0.1:32865 0.0.0.0:* LISTEN 2707/opcmona
    tcp 0 0 127.0.0.1:42755 0.0.0.0:* LISTEN 1823/ovcd
    tcp 0 0 127.0.0.1:41700 0.0.0.0:* LISTEN 2587/opcmsga
    tcp 0 0 127.0.0.1:57540 0.0.0.0:* LISTEN 1803/ttd
    tcp 0 0 0.0.0.0:4999 0.0.0.0:* LISTEN 3360/lca
    tcp 0 0 127.0.0.1:35463 0.0.0.0:* LISTEN 2330/ovconfd
    tcp 0 0 127.0.0.1:45513 0.0.0.0:* LISTEN 2069/oacore
    tcp 0 0 127.0.0.1:40041 0.0.0.0:* LISTEN 2069/oacore

    DB Server

    =========

    C:\Windows\system32>netstat -abno | find "8888"
    TCP 10.204.74.210:60684 10.204.108.211:8888 SYN_SENT 4340
    TCP 10.204.74.210:60685 10.204.102.210:8888 SYN_SENT 1268
    TCP 10.204.74.210:60686 10.204.102.210:8888 SYN_SENT 1676

    Db server is up and running but not writing anything in logs , verified the confserv.conf , everything is identical but still the issue persists.

    Can someone please help with this.

    Thank You,


    #Unsure/Other

    ------------------------------
    Nitin Turankar

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


  • 2.  RE: Config server not able to connect to DB server

    Posted 12-20-2020 12:18

    Issue resolved after re installation of DB server



    ------------------------------
    Nitin Turankar
    Optum Technology, Inc
    ------------------------------



Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources