|
|
| Author |
Message |
| 25 new of 283 responses total. |
krj
|
|
response 50 of 283:
| 
Jan 12 03:33 UTC 1999 |
My calls to Grex have been getting answered by a modem which does not
respond further for about the last fifteen minutes. Apparently the
same problem as reported in #46 and #47. This final time I got lucky,
I guess.
|
aruba
|
|
response 51 of 283:
|
Jan 12 04:00 UTC 1999 |
Yeah, I think krj and I were competing for that modem that doesn't connect
right, because all the other lines were full. The fact that Grex answered
every few tries but didn't connect meant that my attack-dial script wasn't
very effective, and I had to keep restarting it. Scott, is there any way to
fix that modem? Do you know which one it is?
Before I finally got in, I tried changing the speed I was calling at from
14400 to 9600, on a lark. I got in right after that, but I can't say if it
was on the modem that's been having problems.
|
n8nxf
|
|
response 52 of 283:
|
Jan 12 12:30 UTC 1999 |
I was unable to log in via modem today. It would connect then nothing.
I'm in on a telnet right now.
|
void
|
|
response 53 of 283:
|
Jan 12 13:10 UTC 1999 |
same here. i'm here via backtalk.
|
dpc
|
|
response 54 of 283:
|
Jan 12 14:47 UTC 1999 |
I dial in. Yesterday afternoon about 4:30 I dialed -3000 and I *think*
I got no response at all. I tried several other dialins and got busies.
Just now, I got "modem answers but no Grex" on -3000. Then I
got in on -4931.
|
scott
|
|
response 55 of 283:
|
Jan 12 15:49 UTC 1999 |
OK, OK, I'll fix it. ;)
|
keesan
|
|
response 56 of 283:
|
Jan 12 20:53 UTC 1999 |
Don't we have two leftover good modems from the dropped lines?
I dial in at 9600 and have had no connection problems (when not busy signal).
|
scott
|
|
response 57 of 283:
|
Jan 12 22:55 UTC 1999 |
I think it will be a programming issue, like the other times. One of the
modems loses its settings...
|
keesan
|
|
response 58 of 283:
|
Jan 13 05:09 UTC 1999 |
I just dialed in at 9600 and connected at 2400. 761-3000. Earlier I could
not connect until I dialed 5041, at 9600.
|
scott
|
|
response 59 of 283:
|
Jan 13 16:26 UTC 1999 |
Might be a dirty phone line issue.
Busy signals right now; means that a lot of people are dialed in after Grex
was down for a few hours. If any modems are still misbehaving I'll be able
to check the logs.
|
aruba
|
|
response 60 of 283:
|
Jan 13 19:11 UTC 1999 |
I got a busy signal just now, but there are only 6 people dialed in on the
terminal server. What's up with that?
|
scott
|
|
response 61 of 283:
|
Jan 13 19:57 UTC 1999 |
According to the terminal server, there has been no activity on lines
3,4,5,8,9 (server ports). Clearly I need to visit the Pumpkin and find out
the truth.
|
scott
|
|
response 62 of 283:
|
Jan 13 23:49 UTC 1999 |
I found a number of modems stuck "on", so I reset them. That should free up
the lines. I'll be keeping an eye on them to see if it happens again.
|
aruba
|
|
response 63 of 283:
|
Jan 14 02:32 UTC 1999 |
Thanks Scott.
|
russ
|
|
response 64 of 283:
|
Jan 14 04:14 UTC 1999 |
Re #59:
>Might be a dirty phone line issue.
I had to hang up and re-dial tonight because I got a phone
line that was spewing simply amazing amounts of noise.
|
gregb
|
|
response 65 of 283:
|
Jan 14 15:16 UTC 1999 |
Re. 61: Just out of curiousity, what's on 1, 2, 6 and 7?
|
dpc
|
|
response 66 of 283:
|
Jan 14 16:27 UTC 1999 |
The MOTD says Grex was unavailable yesterday morning 1/13. When
I logged on during that period, the System told me "sorry..."
I didn't know if a hacker had wiped the system or what.
The next time, could the staff please post a short message
more enlightening than "sorry..."? Thanx!
|
aruba
|
|
response 67 of 283:
|
Jan 14 18:16 UTC 1999 |
(I would've appreciated that too. I got mail from one new user who thought
he was being told "sorry" because he had entered the wrong password.)
|
steve
|
|
response 68 of 283:
|
Jan 14 23:09 UTC 1999 |
Grex was rendered senseless that morning by a vandal. When I got up
Weds morning I found I was on Grex and what I was doing was frozen at 4:18
am. I elected to get over to the Pumkin on my way to work although I
shouldn't have, because a crisis came up and I was working via the phone
to fix it, while getting ready to head out.
So when I got to Grex I was busy with this other problem and had to
do things as quickly as possible. I didn't have time to fuss with a nice
message--I wanted to create the /etc/nologin file as quickly as possible
to thwart any logins as I inspected the system. Along that time I got yet
another page and was busy working on that on the phone while working on
Grex.
Sometimes, things don't happen as well as they should. Sorry. The
alternative of course would have been for me to skip working on Grex and
let the next available staff person stuble out into the cold and get over
there and deal with it.
|
aruba
|
|
response 69 of 283:
|
Jan 14 23:45 UTC 1999 |
We certainly appreciate your fixing it, STeve.
|
mic
|
|
response 70 of 283:
|
Jan 15 00:24 UTC 1999 |
Thanks STeve!! You did more than your call.
|
steve
|
|
response 71 of 283:
|
Jan 15 03:51 UTC 1999 |
Thanks. With any luck the next time I have to keep people out there
will be a reasonable message explaining why. I do realize that "sorry"
is near Zen-like, and most people prefer error messages that less resemble
a koan.
|
gregb
|
|
response 72 of 283:
|
Jan 15 14:18 UTC 1999 |
Re. 71: Steve, is there a way you could set up a stock msg. that displays
under such circumstances? That way you wouldn't have to come up with
something pithy to say every time. Not to mention saving time.
|
aruba
|
|
response 73 of 283:
|
Jan 15 15:07 UTC 1999 |
Something like, "Sorry, Grex is cranky right now. Call back in a little
while."
|
steve
|
|
response 74 of 283:
|
Jan 15 15:49 UTC 1999 |
Sure--that is an *excellent* idea. I can make it a csh alias, and
type that one command to create the message. Thanks! That solves my
problem of when critically pressed for time, and informing our users.
|
