Stack Trace dbg_dump_stack

[james_morrison]

Hi --

We are running Rep Server 15.7.1/EBF 25284 SP210

When attempting to suspend route we had error 4078 followed by stack trace  and server shutdown: 

We were attempting to change rsi configuration settings

I. 2016/06/01 17:28:51. RSI for 'GBL_RS_LON103': Waiting response from the RSI receiver.

E. 2016/06/01 17:28:52. ERROR #4078 RSI(GBL_RS_LON103) - generic/rsi/rsiint.c(2400)

        Unexpected return value '-202' from ct_results. Please check log for error messages from CT-Lib.

E. 2016/06/01 17:28:52. ERROR #4044 RSI(GBL_RS_LON103) - generic/rsi/rsiint.c(341)

        RSI for 'GBL_RS_LON103': Shutting down due to an exception.

I. 2016/06/01 17:29:03. RSI: Trying to connect to 'GBL_RS_LON103'.

I. 2016/06/01 17:29:04. RSI: connection to 'GBL_RS_LON103' is established and the route is active.

T. 2016/06/01 17:29:04. (256): Thread RSI(GBL_RS_LON103) infected with signal 11.

T. 2016/06/01 17:29:04. (256): Dumping memory trace.

T. 2016/06/01 17:29:04. (256): ***************STACK TRACE***************

T. 2016/06/01 17:29:04. (256): *****thread RSI(GBL_RS_LON103)*******

T. 2016/06/01 17:29:04. (256):  pc: 0x0000000000861bbc + 00000000000000e3, dbg_dump_stack ()

T. 2016/06/01 17:29:04. (256): *****End of stack trace.****

T. 2016/06/01 17:29:04. (256): Internal error. Attempting to produce a core file.

Server was restarted and all routes /connections came up without errors

Checking knowledge base saw note referring to CR  784995

No fix identified yet

Can I find any more description of this CR /bug ..

Any insight into initial Error 4078 ?

Thanks

Jim

[james_morrison]

Source :

admin version

2> go

Version                                                                                                                           

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

Replication Server/15.7.1/EBF 25284 SP210 rs1571sp210/Linux AMD64/Linux 2.6.18-128.el5 x86_64/2089/OPT64/Tue Feb 23 10:57:16 2016

1> admin show_route_versions

2> go

Source RepServer               Dest. RepServer                Route Version

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

GBL_RS_GRN19                   GBL_RS_GRN9                          1571207

GBL_RS_GRN19                   GBL_RS_GRN_SYP                       1571207

GBL_RS_GRN19                   GBL_RS_GRN2                          1571207

GBL_RS_GRN19                   GBL_RS_LON103                        1571207

Target:

Replication Server/15.7.1/EBF 25284 SP210 rs1571sp210/Linux AMD64/Linux 2.6.18-128.el5 x86_64/2089/OPT64/Tue Feb 23 10:57:16 2016

Source RepServer               Dest. RepServer                Route Version

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

GBL_RS_GRN19                   GBL_RS_LON103                        1571207

GBL_RS_LON103                  GBL_RS_LON302                        1571207

GBL_RS_LON103                  GBL_RS_LON203                        1571207

[Mark_A_Parsons]

Thanks.

I was looking for potential issues between different RS versions, but that's not an issue here.

Another shot in the dark ... can you verify the RSSD was not shutdown/taken-offline while one of the repservers (source/target of route) were still running? [I'm working at a client where they've routinely bounced the ASE/RSSD without shutting down the RS ... causes lots of oddball problems when the RSSD is yanked out from under the RS!]

[james_morrison]

The RSSD was up during this time. We did open a case and  SAP initial response linked it to CR 784995