Brief lockout of ASE Server --missing parameters in error log

[james_morrison]

Hi

Last night user was locked out of ASE server (15.5 ESD 2) briely  -- Application Had following error:

DBError: [20011]: Maximum number of DBPROCESSes already allocated

Around the time the error was reported I noticed strange entry in ASE error log -- for about 1 minute the hour and minute entries were not written to log:

00:14:00000:06133:2015/07/16 20:52:40.83 kernel  Cannot read, host process disconnected: BT4-TRD-STC 00000123 spid: 6133

00:02:00000:06524:2015/07/16 20:52:40.84 kernel  Cannot read, host process disconnected: BT4-TRD-STC 00000123 spid: 6524

00:06:00000:09674:2015/07/16 :11.90 kernel  Cannot read, host process disconnected: APPW54-STC 00000123 spid: 9674

00:16:00000:07510:2015/07/16 :27.69 kernel  Cannot read, host process disconnected: APPW54-STC 00000123 spid: 7510

00:04:00000:01925:2015/07/16 :27.69 kernel  Cannot read, host process disconnected: APPW54-STC 00000123 spid: 1925

00:00:00000:00283:2015/07/16 :43.87 kernel  Cannot read, host process disconnected: appw54-stc  spid: 283

00:09:00000:05736:2015/07/16 :43.88 kernel  Cannot read, host process disconnected: appw54-stc  spid: 5736

00:20:00000:06548:2015/07/16 :43.92 kernel  Cannot read, host process disconnected: appw54-stc  spid: 6548

I have not seen that in log before ..

at time this happened there were number of maintenance actions running,..

any thoughts..?

Thanks

Jim

[james_morrison]

We had period earlier today where new login attempts were failing to connect to ASE --

Get errors like :

CT-LIBRARY error:

        ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

{dl2-trd-stc:GBL_TRD:sybase}

.  Connections already logged in were fine -- I was able to run sp_lock -- did not see anything out of ordinary -- master db looked ok -- no blocking.  Just before new logins were able to connect this was in log:

0:02:00000:00000:2015/07/23 11:07:14.02 kernel  nspacket: send, Connection reset by peer

00:04:00000:09227:2015/07/23 11:07:14.02 kernel  extended error information: hostname: GRNW7042 login: systudor

00:01:00000:03828:2015/07/23 11:07:14.06 server  Update of syslogins failed

00:21:00000:08814:2015/07/23 11:07:14.07 server  Update of syslogins failed

10 seconds after this new logins were able to get in ..

[jayrijnbergen]

Documented error, it's in the troubleshooting guide

The Backup Server runserver file, the interfaces file, and the sysservers table in the master database do not have a consistent name for the Backup Server.

or, more likely if it's an intermittent error

You have hit a network limit for the Backup Server process. Typically, this limit is set to 25.

Start Backup Server with the -Nnn flag to change the network limit. For example, -N30 increases the limit to 30.

[former_member188958]

Although this is an error reported by the Backup Server, it is not unique to it.  The error can be raised by any client built using Open Client DB-Library.   DB-Library has a default of 25 DBPROCESS structures, but can be configured for more.  It sounds as if your client exceeded it's current setting.

Details on this setting can be found in the

Software Developer's Kit 15.7 > Open Client DB-Library/C Reference Manual > Routines

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32600.1570/html/dblib/X42139.htm

Errors

The

dbopen call will return NULL if any of the following errors occur. These errors

can be trapped in the application’s error handler (installed with

dberrhandle.)

Error Condition/cause

-------

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

SYBEDBPS

Maximum number of DBPROCESSes already allocated.

Note that an application

can set or retrieve the maximum number of DBPROCESS structures with

dbsetmaxprocs and

dbgetmaxprocs

dbsetmaxprocs

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32600.1570/html/dblib/X47066.htm

Description:

Set the maximum number of simultaneously open DBPROCESS structures.

Syntax:

RETCODE dbsetmaxprocs(maxprocs)

int

maxprocs;

Parameters

maxprocs

The new limit on simultaneously open

DBPROCESS structures for this particular program.

Returns

SUCCEED or

FAIL.

Usage

A DB-Library program has a maximum number of

simultaneously open DBPROCESS structures. By default, this number is 25. The

program may change this limit by calling dbsetmaxprocs.

The program may

find out what the current limit is by calling dbgetmaxprocs.

The missing hour and minute fields in the errorlog are certainly strange, I have not seen that before.  It may or may not be related to the DBPROCESS error.

When you say there were a number of maintenance actions running, do you mean someone was running DBCCs, REORGS, or DUMPs, or was it that sp_who or sysprocesses showed some number of connections as "MAINTENANCE TOKEN"?  The later is often seen when a connection is early in the login process as it is the 0th element in an array of possible values and so shows up when the field is uninitialized.  In that case, I think it may be related as the client may be initiating a login but then hitting the DBPROCESS error and breaking the connection early in the process.

-bret