Archive of UserLand's first discussion group, started October 5, 1998.
inetd events gone bad...
Author: Posted: 4/29/1999; 4:30:31 PM Topic: inetd events gone bad... Msg #: 5429 Prev/Next: 5428 / 5430
Any idea on what's happening here?4:11:49PM client = 206.173.113.140 port = 80 stream = 6 whatWentWrong = The connection timed out before the pattern was found. whatWereWeDoing = Calling the daemonMy server is a PowerMac G3 300 MHz. Frontier v6 Mac OS v8.14:09:51PM client = 206.173.113.140 port = 80 stream = 7 whatWentWrong = Can't write stream because TCP/IP error code 57 - Socket is not connected. whatWereWeDoing = Returning data
4:09:20PM client = 206.173.113.140 port = 80 stream = 6 whatWentWrong = Can't write stream because TCP/IP error code 57 - Socket is not connected. whatWereWeDoing = Returning data
2:15:44PM client = 205.188.209.74 port = 80 stream = 6 whatWentWrong = The connection timed out before the pattern was found. whatWereWeDoing = Calling the daemon
2:15:13PM client = 205.188.209.74 port = 80 stream = 6 whatWentWrong = The connection timed out before the pattern was found. whatWereWeDoing = Calling the daemon
I've noticed these errors in the inetd log. One person told me they couldn't connect to my server. I can see evidence that others are able to connect so it's not that no one can connect.
If there is something I can tweak on my end, please let me know. I can attempt to get more details if needed. Point me in the right direction and I'll dig! :-)
Thanks for any pointers...
Toodle-looooooo..... Thomas
There are responses to this message:
- Re: inetd events gone bad..., Dave Winer, 4/29/1999; 4:38:50 PM
This page was archived on 6/13/2001; 4:49:38 PM.
© Copyright 1998-2001 UserLand Software, Inc.