|
Grex > Helpers > #134: Grex System Problems - Summer 2004 |  |
|
| Author |
Message |
| 25 new of 286 responses total. |
krj
|
|
response 210 of 286:
| 
Sep 12 05:49 UTC 2004 |
Connections via telnet have also seemed slower than usual, though
I have not attempted to measure the time.
|
mcnally
|
|
response 211 of 286:
|
Sep 13 05:41 UTC 2004 |
I am still experiencing an extended wait between the time that I start
my ssh client (PuTTY) and the time I receive a login prompt from Grex.
Performance is more or less normal once I get logged in but it takes
quite a while for the login prompt to show up. While connecting to my
present session I timed it and it took 79 seconds before I got a prompt.
Any ideas?
|
rcurl
|
|
response 212 of 286:
|
Sep 13 06:14 UTC 2004 |
I just opened another ssh1 terminal window to Grex, and it also took 79
seconds for the login prompt to appear.
|
jor
|
|
response 213 of 286:
|
Sep 13 12:07 UTC 2004 |
similar delay with dialin.
|
davel
|
|
response 214 of 286:
|
Sep 13 12:57 UTC 2004 |
and with telnet.
|
aruba
|
|
response 215 of 286:
|
Sep 13 13:03 UTC 2004 |
Yup, I get the same thing.
|
tod
|
|
response 216 of 286:
|
Sep 13 13:52 UTC 2004 |
telnet takes 2 min
|
gull
|
|
response 217 of 286:
|
Sep 13 16:02 UTC 2004 |
Staff seems to have given up on commenting in this item. Maybe someone
will have to go prod them in coop or garage to find out what's actually
going on?
|
twenex
|
|
response 218 of 286:
|
Sep 13 16:07 UTC 2004 |
prod them in coop[, or in] garage... or in person.
|
mfp
|
|
response 219 of 286:
|
Sep 13 16:18 UTC 2004 |
Point.
|
cmcgee
|
|
response 220 of 286:
|
Sep 13 20:28 UTC 2004 |
Very consistent 78-79 second delay between welcome to Grex and login prompt
when I dial in.
|
naftee
|
|
response 221 of 286:
|
Sep 13 21:00 UTC 2004 |
Yeah, I was using m-net and forgot about the GreX window for a secONde.
|
gull
|
|
response 222 of 286:
|
Sep 13 23:17 UTC 2004 |
Sounds suspiciously like it's waiting for a dead nameserver to time out.
|
krokus
|
|
response 223 of 286:
|
Sep 14 02:06 UTC 2004 |
re 217
Despit the staff being staff, Grex isn't their entire life. I'm sure
they'll comment when they have a few spare minutes.
|
gelinas
|
|
response 224 of 286:
|
Sep 14 03:47 UTC 2004 |
Or when we know something worth saying.
|
gelinas
|
|
response 225 of 286:
|
Sep 14 03:59 UTC 2004 |
Based on comments above, I took a look at /etc/resolv.conf, commented
out the loop-back address and restarted named. Now to see if it actually
makes a difference.
|
marcvh
|
|
response 226 of 286:
|
Sep 14 05:04 UTC 2004 |
So far it does not seem to make a difference.
|
mcnally
|
|
response 227 of 286:
|
Sep 14 06:50 UTC 2004 |
re #222:
> Sounds suspiciously like it's waiting for a dead nameserver to time out.
A not unreasonable guess but that doesn't seem to be the problem.
Assuming a reasonable caching policy on Grex it wouldn't have fit
the pattern anyway, as it takes a long time to get the login prompt
every time one tries, not just the first time (after which, presumably
the value would be stored in the local cache.)
re #225:
> Based on comments above, I took a look at /etc/resolv.conf, commented
> out the loop-back address and restarted named. Now to see if it actually
> makes a difference.
Doesn't seem to have.. (And I doubt that restarting named was necessary.)
|
dpc
|
|
response 228 of 286:
|
Sep 14 14:05 UTC 2004 |
It took a minute and 19 seconds to get a prompt just now. I really
hope this situation can be fixed soon.
|
aruba
|
|
response 229 of 286:
|
Sep 14 14:29 UTC 2004 |
Still a long pause for me.
|
gregb
|
|
response 230 of 286:
|
Sep 14 17:07 UTC 2004 |
This is one time I'm glad I use Backtalk.
|
marcvh
|
|
response 231 of 286:
|
Sep 14 17:13 UTC 2004 |
Re #227, caching failed lookups is not universal. Some systems only
cache success, not failure.
|
jor
|
|
response 232 of 286:
|
Sep 14 23:19 UTC 2004 |
I just measured the pause at about 78 seconds.
The temperature is 74. Winds are calm and
my disposition is sunny.
|
tod
|
|
response 233 of 286:
|
Sep 14 23:30 UTC 2004 |
Partly cloudy
hayz buddhist messiah thetan
|
mcnally
|
|
response 234 of 286:
|
Sep 15 07:55 UTC 2004 |
re #231: I was assuming a resolv.conf with more than one nameserver
listed (which I think is how we started) and also assuming only one
broken nameserver such that the resolver query would block until the
first (broken) nameserver timed out and then succeed upon querying
the second server.
I suppose it still could be a nameserver issue but it seems to be
something else. I wonder what's special about 78-79 seconds? Several
people have measured the same delay time at this point (and one or two
report longer times.)
|