Bug #1200
closed(network_solaris_sendfilev.c.104) writev failed: Transport endpoint is not connected 894
Description
I have 4 lighttpds which serve as proxy to tomcat5 (and do some other things - generally ~250 requests per second). Very rarely, a few times a day I get following errors on each of them:
<snip> 2007-05-25 05:34:37: (network_solaris_sendfilev.c.104) writev failed: Transport endpoint is not connected 38 2007-05-25 05:34:37: (mod_proxy.c.824) write failed: Transport endpoint is not connected 134 2007-05-25 05:34:37: (mod_proxy.c.911) proxy-server disabled: 10.1.7.11 9080 38 2007-05-25 05:34:37: (mod_proxy.c.1249) no proxy-handler found for: /interface/page1.jsp 2007-05-25 05:34:42: (mod_proxy.c.1294) proxy - re-enabled: 10.1.7.11 9080 </snip>
<snip> 2007-05-25 07:34:49: (network_solaris_sendfilev.c.104) writev failed: Transport endpoint is not connected 85 2007-05-25 07:34:49: (mod_proxy.c.824) write failed: Transport endpoint is not connected 134 2007-05-25 07:34:49: (mod_proxy.c.911) proxy-server disabled: 10.1.7.11 9080 85 2007-05-25 07:34:49: (mod_proxy.c.1249) no proxy-handler found for: /AdminEye/graph 2007-05-25 07:34:50: (mod_proxy.c.1249) no proxy-handler found for: /AdminEye/graph </snip>
It happens only when light is trying to forward request to tomcat (and 99.99% of communication is OK).
Some useful data:
$uname -X System = SunOS Release = 5.10 KernelID = Generic_118844-19 Machine = i86pc BusType = <unknown> Serial = <unknown> Users = <unknown> OEM# = 0 Origin# = 1 NumCPU = 4
$./bin/lighttpd -V lighttpd-1.4.13 (ssl) - a light and fast webserver Build-Date: May 14 2007 15:18:02 Event Handlers: + select (generic) + poll (Unix) - rt-signals (Linux 2.4+) - epoll (Linux 2.6) + /dev/poll (Solaris) - kqueue (FreeBSD) Network handler: + sendfile Features: - IPv6 support + zlib support + bzip2 support + crypt support + SSL Support + PCRE support - mySQL support - LDAP support - memcached support - FAM support - LUA support - xml support - SQLite support - GDBM support
-- Janek
Updated by Anonymous about 17 years ago
I'll second the problem. I am using lighttpd as frontend server for a reverse squid. The goal is to distribute the requests between several servers. In the setup lighttpd distributes the request to a single squid server.
2008-02-13 10:45:20: (network_solaris_sendfilev.c.104) writev failed: Transport endpoint is not connected 9 2008-02-13 10:45:20: (mod_proxy.c.825) write failed: Transport endpoint is not connected 134 2008-02-13 10:45:20: (mod_proxy.c.912) proxy-server disabled: 10.65.33.97 8080 9 2008-02-13 10:45:20: (mod_proxy.c.1250) no proxy-handler found for: /KURANGA/images/DetailsView.jpg 2008-02-13 10:45:20: (mod_proxy.c.1250) no proxy-handler found for: /KURANGA/images/RecordInfo.jpg 2008-02-13 10:45:46: (mod_proxy.c.1295) proxy - re-enabled: 10.65.33.97 8080
some more information:
bash-2.05# uname -X
System = SunOS
Node = cms-migration
Release = 5.9
KernelID = Generic_122300-10
Machine = sun4u
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 8
lighttpd-1.4.15 (ssl) - a light and fast webserver Build-Date: May 7 2007 18:18:53 Event Handlers: + select (generic) + poll (Unix) - rt-signals (Linux 2.4+) - epoll (Linux 2.6) + /dev/poll (Solaris) - kqueue (FreeBSD) Network handler: + sendfile Features: + IPv6 support + zlib support + bzip2 support + crypt support + SSL Support + PCRE support - mySQL support - LDAP support - memcached support - FAM support - LUA support - xml support - SQLite support - GDBM support
is there any progress on the report so far?
Regards
Uli
-- rhaen
Updated by rhaen about 17 years ago
just updated to 1.4.18 today - the bug still exists.
lighttpd-1.4.18 (ssl) - a light and fast webserver Build-Date: Feb 12 2008 02:03:46 Event Handlers: + select (generic) + poll (Unix) - rt-signals (Linux 2.4+) - epoll (Linux 2.6) + /dev/poll (Solaris) - kqueue (FreeBSD) Network handler: + sendfile Features: + IPv6 support + zlib support + bzip2 support + crypt support + SSL Support + PCRE support - mySQL support - LDAP support - memcached support - FAM support - LUA support - xml support - SQLite support - GDBM support
Updated by stbuehler over 16 years ago
- Status changed from New to Invalid
- Patch available set to No
I don't know how that could be lightys fault. if tomcat drops the connection, that should be ok to log imho.
Also available in: Atom