'lti' RepAgent USER sessions filling up limit of connections into RepServer

[Former Member]

Sometime, RepAgents are trying and trying to connect into RSSD . . .

Each new retry is opening a new USER Session and may gradually filling up the Limit of Sessions

When stopping the RepAgent's, no more 'lti' Sessions are opened but all accumulated Sessions are not closed.

We can find what is causing this ?

Sess attached document

  . . .

  240 USER   Awaiting Command     SRSSTA01_ra

my_document.txt.zip

[Former Member]

1. Observations
   ...

1
- ASE errorlog snippet shows repagents for 2 databases (dbid = 6 & 😎
retrying connection every 60 seconds; usually (but not always) there are
additional messages in the ASE errorlog indicating what problem the repagent is
having.

Are
there any other messages in the ASE errorlog prior to the snippet you've
posted?  [I'm looking for any/all messages that would indicate what
problem(s) these repagents are having.]

Are
any messages displayed when you run 'sp_start_rep_agent'?

As you indicate, I found some RepAgent
Connections stil trying to connect !!!

2
- RS errorlog snippet shows the SRSSTA01_ra user coming in from different
dataservers (eg, SYBDEV07, SYBSTA01, SYBRSS01).

Are you
really replicating from all of these dataservers? And is it your intention to
use the same repagent user account to connect to the same repserver (SRSSTA01)?
[While this is certainly doable it makes troubleshooting a bit more
complicated.]

Each RepAgent is connecting using
'SRSSTA01_ra' for each Primary Server|Database, where i prviously run 'rs_init'
with the same Login and Pw for every Primary Context !

I'm
wondering if some of the PDBs were dumped/loaded from another dataserver and
the repagents weren't (re)configured to point to the correct repserver and/or
use a different user account (or potentially the repagent wasn't disabled where
not needed.]

No !

3
- 'admin who' output usually shows a successful repagent login with a name of
'REP AGENT'

Your
multiple entries for name = 'USER' and Info = 'SRSSTA01_ra' would tend to
indicate these sessions are not recognized by the Repserver as valid repagent
logins.  What I can't tell at this point is if these are connections
coming from invalid/misconfigured repagents ... or if you've got other
processes (eg, monitoring processes) logging into the repserver with the SRSSTA01_ra
user account.

Are
you using the SRSSTA01_ra user account as your login for other processing (eg,
monitoring scripts)?

Usually
when I see a repagent with a problem connecting to the repserver I will see a)
the same/similar messages in the ASE errorlog (though there are usually
additional messaegs mentioning the actual problem) and b) no associated
connection in the repserver for said repagent.

The
fact that you have a lot of 'USER' connections using the 'SRSSTA01_ra' user
account would seem to indicate that you have some non-repagent processes
connecting to the repserver with the SRSSTA01_ra user account.

Personally
... I'd need to see more info, to include:

I do not use
'RSSSTA01_ra' from any 'isql' session

when i am
connecting to ASE|RSSD RepServer, i am using a
common dedicated User 'as_rep' wtih the same Pw everywhere and showing
User Sessions like in that example

     83
USER       Awaiting Command     as_rep

     84
USER       Active               as_rep

The   '297
USER       Awaiting
Command     SRSSTA01_ra'  cumulative connections  seem caused by uncompleted connections from
'active' RepAgent unable to successuflly connecting ! I have no idea how i
create this kind of situations ? ? ?

(You wil
find attached the full Sybase Audit Log ,just in case you could find something)

Please note.
. .at the moment,

All RepAgent
have been 'stopped' and changed to 'disable'

All Queues
have been cleaned and system became 'quiesced'

SRSSTA01  have been 'shutdown' and 'restarded' to
eliminate cumulative pending 'LTI USERS Connections'

Il thing
'disabling' RepAgent is making Information you request unavailable ?

1
- repserver version

1. I.
   2013/09/03 16:31:07. Server using Open Server version Sybase
   Server-Library/15.7/P-EBF20169-20168 ESD #2 ONE-OFF/DRV.15.7.0.2/SPARC/Solaris
   10 Native Threads/BUILD1570-016/64bit/OPT

/Fri
May  4 10:00:57 2012

1. I.
   2013/09/03 16:31:07. Server using Open Client version Sybase
   Client-Library/15.7/P-EBF20168 ESD #2 ONE-OFF/DRV.15.7.0.2/SPARC/Solaris 10
   Native Threads/BUILD1570-016/64bit/OPT/Fri M

ay  4 09:55:58 2012

1. I.
   2013/09/03 16:31:07. Server using Express Connect Library version Sybase
   ExpressConnect-Library/15.7.1/P/RCI 3.3/Sun_svr4/OS 5.8/1/OPT64/Sun May 13
   18:15:35 2012
2. I.
   2013/09/03 16:31:08. Server site id is '16777317'.

2
- entire output from 'sp_help_rep_agent' for each ASE dataserver attempting to
connect to the repserver (eg, SYBDEV07, SYBSTA01, SYBRSS01); check your
repserver errorlog for a complete list of ASEs as connection sources    attached

3
- the complete output from running 'admin who' attached

4
- all associated lines from the repserver and ASE errorlogs  attached

Alternatively
you could consider opening a case with Sybase tech support. (In theory there
could be a bug with your RS version that misallocates your repagent login as a
normal USER connection ... *shrug*)

We have
download Ebf 15.7.1 SP100 ... we will install it soon

20130903_log_info.txt.zip