From: "H. Willstrand" <h.willstrand@gmail.com>
To: "M. Istehbab" <hariskhan@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: TCP connection failure in kernel 2.6.25
Date: Sat, 26 Apr 2008 22:27:04 +0200 [thread overview]
Message-ID: <1209241624.2929.17.camel@localhost.localdomain> (raw)
In-Reply-To: <c1410bfe0804260516k1149fadaoc06f02b94dcd12e9@mail.gmail.com>
On Sat, 2008-04-26 at 17:16 +0500, M. Istehbab wrote:
> Yes, after a while (it can be a few seconds, minutes, or 1+ hour) the
> proxy server starts accepting connections again. I don't need to
> reboot the box when this happens.
>
> This happens randomely to anyone behind it. Then, after a while, it
> starts working again by itself.
>
Well, there are too many possibilities for failures... the Linux
distribution (RHEL 3 workstation) was built for 2.4.21 (around year
2003) and you try 2.6.x
Maybe you should stick to one of the later 2.4.x kernels or even better
upgrade the Linux distribution.
Cheers,
H. Willstrand
> M. Istehbab
>
> On 4/26/08, H. Willstrand <h.willstrand@gmail.com> wrote:
> >
> > >
> >
> > Is the proxy server accepting connections after the issue has occurred?
> > Or do you need to re-boot? Or do you have to wait for a number of
> > seconds or what?
> >
> > Cheers,
> > H. Willstrand
> >
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-04-26 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 9:17 TCP connection failure in kernel 2.6.25 M. Istehbab
2008-04-26 10:18 ` H. Willstrand
2008-04-26 12:16 ` M. Istehbab
2008-04-26 20:27 ` H. Willstrand [this message]
2008-04-27 6:02 ` M. Istehbab
2008-04-27 16:56 ` H. Willstrand
2008-05-08 19:32 ` M. Istehbab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1209241624.2929.17.camel@localhost.localdomain \
--to=h.willstrand@gmail.com \
--cc=hariskhan@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox