HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- TCP_NODELAY error with Apache 2
Operating System - HP-UX
1830237
Members
13161
Online
109999
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
04-21-2005 03:07 AM
04-21-2005 03:07 AM
TCP_NODELAY error with Apache 2
I'm getting a new error on one of my 11.11 servers running Apache 2.0.51 now that I've put it in production. In the Apache error log, I'm seeing this:
[warn] (22)Invalid argument: apr_socket_opt_set: (TCP_NODELAY)
Definitely not for every hit, or even for most, but several per minute. This server is now serving production web traffic behind a Cisco content switch. I see the same error to a much lesser degree on my primary production server running 11.23. I can't say it's never happened before, but I hadn't seen it. To the best of my knowledge, it's not impacting user experience. Maybe it's nothing, but I'd like to know if anyone's seen it before and what it might mean.
[warn] (22)Invalid argument: apr_socket_opt_set: (TCP_NODELAY)
Definitely not for every hit, or even for most, but several per minute. This server is now serving production web traffic behind a Cisco content switch. I see the same error to a much lesser degree on my primary production server running 11.23. I can't say it's never happened before, but I hadn't seen it. To the best of my knowledge, it's not impacting user experience. Maybe it's nothing, but I'd like to know if anyone's seen it before and what it might mean.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2005 03:18 AM
04-21-2005 03:18 AM
Re: TCP_NODELAY error with Apache 2
I would look at network configuration.
Appears the switch may not be configured in a way the NIC on the server and all network services need.
I'd try carefully to correct this before it impacts user performance.
Also might want to see the Listen directive in http.conf, see that its on an ip address that always available and not failing over to another server with a serviceguard package.
SEP
Appears the switch may not be configured in a way the NIC on the server and all network services need.
I'd try carefully to correct this before it impacts user performance.
Also might want to see the Listen directive in http.conf, see that its on an ip address that always available and not failing over to another server with a serviceguard package.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2005 03:58 AM
04-21-2005 03:58 AM
Re: TCP_NODELAY error with Apache 2
EINVAL when trying to set TCP_NODELAY option usually means that the connection
to the client has been lost.
to the client has been lost.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2005 07:36 AM
04-22-2005 07:36 AM
Re: TCP_NODELAY error with Apache 2
In addition to the possiblilty that the remote has closed the connection, you might want to tusc one or more of the httpd's and see if perhaps sometimes one of the arguments to the setsockopt() is getting botched.
IIRC TCP_NODELAY is one of the settings inherited across an accept() call, so if TCP_NODELAY is (for whatver reason) being set on every connection, there is a possible enhancement right there.
IIRC TCP_NODELAY is one of the settings inherited across an accept() call, so if TCP_NODELAY is (for whatver reason) being set on every connection, there is a possible enhancement right there.
there is no rest for the wicked yet the virtuous have no pillows
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