|
Grex > Helpers > #136: Grex System Problems - Fall 2004 |  |
|
| Author |
Message |
| 25 new of 109 responses total. |
twenex
|
|
response 38 of 109:
| 
Oct 8 12:50 UTC 2004 |
Only to the directory ~twenex, whose permissions have recently been changed
and then changed back again.
|
gelinas
|
|
response 39 of 109:
|
Oct 8 12:57 UTC 2004 |
Ah. I think you have to give "r-x" to everyone, to enable picospan to
find and read your .cflist file.
That's largely why I use a ~/Private and ~/Public structure. :)
|
twenex
|
|
response 40 of 109:
|
Oct 8 13:03 UTC 2004 |
The permissions were the problem. The permissions need to be at least 750,
or rwxr-x---. I had inadvertently changed them "back" to 740, no "x"
permission for the group.
Thanks.
|
keesan
|
|
response 41 of 109:
|
Oct 11 20:28 UTC 2004 |
/tmp is full, cannot write to file.
|
gelinas
|
|
response 42 of 109:
|
Oct 12 04:22 UTC 2004 |
Fixed. Thank you for mentioning it.
|
mfp
|
|
response 43 of 109:
|
Oct 12 04:25 UTC 2004 |
This response has been erased.
|
naftee
|
|
response 44 of 109:
|
Oct 12 06:39 UTC 2004 |
Thanks gelinas!
|
katie
|
|
response 45 of 109:
|
Oct 12 12:48 UTC 2004 |
Still a problem...I can't read mail.
|
bhoward
|
|
response 46 of 109:
|
Oct 12 15:03 UTC 2004 |
/tmp filled up again. Fixed.
|
tsty
|
|
response 47 of 109:
|
Oct 13 08:11 UTC 2004 |
it fille up again an hour or so ago .. but fixed now, somehow.
|
albaugh
|
|
response 48 of 109:
|
Oct 15 16:38 UTC 2004 |
Just now: Tried to telnet to grex, connection failed, twice in a row. Was
able to connect/"login" via backtalk. Then went back and was able to
connect/login via telnet. This has happened before. Comments?
|
davel
|
|
response 49 of 109:
|
Oct 15 16:50 UTC 2004 |
Just a few minutes ago, I & some others I talked with (phones) had a lot of
trouble connecting to anything at all through the internet. I'd say something
was not working out there, & that it got fixed.
|
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?
|