- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: problem with running Sybase
Operating System - HP-UX
1753873
Members
7320
Online
108809
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2000 10:31 PM
тАО06-20-2000 10:31 PM
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
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
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2000 11:45 PM
тАО06-20-2000 11:45 PM
Solution
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2000 11:46 PM
тАО06-20-2000 11:46 PM
Re: problem with running Sybase
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2000 10:25 PM
тАО07-13-2000 10:25 PM
Re: problem with running Sybase
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.
These messages should be informational only and don't do any harm to the dataserver process.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP