topic Re: problem with running Sybase in Operating System - HP-UX

problem with running Sybase

mxshao — Wed, 21 Jun 2000 05:31:09 GMT

Hi,

I run Sybase 11 on a HP-UX 11.0 system, there always displays the following messages:
sample1: 00:00000:00000: 2000/06/16 10:41:39.17 kernel nrpacket:recv, connection timed out
sample2: 00:00000:00000: 2000/06/16 10:44:33.12 kernel cannot read, host process disconnected
sample3: 00:00000:00000: 2000/06/16 10:45:29.34 kernel cannot send, host process disconnected

These messages were written to Sybase's errorlog file too.

why they displayed? and how can I resolve them?

I am looking forward to any reply.

Thanks

Re: problem with running Sybase

Alex Glennie — Wed, 21 Jun 2000 06:45:52 GMT

Found following info on 10.20 sybase 11.5 : beleive it's still relevant :

The message is recorded on the CONSOLE and in the SQLServer Log file.
Kernel: nrpacket recv, connection timed out
Cannot read host process disconnected

messages are informational messages. This would come about when a
client PC is idle and times out, or the user may turn off the PC (not
exist gracefully from the PC app), or maybe the user Reboots the PC
(CntlAltDelete).

What happens is that the keepalive option of HPUX attempts to poll the
clients, and it sends a message. If no response the HPUX server knows
that the client is gone and it cleans up. In the case of Sybase, it
writes the message to the SQLServer log and the console for information
only. The HPUX keepalive option values can be looked at with the
following:

/usr/contrib/bin/nettune -l

The 3 parms: are: tcp_keepstart, tcp_keepfreq, tcp_keepstop
I am not absolutely sure, but the keepstart states how long to wait
from the beginning of the TCP idle to check the client. The system
will loop 10 times to determine if the client is there.

The bottom line, that if there are intermittent messages that this is not unexpected with Sybase, and the messages are just informational.

However it would be wise first to check you don't have any network problems and also to check /var/adm/syslog/syslog.log to be on the safe side.

Re: problem with running Sybase

Alex Glennie — Wed, 21 Jun 2000 06:46:23 GMT

Re: problem with running Sybase

Philip Chan_1 — Fri, 14 Jul 2000 05:25:28 GMT

That happens when a Sybase connection was terminated unexpectedly (without a proper logout), for example an user just power off the machine or his PC hung up completely.

These messages should be informational only and don't do any harm to the dataserver process.