|
|
|
This item is for system problems. If something on Grex isn't working right (line noise on a modem, weird behavior from a program, etc.), this is the place to announce it. Except for security holes. If you find a hole in system security, mail information about it to "staff".
405 responses total.
This response has been erased.
darn ....
logging in with ssh .. i have been bounced 4 times whilst entering bbs responses ... first freeze, then disconnect ... someting is screwey in bbs-land ....
parcel : parcel:x:28502:205:lettermail:/d/p/a/parcel:/usr/local/bin/bash seems to be another canadian L-user. from 67.70.138.80 adn 24.146.22.75 ... it shows in whatever.
Login Name TTY Idle Login Time Location Work Phone newuser The Newuser Program p0 13:20 Mar 16 22:32 rcurl Rane Curl *s0 Mar 23 13:48 That newuser is going to wonder where everyone is.....
(Actually, that "newuser" isn't even here, is he/she?)
Grex appeared to suffer a loss of Internet connectivity between 7am and 8am this morning. I dropped by the Pumpkin this afternoon, our DSL modem claimed to have a link, but I power cycled it anyway. We appear to be back. All the modem users had the place to themselves all day. :)
Heh. Thankyou for being a fr- er, for performing a publ service!
What I had bookmarked once upon a time as "Welcome to the grex status page", i.e. where to find out if grex were down, with URL http://grexstatus.nether.net/ , appears to be now a "home" screen for Jared. There is nothing about grex on that page at all...
thankxxx kip
Having issues with ssh, this is what I got when I tried to connect
with PuTTY a couple minutes ago:
Server refused to allocate pty
Warning: no access to tty; thus no job control in this shell...
mesg: I/O
stream 2 improperly redirected
stty: TCGETS: Operation not supported on socket
stty:
standard input: Operation not supported on socket
TERM: Undefined variable.
stty:
standard input: Operation not supported on socket
mesg: I/O stream 2 improperly
redirected
I get that once in a while with ssh. I think it's because the ssh server on Grex doesn't know how to handle the telnet queue.
This response has been erased.
I have been connecting via telnet using MacSSH in rlogin mode (the client has only ssh2 otherwise). Today, however, I encountered a queue, and was disconnected when the queue reached zero (many times). I recall this happened another time when there was a queue. Is there an explanation, or cure (perhaps by setting parameters in the client) to fix this?
Try "stty 9600" on the client end before connecting to grex. Grex is entirely too trusting of tty parameters from random clients... I'm surprised though that you're using rlogin...
There was discussion about this before. Since Grex doesn't support SSH2, and Rane's telnet client can't do SSH1, rlogin is about his only alternative.
The client also supports rsh, rexec and "raw TCP". Any of those options?
Not really. rsh might work but it wouldn't give you any advantages over rlogin.
What has happened to port-fwd (SSH) thru Grex - worked well before, now I get disconnected and/or it just freezes.
It was intentionally disabled, as it's against policy and has other problems. If you want to discuss the technical issues, you might want to ask in the garage conference, but you might first want to check coop and look for past discussions on port forwarding, or enter a new item to discuss port forwarding and sshd.
repeated disconnets from telnet session 11:49am Friday.
Problem doesn't seem to be my ISP. I get halfway through the agora and the keyboard doesn't respond on grex. The disconnect seems to happen after about four minutes of no throughput. [logging off on my own this time]
yep I keep getting kicked, last time
in mid party quip
not idle at all
Many people in party are reporting random disconnects; I got hit once.
FWIW, I've seen packets dropped between the ISP and grex every time I traced the route this evening. Sometimes, it's only one hop's worth, but it's sometimes been more.
weirdness on disconnects: tsty ttyp6 pcp05308905pcs.w Sat Apr 3 01:25 - 02:04 (00:38) tsty ttypa pcp05308905pcs.w Sat Apr 3 01:46 - 02:21 (00:34) tsty ttypb pcp05308905pcs.w Sat Apr 3 02:03 - 02:23 (00:20) tsty ttyp5 pcp05308905pcs.w Sat Apr 3 02:04 still logged in tsty ttyp3 pcp05308905pcs.w Sat Apr 3 02:45 still logged in tsty ttyp9 pcp05308905pcs.w Sat Apr 3 02:47 still logged in didn't matter if party/mail/bbs fwiw.
more weirdness User tty login@ idle JCPU PCPU what tsty ttyp1 6:52am 10 4 w tsty ttyp2 6:20am 3 21 10 bbs the bbs w/idle created resp #26 .. teh connectin froze this response is from ttyp1 .... grex took anoher login but the first connectin is still frizzed! and now > w |grep ts tsty ttyp1 6:52am 19 9 grep ts tsty ttyp2 6:20am 6 21 10 bbs > something weird ... did't even get 'y9ou are logged on twice' notice.
same shit; same day! tsty ttyp1 6:52am 3 47 20 more tsty ttyr1 7:30am 6 2 grep ts ssh relogin timed out twice this time. now i'n straight telnet.
although the formatting is messed, here is tracert:
seems hop 16 might have a problem
04/04/04 07:42:24 Fast traceroute 216.93.104.34
Trace 216.93.104.34 ...
1 No Response * * *
2 68.87.61.13 11ms 16ms 10ms TTL: 0
(ge-2-1-ur01.annarborwest.mi.mich.comcast.net ok)
3 68.87.60.130 10ms 13ms 11ms TTL: 0
(srp-0-0-ur01.pontiac.mi.mich.comcast.net ok)
4 12.119.243.105 16ms 18ms 12ms TTL: 0 (No rDNS)
5 12.123.139.34 12ms 11ms 13ms TTL: 0 (gbr2-p30.dtrmi.ip.att.net
probable bogus rDNS: No DNS)
6 12.122.12.181 12ms 17ms 13ms TTL: 0 (tbr2-p012601.dtrmi.ip.att.net
probable bogus rDNS: No DNS)
7 12.122.10.134 26ms 26ms 20ms TTL: 0 (tbr2-cl1.cgcil.ip.att.net
probable bogus rDNS: No DNS)
8 12.123.6.69 20ms 21ms 19ms TTL: 0 (ggr2-p3120.cgcil.ip.att.net
probable bogus rDNS: No DNS)
9 208.175.10.93 21ms 26ms 20ms TTL: 0
(dcr1-so-3-3-0.Chicago.savvis.net ok)
10 208.175.10.50 20ms 20ms 19ms TTL: 0
(agr1-so-0-0-0.Chicago.savvis.net ok)
11 208.172.2.24 25ms 23ms 20ms TTL: 0
(bar16-loopback.Chicago.savvis.net ok)
12 208.172.8.206 35ms 41ms 34ms TTL: 0 (voyagernet.Chicago.savvis.net
ok)
13 209.153.129.86 36ms 37ms 37ms TTL: 0
(se3-0.rtr0.flnt.mi.voyager.net ok)
14 209.153.142.3 37ms 38ms 39ms TTL: 0
(fe0-0.rtr1.flnt.mi.voyager.net ok)
15 216.93.15.210 36ms 39ms 36ms TTL: 0 (rback0.flnt.mi.voyager.net
ok)
16 No Response * * *
17 216.93.104.34 60ms 61ms 218ms TTL:241 (grex.cyberspace.org ok)
ohhh, yes, ANother damn freeze & ssh timeout & telnet login.
I didn't get a disconnect from my telnet session! (So, there's no problem anymore, I guess.)
This response has been erased.
same here.
Not only is telnet down, but attempting to telnet to grex immediately kills one's ssh session!
Not for me: Two ssh and one telnet session open simultaneously, and all working.
I still frequently get things locked up for about a minute (for the past week or so) as does Jim, when dialed in or telnetted. And my mail logfile records locks of some sort.
ssh seems to be a *lot* more sensitive to network interruptions than telnet. I'm not sure why.
I just got locked up twice in 5 minutes while telnetted - reading mail, and reading bbs. Quicker to close the connection and telnet back than to wait the minute for it to unlock.
sshd sets SO_KEEPALIVE. Telnet does not.
Ah. That would do it.
| Last 40 Responses and Response Form. |
|
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss