|
Grex > Helpers > #136: Grex System Problems - Fall 2004 |  |
|
| Author |
Message |
| 25 new of 109 responses total. |
jor
|
|
response 50 of 109:
| 
Oct 15 20:15 UTC 2004 |
Interesting. I was in an office about 11:45 a.m.,
and their LAN had just lost their Comcast
internet connection.
|
twenex
|
|
response 51 of 109:
|
Oct 17 19:40 UTC 2004 |
Grex is now back up, but there is as yet no explanation as to why it was down
today (Sunday). It might be nice to have one, if it's possible.
|
janc
|
|
response 52 of 109:
|
Oct 17 21:39 UTC 2004 |
Checking the staff conference, it appears that Joe rebooted Grex. It
had crashed. There was no error message on the console.
|
twenex
|
|
response 53 of 109:
|
Oct 17 21:40 UTC 2004 |
Ah. Fair enough, thanks.
|
gelinas
|
|
response 54 of 109:
|
Oct 18 01:31 UTC 2004 |
I've now updated the motd. I'm sorry that I didn't have time to do so
while in the Pumpkin.
|
davel
|
|
response 55 of 109:
|
Oct 18 17:57 UTC 2004 |
Joe, thanks for rebooting. Much more important, much as we all like to know
what's going on.
|
rcurl
|
|
response 56 of 109:
|
Oct 19 18:21 UTC 2004 |
Has something changed in internet access to Grex? rlogin used to work to
telnet to Grex, but now it doesn't work.
|
janc
|
|
response 57 of 109:
|
Oct 22 14:42 UTC 2004 |
I can't think of anything, unless it is a change in the configuration of the
firewall that I don't know about. When did it last work for you?
|
rcurl
|
|
response 58 of 109:
|
Oct 22 16:51 UTC 2004 |
It may have been several weeks before I mentioned it that I had previously
used rlogin at all. I had been connecting using the MacSSH client which
does not have ssh1, but recently have been using the Terminal client with
ssh1.
|
janc
|
|
response 59 of 109:
|
Oct 23 03:23 UTC 2004 |
I'm not aware of any changes in that time frame.
|
naftee
|
|
response 60 of 109:
|
Oct 23 22:47 UTC 2004 |
In your frame of reference, (Inertial F.O.R.) that is unlikely.
|
richard
|
|
response 61 of 109:
|
Oct 26 00:27 UTC 2004 |
Got the following when I tried to log on earlier:
"Backtalk Crash!
Mon Oct 25 20:26:07 2004
Oops! The authors of Backtalk are deeply sorry to confess that our
program has failed to operate correctly. This is due to an error in
Backtalk itself, or in one of Backtalk's script files, or in the
configuration of the system. It is probably not due to anything you
might have done. The page below contains an error message and a
detailed dump of the state Backtalk was in when the error occurred.
This may be useful to anyone trying to fix the problem.
All this information has been logged, but it may still be helpful for
you to report this error and the circumstances under which it occurred
to the system administrators.
Thanks for your assistance in getting the bugs out of this
conferencing system. We sincerely and humbly beg your forgiveness."
|
aruba
|
|
response 62 of 109:
|
Oct 26 00:30 UTC 2004 |
What was the error message, Richard?
|
gregb
|
|
response 63 of 109:
|
Oct 27 16:40 UTC 2004 |
From my experience, nothing'll get done. I've noted problems with
Backtalk in the past and have never gotten any response or has the
problems been fixed. Backtalk seems to be the step-child of Grex. And
gets treated as such.
|
aruba
|
|
response 64 of 109:
|
Oct 27 22:38 UTC 2004 |
That hasn't been my experience. Jan is very active programming things, and
just lately he's done a huge amount of work to get NextGrex up and running.
However, I'm sure he will need the error message from Richard to be able to
duplicate the problem.
|
baker
|
|
response 65 of 109:
|
Oct 28 01:53 UTC 2004 |
I would like to send Jan a loaf of bred in return for his work on Grex, which
I hope will be a duitiful business partner. It's the "yeast" i can do.
|
naftee
|
|
response 66 of 109:
|
Oct 28 02:17 UTC 2004 |
Dude, pass the shrooms
|
gull
|
|
response 67 of 109:
|
Oct 28 13:35 UTC 2004 |
Re resp:63: We're not the only site that runs Backtalk, and it *is*
being actively developed by Jan. According to
http://www.unixpapa.com/backtalk/, we're not running the most current
version. Probably he's holding out on doing any major upgrades on the
current system, since it's going to be replaced by NextGrex anyway.
|
keesan
|
|
response 68 of 109:
|
Oct 29 04:44 UTC 2004 |
Today it has been taking about a minute to actually send a mail.
|
keesan
|
|
response 69 of 109:
|
Oct 29 05:07 UTC 2004 |
And a minute to time out on outgoing telnet. Maybe the mail just got queued?
|
keesan
|
|
response 70 of 109:
|
Oct 29 05:08 UTC 2004 |
And no incoming mail since 2 pm. Time to call staff.
|
drew
|
|
response 71 of 109:
|
Oct 29 06:29 UTC 2004 |
Internet connection seems to be hosed. Again.
|
gelinas
|
|
response 72 of 109:
|
Oct 29 10:29 UTC 2004 |
Yes, it does seem to be the Internet connection. I'm power-cycling the DSL
modem right now. That is, I've turned it off and will turn it back on
shortly.
|
gregb
|
|
response 73 of 109:
|
Oct 29 16:25 UTC 2004 |
Re. 64: No offense, Mark, but being in the inner circle makes your
observation perceptively biased. The problems/concerns I brought up
occured some time ago, before Jan's work on NextGrex, of which I
agree, he's been working his buns off with. I look forward to giving
the new system a spin.
|
rcurl
|
|
response 74 of 109:
|
Nov 2 06:37 UTC 2004 |
rlogin and ssh1 are not working tonight. (I don't try relogin very often,
but tonight ssh1, my usual, wasn't working either, so I'm finally on with
plain old telnet.)
|