|
|
| Author |
Message |
| 25 new of 292 responses total. |
scott
|
|
response 6 of 292:
| 
Sep 24 19:29 UTC 1999 |
I think groovy has more flaky ports now. Sigh, that's why I swapped groupie
out. :(
|
keesan
|
|
response 7 of 292:
|
Sep 24 19:59 UTC 1999 |
Could someone post (here) the list of phone numbers, in order, and I would
be willing to phone in to all of them in order to see if I can pinpoint the
problem. Again, 7613000 did not work, 761-5041 (at or near the end) did.
|
other
|
|
response 8 of 292:
|
Sep 24 20:27 UTC 1999 |
keesan, scott is suggesting that the terminal server is the problem, not the
modem. that means that the phone number is not related to whether or not you
have a problem.
|
mooncat
|
|
response 9 of 292:
|
Sep 24 22:56 UTC 1999 |
I just experienced the connecting- but no response from Grex problem.
I only know the 761-3000 number (I always forget to look up the other
numbers when I'm online) so I had to dial several times before getting
a connection that worked.
Oh and, 764-544
|
mooncat
|
|
response 10 of 292:
|
Sep 24 22:57 UTC 1999 |
(er... 734-544 I have no idea what 764 is the area code for... <shrugs>)
|
scg
|
|
response 11 of 292:
|
Sep 25 06:17 UTC 1999 |
Ok, on that list of NPA/NXXs, we seem to have Ann Arbor Main, Ann Arbor
Southeast, and Ypsi Main. That would seem to suggest that it's not CO
specific.
|
scott
|
|
response 12 of 292:
|
Sep 25 12:20 UTC 1999 |
Actually the phone numbers for Grex do map to specific modems and then onto
specific ports on the terminal server. So trying numbers would be a useful
thing after all. You can get the list of phones by typing !phones or
phones at a prompt.
|
other
|
|
response 13 of 292:
|
Sep 25 18:36 UTC 1999 |
oh, oops. i thought the server just assigned connections to whatever port
was available... sorry.
|
kaplan
|
|
response 14 of 292:
|
Sep 25 21:23 UTC 1999 |
agora 4 linked to helpers 84
|
scott
|
|
response 15 of 292:
|
Sep 25 21:49 UTC 1999 |
...and then Grex assigns a random telnet port to a terminal server port. That
part is true, such that you can't tell from the tty what terminal server port
it is. But phone numbers still map directly.
|
gelinas
|
|
response 16 of 292:
|
Sep 25 22:41 UTC 1999 |
Re #2: No, my .forward was _not_ still there. I (re-)created it when I
discovered I had mail. Of course, I may have just thought I created one
originally. It's still there, now, though, so I guess it's fine.
|
aruba
|
|
response 17 of 292:
|
Sep 26 00:19 UTC 1999 |
That sounds likely. You're certainly allowed to have a .forward on Grex.
|
nephi
|
|
response 18 of 292:
|
Sep 26 03:40 UTC 1999 |
|
keesan
|
|
response 19 of 292:
|
Sep 27 22:23 UTC 1999 |
I have not been having any trouble connecting at 761-3000 for two days now.
|
remmers
|
|
response 20 of 292:
|
Sep 27 22:55 UTC 1999 |
I just connected to 761-3000 successfully.
|
pfv
|
|
response 21 of 292:
|
Sep 29 17:02 UTC 1999 |
System load has been over 18 and back & forth between 11 and 14
for over an hour now.. Systems acting weird as hell.
My other session is now totally locked up and even AYT's are doing
nothing at all.
What gives?
|
gull
|
|
response 22 of 292:
|
Sep 30 13:39 UTC 1999 |
I fear something Very Bad is happening to /var/spool/mail. Pine gave me
this error when I tried to close my inbox:
SERIOUS DISK ERROR WRITING: "/var/spool/mail/g/u/gull"
The reported error number is 6. The last reported mail error was:
"Unable to sync folder: No such device or address"
Retrying got "Unable to sync folder: I/O error"
|
aruba
|
|
response 23 of 292:
|
Sep 30 14:07 UTC 1999 |
I had a similar problem. When I logged in earlier Grex told me I had no
mail, although I have a lot of old messages in my mailbox. I did an ls -l
on /var/spool/mail/a/r and saw this:
ls: arrow: I/O error
ls: arunjun: I/O error
ls: arthur: I/O error
ls: aravind: I/O error
etc. After a bunch of those, a bunch of normal output from ls, like
-rw------- 1 ar humans 3345 Sep 21 00:04 ar
-rw------- 1 ara007 populus 5571 Sep 28 01:01 ara007
-rw------- 1 arabella people 74352 Sep 30 06:58 arabella
-rw------- 1 arabian humans 0 Jun 4 20:21 arabian
Mine was among the normal files, so I ran Pine, and it tried for a while
to open my inbox, then Grex logged me out. I tried to log in again a
couple times, and Grex hung up on me each time. So I waited a few minutes
and tried again, and now everything seems fine.
|
rcurl
|
|
response 24 of 292:
|
Sep 30 15:56 UTC 1999 |
I haven't been able to connect via Merit since last night - get a domain
not known error this morning (couldn't even get into Merit last night).
Anyone know anything about a problem there?
|
mooncat
|
|
response 25 of 292:
|
Sep 30 17:39 UTC 1999 |
i don't know if this is connected to Merit or not, however, U of M had
a fire (apparently) in the computer area, so they've been trying to deal
with this. I can't get into my U of M mail (apparently only a few boxes
were destroyed and thus some people can get access and some can't.). That
may have a connection to the Merit problem. <shrugs> dunno.
|
rcurl
|
|
response 26 of 292:
|
Sep 30 17:52 UTC 1999 |
That's probably it.
|
mcnally
|
|
response 27 of 292:
|
Sep 30 18:19 UTC 1999 |
Yep.. According to reports, a bank of batteries in the Computing Center
building caught fire and began leaking acid. Fire crews shut down power
to the building and it's taken a while to straighten things out..
|
flem
|
|
response 28 of 292:
|
Sep 30 20:09 UTC 1999 |
That would explain it. I can't get to my email either.
|
otaking
|
|
response 29 of 292:
|
Sep 30 20:56 UTC 1999 |
When I came into work this morning at UM North Campus, I was told that some
idiot severed a major internet connection with a backhoe in Ohio. The
university lost e-mail and internet access for the entire morning because of
it. I could only access UM sites from here until noon.
|
mcnally
|
|
response 30 of 292:
|
Sep 30 22:54 UTC 1999 |
That also happened. (Backhoes: nature's most fearsome predator of the
helpless fiber-optic cable..) If you're interested in reading about that
one there was an article in today's (9/30) Wired News..
|
