|
|
| Author |
Message |
| 25 new of 224 responses total. |
mcnally
|
|
response 50 of 224:
| 
Apr 30 16:58 UTC 2003 |
I used it yesterday, so if it's broken it broke recently..
|
keesan
|
|
response 51 of 224:
|
Apr 30 18:18 UTC 2003 |
I had the same problem - I assumed grex was just slow and I gave up.
About an hour ago today. I was able to ftp out of grex earlier. Is this
related to the discussion in coop about banning inbound ftp until we get the
new computer? So as to not allow people to import large annoying programs?
I was trying to ftp a 2K text file.
|
glenda
|
|
response 52 of 224:
|
Apr 30 18:58 UTC 2003 |
ftp won't be banned without there being a vote on it. Just because it is
being discussed doesn't mean it will be implimented without due process
according to the bylaws.
|
keesan
|
|
response 53 of 224:
|
Apr 30 20:46 UTC 2003 |
Pine and mail both recently refused to send anything at all (could not find
sendmail), mail sending is taking a minute or so, and now someone phoned to
tell me that the attachment that I sent did not get there, but the message
body did. Twice. Small file.
|
krj
|
|
response 54 of 224:
|
May 1 18:37 UTC 2003 |
resp:49 :: ftp is working today, thanks.
|
keesan
|
|
response 55 of 224:
|
May 1 20:01 UTC 2003 |
Everything is working beautifully today, thanks to whoever fixed it.
|
gull
|
|
response 56 of 224:
|
May 2 13:41 UTC 2003 |
I think Grex was having Internet connection problems yesterday. That
may explain some of it.
|
davel
|
|
response 57 of 224:
|
May 5 21:00 UTC 2003 |
Earlier, when I tried to get on (via dialin), it was very slow, and then Grex
kept disconnecting me. Eventually I telnetted in; it was only fairly slow.
But then I started getting errors writing to /tmp - filesystem was full. It's
still pretty full.
|
scott
|
|
response 58 of 224:
|
May 5 22:29 UTC 2003 |
A culprit was collared.
|
davel
|
|
response 59 of 224:
|
May 6 13:43 UTC 2003 |
A big THANKS to all those hardworking, underappreciated folks on staff who
have to deal with this stuff!
|
other
|
|
response 60 of 224:
|
May 6 13:59 UTC 2003 |
Woohoo Staff!
<cheers and waves an organic carrot in a competely non-threatening
manner>
|
drew
|
|
response 61 of 224:
|
May 6 19:05 UTC 2003 |
Somebody with root access please empty out /tmp. It's at 100%.
|
gregb
|
|
response 62 of 224:
|
May 6 23:53 UTC 2003 |
Hey, Drew! First time I've seen you since I re-joined. How'd you like
PenguiCon?
|
drew
|
|
response 63 of 224:
|
May 7 15:40 UTC 2003 |
I liked it a lot.
|
tpryan
|
|
response 64 of 224:
|
May 15 14:56 UTC 2003 |
Why does Grex answer the phone, then hang up on me.
in my world, that is RUDE!
|
pfv
|
|
response 65 of 224:
|
May 15 15:49 UTC 2003 |
ssh: password denied.
telnet: new/old password tripe.
Can we get ssh to understand this shit, or stop screwing with the password
mandatorily? This is really irritating.
thanks.
|
goose
|
|
response 66 of 224:
|
May 15 19:25 UTC 2003 |
Hmm..other than complaining that it's SSH1, SSH Secure Shell has always worked
for me, PuTTY too (without the SSH1 complaints)
Win2k environment of course.
|
tod
|
|
response 67 of 224:
|
May 15 19:30 UTC 2003 |
This response has been erased.
|
remmers
|
|
response 68 of 224:
|
May 15 20:01 UTC 2003 |
The problem is that ssh doesn't understand the password expiration
system (the thing that requires you to change your password every
so often). If you log in with telnet and your password has expired,
telnet gives you an opportunity to change it, but ssh just fails to
log you in. When this happens, you have to connect via telnet and
change your password. Then ssh will work again. Not a very
satisfactory situation. I think that Pete is suggesting that
we turn off password expiration until we can make ssh deal with
it properly. This probably won't happen before we get onto the new
hardware and OS. Offhand, turning off password expiration seems
reasonable to me.
|
tod
|
|
response 69 of 224:
|
May 15 21:04 UTC 2003 |
This response has been erased.
|
cross
|
|
response 70 of 224:
|
May 15 21:55 UTC 2003 |
This response has been erased.
|
keesan
|
|
response 71 of 224:
|
May 15 23:35 UTC 2003 |
Will the new grex recognize 'linux' terminal type instead of unknown?
My arrow keys won't work when I telnet to grex with linux and use Lynx.
I have set it to force vt102.
|
tod
|
|
response 72 of 224:
|
May 15 23:43 UTC 2003 |
This response has been erased.
|
cross
|
|
response 73 of 224:
|
May 15 23:47 UTC 2003 |
This response has been erased.
|
keesan
|
|
response 74 of 224:
|
May 15 23:50 UTC 2003 |
How would that work when I am not using xterm?
Someone else for whom I set up a user account here says he is unable to telnet
to grex with Linux, but can do so with grex, and he asked a friend to try and
the friend could telnet with Windows but not Linux. I am using the identical
linux telnet program (on different computers, of course). He also tried with
ssh. He says he tried many times with Linux telnet and it never worked.
---------------------------------------
> . What happens exactly when you try to telnet?
me@computer:~$ telnet www.grex.org
Trying 216.93.104.34...
Connected to grex.cyberspace.org.
Escape character is '^]'.
Connection closed by foreign host.
me@computer:~$
I never get as far as bash. As you can see, the connection gets closed by
the foreign host almost immediately.
> You can also try telnetting to www.grex.org and signing in as newuser and
> choosing your own login and password and shell and having it identify your
> terminal - perhaps that will work better.
I never have gotten that far on any Linux machine. The connection
always gets closed before any login prompt. I use telnet and ssh for
other connections from the Linux machines in question, and have never
encountered any problem. Only your shell svc does this. I've logged in
at www.grex.org and run Pine using a Win machine or two, but I can't get
it to work from any Linux machine (including the one I have BL2 on).
James
(I don't know what he means by a shell svc. I think I set him up with
bash).
-----------------------------------------
Never, at any time that I've tried logging in from a Linux machine, has it
worked. I've tried probably 20 - 25 times, at various times of night and
day. Every time I have tried from a Win machine, it has worked. I've
never gotten the "connection closed by freign host" message using a Win
machine (tried this 3 or 4 times probably). One of the individuals from
the IRC channel tried it from a Linux machine, then a Win machine,
apparently in immediate succession. It would fail (with the same error
I'm getting, I presume) from the Linux machine, but got a login prompt
from the Win machine.
I just tried logging in using ssh. I got an ominous warning, as follows:
me@mycomputer:$ ssh www.grex.org
The authenticity of host 'www.grex.org (216.93.104.34)' can't be established.
RSA1 key fingerprint is 74:4c:1e:86:04:2a:ac:ab:c2:cd:32:ff:19:76:80:fc.
Are you sure you want to continue connecting (yes/no)? no
Host key verification failed.
me@mycomputer:$
Afterward, I answered "yes" and was able, finally, to login using ssh.
But telnet is failing under Linux. Maybe it has to do with the
authenticity problem?
James
-------
-------
It has worked for me and the author of the Linux setup, using the same
software, nary a problem. We both have 33K modems. I don't know what
James has, maybe something faster?
I just confirmed it worked a couple hours ago.
What might be happening on James's end that is causing problems?
This has been a few weeks, it is not that grex is down when he tries.
|
