On Wed, 18 Jun 2008 15:31:49 -0400
Bill Moran <[EMAIL PROTECTED]> wrote:
> > what is really weird is that the machine that hosts that site isn't
> > the only one which has slowed down. the other machine which only
> > serves email experiences the same thing (slow ssh connection, long
> > ping times).
> I'm confused as to why you think this is related to the machine when
> there are multiple machines involved?
i may have stated the case poorly. i thought is was a 7 issue not a
> If you're _absolutely_ sure the problem started occurring with the 7
> upgrade, I'd look at the possibility that the NICs you're using aren't
> as well supported in 7 as they were in 6. Have you verified all the
> speed/duplex settings are matched?
we don't know how to do this, but will try to find out. however, see
below, since i no longer think the problem is 7.
> > we are going to bypass the servers by using one of our dynamic ip
> > addresses and see what it is like then. if that computer
> > experiences a slowdown, i think it may suggest that the problem is
> > due to network activity within the cable company. if there is no
> > slowdown, then that seems to point the problem exclusively to our
> > servers.
> That's also a good diagnostic step.
ok i am 99% convinced now that this has nothing to do with freebsd 7 at
all. here's why:
1. there are 2 servers involved and they both get affected so as you
say, bill "It sure sounds like a network issue, from the description of
the symptoms." if it were a 7 issue, then there is no reason for them
to be affected simultaneously - but if it is a network issue, they
would experience the slowdowns together which they do.
2. by-passing the servers produced mirror results. the machine on the
dynamic address displayed an identical ping pattern to the same sites
as those going through the servers. this would suggest that the problem
has nothing to do with our servers.
3. we just found that on more than one instance when there was heavy
activity on the website server, the pinging rate was low. this suggests
that our servers are more than capable of handling the load and are not
slowing our access down at all.
4. though i said we didn't have the problem with 6.3 initially which
was true, this doesn't mean that the problem lies with 7 - all it
means is that we didn't notice anything wrong with 6.3 while we used
it. if this is a network issue from the outside, it may have started
recently and merely coincides with our upgrade to 7. also, my son
recalls that on rare occasions 6.3 may have acted somewhat slower than
usual (though nothing like what we are experiencing now).
5. i don't see why there would be a dns problem since we are sshing
from within our local network which the servers are part of. in fact,
it is slow even when you use the ip address directly.
so my present conclusion is that bottlenecks may be developing in the
'vicinity' of our assigned ip addresses (static and dynamic). these may
not even be the fault of our cable company possibly, but i'll check
with them anyway again.
the only nagging matter though is why sshing in sometimes becomes slow.
i will do as you suggest though bill (and jonathan) and produce some
network graphs and look at the dns. it will be good to become familiar
with these things since part of the reason for setting up our home
servers was to gain an education about this stuff.
i really appreciate the interest you've shown in our little problem and
will follow through on your earlier suggestions as well as any others
you may have.
... with you on your journey
Information, Inspiration, Imagination - truly a site for soaring I's
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"