|
|
| Author |
Message |
| 25 new of 188 responses total. |
scott
|
|
response 25 of 188:
|
Sep 26 22:28 UTC 2000 |
The network was way bogged down, partially due to a vandal trying to flood
another system.
|
albaugh
|
|
response 26 of 188:
|
Sep 27 04:13 UTC 2000 |
I lost grex telnet connectivity around 6:30pm Tue 9/26, and backtalk couldn't
grex either. I'm dialing in now, 12:15am Wed 9/27.
|
ea
|
|
response 27 of 188:
|
Sep 30 15:43 UTC 2000 |
Backtalk seems to be running really slowly this morning. It's not
timing out, but it's taking much longer than usual.
|
mcnally
|
|
response 28 of 188:
|
Sep 30 21:08 UTC 2000 |
Lately I've been experiencing long delays between the time my telnet
program reports connecting to Grex and the time the login prompt shows
up, even when there's no queue..
|
gelinas
|
|
response 29 of 188:
|
Sep 30 21:15 UTC 2000 |
I've noticed that delay, too.
|
tpryan
|
|
response 30 of 188:
|
Sep 30 22:55 UTC 2000 |
I've been getting that delay on the dial-up server. This morning
I got disconnected by that thing instead of Grex proper. Some message
about My Host don't know cyberspace.org or something like that.
|
scg
|
|
response 31 of 188:
|
Sep 30 23:52 UTC 2000 |
Grex's named wasn't running, for some reason.
|
flem
|
|
response 32 of 188:
|
Oct 3 17:50 UTC 2000 |
While running pine today, I got the following error message:
ld.so: call to undefined procedure _sigpause from 0xef785528
Unsurprisingly, pine crashed.
|
keesan
|
|
response 33 of 188:
|
Oct 5 00:22 UTC 2000 |
I have gotten this message a few times, after a long delay when I tried to
send mail.
|
jp2
|
|
response 34 of 188:
|
Oct 6 18:16 UTC 2000 |
This response has been erased.
|
rcurl
|
|
response 35 of 188:
|
Oct 6 19:03 UTC 2000 |
After entering logout at the shell prompt, one gets another login
prompt. Responding exit sometimes logs out, and sometimes produces
yet another login prompt. I have not detected evident cause of sometimes
getting a second chance to login again, and sometimes not. Is there
method to the madness?
|
mdw
|
|
response 36 of 188:
|
Oct 6 20:02 UTC 2000 |
Try "stty 9600" *BEFORE* connecting to grex.
|
rcurl
|
|
response 37 of 188:
|
Oct 7 05:04 UTC 2000 |
I'm telneting in.
|
mdw
|
|
response 38 of 188:
|
Oct 7 06:17 UTC 2000 |
And?
|
bdh3
|
|
response 39 of 188:
|
Oct 7 06:25 UTC 2000 |
He's telnetting in.
|
mdw
|
|
response 40 of 188:
|
Oct 7 06:58 UTC 2000 |
It surprises me how sometimes people who appear to be so totally
rational can get stuck making some pretty silly assumptions about the
world. Computers are not magical. Computers do not have ESP. Just
because you *think* "stty 9600" won't make a difference to telnet,
because you're not using a serial connection, doesn't mean squat to
those little electrons flying around in your computer, or in grex. The
true essence of science is *not* just logic, but *also* to experiment
with an open mind. So, if you want to solve this problem, discard your
prejudices, try this, and see if it makes a difference.
|
bru
|
|
response 41 of 188:
|
Oct 7 16:51 UTC 2000 |
The system has frozen and then dumped me 6 times in the last two days. What
is the problem here?
|
scg
|
|
response 42 of 188:
|
Oct 7 17:10 UTC 2000 |
It just did that to me too. It appeared to be some sort of network problem,
although I didn't manage to get a traceroute going until after it had come
back.
|
scg
|
|
response 43 of 188:
|
Oct 7 17:16 UTC 2000 |
And it just did it again. As far as I can tell, I'm getting bumped off every
time I start a response criticizing Ralph Nader. Once again, it was back up
by the time my traceroute got that far.
|
jp2
|
|
response 44 of 188:
|
Oct 7 17:20 UTC 2000 |
This response has been erased.
|
rcurl
|
|
response 45 of 188:
|
Oct 7 18:32 UTC 2000 |
Well, after I said in #35 that logging out didn't always work on the first
attempt, Marcus said in #36 to "stty 9600", but since that doesn't affect
telnetting, I stated that in #37, so I don't know why Marcus said "And?"
in #38.
|
scott
|
|
response 46 of 188:
|
Oct 7 21:14 UTC 2000 |
Are you certain it doesn't affect telnet? Telnet clients can do some weird
things at times, and looking for a certain baud rate might be one of them.
|
gelinas
|
|
response 47 of 188:
|
Oct 8 00:25 UTC 2000 |
FWIW, I use <CTRL>D at the login: prompt; it always goes away promptly.
|
mdw
|
|
response 48 of 188:
|
Oct 8 04:49 UTC 2000 |
Actually, in reviewing the above, I do have a clarification: my response
#36 was actually prompted by #34. I suspect #35 had slipped in, and #37
confused me into thinking it was in response to #36 and not a separate
problem.
Re #41,#42,#43 - I think there's a problem with the last hop to grex.
Or, at least, the one time I was able to try things with tracroute
before the connection came back, I found low RTTs to
eth3-0.rback0.flnt.mi.voyager.net, followed by lots of packet drops &
occasional 800 ms RTTs to cyberspacecomm.flnt.mi.voyager.net, and almost
no connectivity to grex itself. Probably what I should be doing is
"traceroute -n" while the trouble is happening, so that traceroute won't
have to wait for the name server...
|
rcurl
|
|
response 49 of 188:
|
Oct 8 05:39 UTC 2000 |
I suspected you had slipped in, but I thought I'd see what transpired if
I went along as though it applied to my comment...... It did go off
into an unexpected direction. What *does* 9600 baud have to do with
a telnet connection?
|