HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Sybase error: "kernel nrpacket: recv, Connection t...
Operating System - HP-UX
1829615
Members
1995
Online
109992
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
09-14-2001 01:41 PM
09-14-2001 01:41 PM
Sybase error: "kernel nrpacket: recv, Connection time out"
Hello,
The Sybase logs show me the next message:
"kernel nrpacket: recv, Connection time out"
My system is HP-UX 10.20 /s800.
I'm looking for information to resolve this problem.
Thanks in advance.
Marco.
The Sybase logs show me the next message:
"kernel nrpacket: recv, Connection time out"
My system is HP-UX 10.20 /s800.
I'm looking for information to resolve this problem.
Thanks in advance.
Marco.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2001 08:59 PM
09-14-2001 08:59 PM
Re: Sybase error: "kernel nrpacket: recv, Connection time out"
Hi Marco,
I found an FAQ for Sybase at http://www.isug.com/Sybase_FAQ/ASE/Section10/3/Q10.3.4.html, it contained the following information;
--qoute
Explanation of "nrpacket: recv, Connection timed out"
Question
I occasionally see the following message in my error log:
nrpacket: recv, Connection timed out.
What does it mean?
Answer
This is an OS error message. It is raised when SQL Server calls the recv function, but the connection has failed either before or during the recv function. It is not a SQL Server error; SQL Server merely reports it.
Explanation
There are a few reasons why the connection might have failed:
The client exited without going through a disconnect, as when someone switches off their PC. (This is the most likely cause.)
The network is extremely busy and is dropping packets.
KEEPALIVE is disabled for the OS, so TCP/IP times out the connection when the client has been idle for some time.
--end quote
Could be a client abnormally exited their session.
Hope this helps
-denver
I found an FAQ for Sybase at http://www.isug.com/Sybase_FAQ/ASE/Section10/3/Q10.3.4.html, it contained the following information;
--qoute
Explanation of "nrpacket: recv, Connection timed out"
Question
I occasionally see the following message in my error log:
nrpacket: recv, Connection timed out.
What does it mean?
Answer
This is an OS error message. It is raised when SQL Server calls the recv function, but the connection has failed either before or during the recv function. It is not a SQL Server error; SQL Server merely reports it.
Explanation
There are a few reasons why the connection might have failed:
The client exited without going through a disconnect, as when someone switches off their PC. (This is the most likely cause.)
The network is extremely busy and is dropping packets.
KEEPALIVE is disabled for the OS, so TCP/IP times out the connection when the client has been idle for some time.
--end quote
Could be a client abnormally exited their session.
Hope this helps
-denver
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP