" /> Somebody can tell me what is going on. - Genesys CTI User Forum

Author Topic: Somebody can tell me what is going on.  (Read 4292 times)

Sid

  • Guest
Somebody can tell me what is going on.
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hello everyone

Can somebody help me with this log?

------------------
@08:56:53.6173 [4521] New client 28 connected from 10.150.56.73
Tue Feb 04 08:56:53 2003.617 Trace puppis mpsc_tserver GCTI04521 New client 28 connected from 10.150.56.73
@08:56:53.6177
fatal: (client_create_internal) tab reuse 28: old 0x013f003b(Desktop Toolkit 5.1 OLE/COM)
<<< (ncosighnd) sig=00:6 level=1
+++ (ncohstvfy) ew/tw=6/7406 ct/thr=6/10 alw=44376
>>> (ncosighan) done 44376 [0000ad58]
@08:56:53.6181 [2024] Signal SIGABRT received
Tue Feb 04 08:56:53 2003.618 Standard puppis mpsc_tserver GCTI02024 OS signal SIGABRT received
>> (ncoexcall) ppid:pid=1:1804 level=1 done 29
Out of conn_main_loop:
4) Sync: socket=48761, remote=10.150.200.233:3086, RX=254968 TX=1676 qix-
7) SERVER: port=3000 q x
8) Async: socket=3000, remote=10.150.56.119:1067, RX=3727 TX=34987 q-x
9) Async: socket=3000, remote=10.150.156.22:1278, RX=1084448 TX=18165369 q-x
10) Async: socket=48770, remote=10.150.200.233:4999, RX=36 TX=253 qixc
11) Async: socket=48772, remote=128.1.154.37:3000, RX=112 TX=148 q-xcr
12) Async: socket=48773, remote=10.40.20.234:3000, RX=180813 TX=244269 q-xcr
13) Async: socket=3000, remote=10.150.56.36:1051, RX=1088 TX=8691 q-x
14) Async: socket=3000, remote=10.150.56.70:1068, RX=843 TX=4654 q-x
15) Async: socket=3000, remote=10.150.56.225:2073, RX=30235 TX=13780332 q-x
16) Async: socket=3000, remote=10.150.56.131:1294, RX=182 TX=4817 q-x
17) Async: socket=3000, remote=10.150.56.190:1065, RX=1860 TX=13619 q-x
18) Async: socket=3000, remote=10.150.92.239:4886, RX=6874 TX=23820 q-x
19) Async: socket=3000, remote=10.150.56.88:1061, RX=4227 TX=23140 q-x
20) Async: socket=3000, remote=10.150.56.132:1045, RX=1413 TX=5390 q-x
21) Async: socket=3000, remote=10.150.156.23:4179, RX=4339 TX=10540 q-x
22) Async: socket=3000, remote=10.150.156.17:1458, RX=696690 TX=3467539 q-x
23) Async: socket=3000, remote=10.150.156.16:1094, RX=139371 TX=1420836 q-x
24) Async: socket=3000, remote=10.150.156.13:1079, RX=698477 TX=3462035 q-x
25) Async: socket=3000, remote=10.150.156.14:1079, RX=736543 TX=3687336 q-x
26) Async: socket=3000, remote=10.150.200.233:48985, RX=31899 TX=13755022 q-x
27) Async: socket=3000, remote=10.150.156.23:4188, RX=4159 TX=7438 q-x
28) Async: socket=3000, remote=10.150.56.73:1045, RX=0 TX=0 q-x
29) Async: socket=51140, remote=129.1.1.1:5678, RX=10541273 TX=848210 q-xcr
30) SERVER: port=6203 q x
31) Async: socket=3000, remote=10.150.156.23:4189, RX=19333 TX=145659 q-x
32) Async: socket=3000, remote=10.150.156.21:2887, RX=19333 TX=253024 q-x
33) Async: socket=3000, remote=10.150.156.18:1262, RX=1068127 TX=5465941 q-x
34) Async: socket=3000, remote=10.150.156.19:1325, RX=1103538 TX=5611979 q-x
35) Async: socket=3000, remote=10.150.200.233:51220, RX=700303 TX=12786176 q-x
<< (ncoexcall) ct/thr=0/0 ppid:pid=1:1804 level=1
Tue Feb 04 08:56:53 2003.640 Trace puppis mpsc_tserver GCTI04541 Message RequestRegisterClient received from 28 ( N/A N/A )
@08:56:53.6412 [0] Received from 28: message RequestRegisterClient
AttributeProtocolVersion 'tserver protocol 4.2'
AttributeApplicationName 'Desktop Toolkit 5.1 OLE/COM'
Tue Feb 04 08:56:53 2003.641 Trace puppis mpsc_tserver GCTI04541 Message RequestRegisterClient received from 28 ( regular Desktop Toolkit 5.1 OLE/COM )
@08:56:53.6416 [0] Received from 28 (Desktop Toolkit 5.1 OLE/COM): message RequestRegisterClient
AttributeProtocolVersion 'tserver protocol 4.2'
AttributeApplicationName 'Desktop Toolkit 5.1 OLE/COM'
Tue Feb 04 08:56:53 2003.655 Trace puppis mpsc_tserver GCTI04541 Message RequestRegisterAddress received from 28 ( regular Desktop Toolkit 5.1 OLE/COM )
@08:56:53.6555 [0] Received from 28 (Desktop Toolkit 5.1 OLE/COM): message RequestRegisterAddress
AttributeThisDN '3591'
AttributeRegisterMode 0
AttributeControlMode 0
AttributeAddressType 1
AttributeReferenceID 1
g3_dn_info(3591)>flags=0x112
@08:56:53.6562 [0] 6.1.0033 send_to 0x013f003b: message EventRegistered

Vic

  • Guest
Somebody can tell me what is going on.
« Reply #1 on: January 01, 1970, 12:00:00 AM »
Can you please give us more info about what product it is, how you are using it and when and what is happening?


Marked as best answer by on July 02, 2018, 03:05:43 PM

VIP

  • Guest
Somebody can tell me what is going on.
« Reply #2 on: January 01, 1970, 12:00:00 AM »
Hi,
mostlikely TServer client (fd 28) had some connection problem in the past. The most recent reconnect caused TServer (G3 v. 6.1.0033 )to fail.Fortunately the TServer did not crash :)
Probably you would need to upgrade the TServer up to latest 6.5.
Anyway, I think it's reasonable to send the log to Genesys TechSupport for analysis.

Sid

  • Guest
Somebody can tell me what is going on.
« Reply #3 on: January 01, 1970, 12:00:00 AM »
Thanks. Basically that is the same Genesys tech support said.
The client that is creating problems is a call recording system. (Verint).

I am going to upgrade TServer and see what happens.


Offline hyetkin

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
Re: Somebody can tell me what is going on.
« Reply #4 on: November 21, 2007, 09:09:23 PM »
upgrade to 6.5 will solve problem