Genesys CTI 7.6 continues Outage

[Mokawanep@gmail.com]

Our Genesys CTI is using the WLBS cluster utility programs and its running on windows server. we are experiencing more outages when a switch over takes place. lately the SIP_wlbs_primary_exe and
SIP_wlbs_backup_exe are both stopping causing the system outage. what can be the root cause of this.

[Kubig]

And manually running of these script ends how, with success? You have to check logs the order in which the scripts were started and if ends with success. Whole funcionality of HA within Windows cluster depends on your script and cluster configuration. So, without logs and any deep description nobody helps you

[Mokawanep@gmail.com]

which logs can i analysis to see the problem.

[Mokawanep@gmail.com]

manual running of the cluster service works but.the problem is that it need manual intervension..

This is the logs from the wlbs
2013-09-17 04:29:08,500 DEBUG -  Checking if process "Sip_server" is running : True
2013-09-17 04:29:08,500 DEBUG -  Trying to execute: "wlbs queryport 5060 192.168.30.44:1"
2013-09-17 04:29:08,516 DEBUG -  Checking if port 5060 is directed to Host#1 in the cluster "192.168.30.44" : True
2013-09-17 04:29:08,516 DEBUG -  Check ok : looping
2013-09-17 04:29:10,516 DEBUG -  Checking if process "Sip_server" is running : True
2013-09-17 04:29:10,516 DEBUG -  Trying to execute: "wlbs queryport 5060 192.168.30.44:1"
2013-09-17 04:29:10,532 DEBUG -  Checking if port 5060 is directed to Host#1 in the cluster "192.168.30.44" : True
2013-09-17 04:29:10,532 DEBUG -  Check ok : looping
2013-09-17 04:29:12,532 DEBUG -  Checking if process "Sip_server" is running : True
2013-09-17 04:29:12,532 DEBUG -  Trying to execute: "wlbs queryport 5060 192.168.30.44:1"
2013-09-17 04:29:12,547 DEBUG -  Checking if port 5060 is directed to Host#1 in the cluster "192.168.30.44" : True
2013-09-17 04:29:12,547 DEBUG -  Check ok : looping
2013-09-17 04:29:14,547 DEBUG -  Checking if process "Sip_server" is running : True
2013-09-17 04:29:14,547 DEBUG -  Trying to execute: "wlbs queryport 5060 192.168.30.44:1"
2013-09-17 04:29:25,610 DEBUG -  Checking if port 5060 is directed to Host#1 in the cluster "192.168.30.44" : False
2013-09-17 04:29:25,610 INFO  - Killing Sip_server because not in cluster anymore
2013-09-17 04:29:25,610 DEBUG -  Killing process Sip_server
2013-09-17 04:29:25,735 WARN  -  Processus already Stopped : Process was not started by this object, so requested information cannot be determined.
2013-09-17 04:29:25,735 INFO  - Exiting Program

[Kubig]

As I wrote it always depends on your script.Chech LCA logs on specified host, if the script was running with right parameters and in right order. If your script needs manually input, they are not developed. And it cannot works properly. Did you read and check deployment guide as well?

[Mokawanep@gmail.com]

[log]
verbose = all
all = stdout, C:\GCTI\log\lca\lca
expire = 10
segment = 10000


LCA logs
01:15:45.375 Trc 04120 Check point 2013-09-17T01:15:45
02:15:45.391 Trc 04120 Check point 2013-09-17T02:15:45
03:15:45.407 Trc 04120 Check point 2013-09-17T03:15:45
04:15:45.422 Trc 04120 Check point 2013-09-17T04:15:45
04:29:25 LCA: handleClientException fd=964
04:29:25 App<115, SIP, pid=3264> disconnected.
04:29:25 Notify STATUS: App<115, SIP, pid=3264, APP_STATUS_STOPPED, PRIMARY.
04:29:25 #### OS Level STOPPED: App<147, SIP_WLBS_Primary_EXE, pid=2416>
04:29:25 Notify STATUS: App<147, SIP_WLBS_Primary_EXE, pid=2416, APP_STATUS_STOPPED, PRIMARY.
04:29:25 ~Application<2416, SIP_WLBS_Primary_EXE>
04:29:25 SCS: 04:29:25 [RequestAppStatus] on App 'SIP_WLBS_Primary_EXE' <pid=2416, dbid=147>
04:29:26 original cmdline: -host srv-gbcti01 -port 2020 -app SIP -service TSrvSIP -l 7260@srv-gbcti01;7260@srv-gbcti04
04:29:26 after cut cmdline: -service TSrvSIP -l 7260@srv-gbcti01;7260@srv-gbcti04
04:29:26 Generated CmdParams='-service TSrvSIP -l 7260@srv-gbcti01;7260@srv-gbcti04 -app "SIP" -host srv-gbcti01 -port 2020'
04:29:26
Command  = sip_server.exe -service TSrvSIP -l 7260@srv-gbcti01;7260@srv-gbcti04 -app "SIP" -host srv-gbcti01 -port 2020 -sstart
04:29:26 Arguments = -service TSrvSIP -l 7260@srv-gbcti01;7260@srv-gbcti04 -app "SIP" -host srv-gbcti01 -port 2020
04:29:26 Workdir  = C:\GCTI\SIP
04:29:26 App<115, SIP, pid=5436) RESTARTED.
04:29:26 DEBUG: SetSetCheckStartupTimer #429916170 on 90 sec.
04:29:26 Notify STATUS: App<115, SIP, pid=5436, APP_STATUS_START_PENDING, PRIMARY.
04:29:26 Client: new client 964 connected, 04:29:26 host srv-gbcti02 (192.168.30.38)
04:29:26 [RRequestRegisterApplication] App<115, SIP, pid=4464>
04:29:26 Found by AppID=115
04:29:26 ~Application<5436, SIP>
04:29:26 CREATE Application <115, SIP, pid=4464, socket=964, confserv=:>.
04:29:26 Notify STATUS: App<115, SIP, pid=4464, APP_STATUS_INITIALIZING, BACKUP.
04:29:26 [RequestAppLiveStatusChanged from APP <115, SIP, pid=4464, APP_STATUS_INITIALIZING, BACKUP> to <APP_STATUS_SERVICE_UNAVAILABLE, BACKUP>
04:29:26 Notify STATUS: App<115, SIP, pid=4464, APP_STATUS_SERVICE_UNAVAILABLE, BACKUP.
04:29:26 [RequestAppLiveStatusChanged from APP <115, SIP, pid=4464, APP_STATUS_SERVICE_UNAVAILABLE, BACKUP> to <APP_STATUS_RUNNING, BACKUP>
04:29:26 Notify STATUS: App<115, SIP, pid=4464, APP_STATUS_RUNNING, BACKUP.
04:29:26 SCS: 04:29:26 [RequestAppStartupInfoChanged] on App 'SIP' <pid=4464, dbid=115>
04:29:26 .... ConfServ<'srv-gbcti01':'2020'> changed for App{'SIP',pid=4464}
04:29:28 SCS_bkp: 04:29:28 [RequestAppStatus] on App 'SIP_WLBS_Primary_EXE' <pid=2416, dbid=147>
05:15:45.438 Trc 04120 Check point 2013-09-17T05:15:45
06:15:45.453 Trc 04120 Check point 2013-09-17T06:15:45

[Mokawanep@gmail.com]

thanks very much go through the deployment guide carefully