|
|
| Author |
Message |
| 25 new of 251 responses total. |
mcnally
|
|
response 171 of 251:
| 
Feb 9 22:34 UTC 2003 |
My ssh connection has been dropped several times today, ditto for telnet.
Generally within a few minutes of my connecting, the session will seem to
freeze, with characters I type evidently not reaching whatever program I'm
in at the time. About a minute or so later my ssh client (putty) gives up
the ghost and declares the connection terminated.
If I ping grex from a command prompt window while my putty session is
frozen, packets seem to be getting through at least as far as grex.org.
Is anyone else experiencing this or should I be looking for explanations
on my end first?
|
gull
|
|
response 172 of 251:
|
Feb 9 22:37 UTC 2003 |
ssh and web access has been very erratic for me today. I'm dialed in right
now, but earlier that wasn't working, either.
|
cmcgee
|
|
response 173 of 251:
|
Feb 9 22:41 UTC 2003 |
I've had problems with telnet and ssh in the past couple hours.
|
keesan
|
|
response 174 of 251:
|
Feb 9 23:01 UTC 2003 |
I could not dial or telnet in just now. Using backtalk (6 pm).
|
jmsaul
|
|
response 175 of 251:
|
Feb 9 23:12 UTC 2003 |
I'm in via SSH right now.
|
keesan
|
|
response 176 of 251:
|
Feb 9 23:18 UTC 2003 |
Now I was able to telnet (17 min after my first five attempts).
|
aruba
|
|
response 177 of 251:
|
Feb 9 23:43 UTC 2003 |
I got dumped earlier today too.
|
gelinas
|
|
response 178 of 251:
|
Feb 10 00:16 UTC 2003 |
Generally, I use traceroute when I notice problems like those described
above, and, generally, I see that packets are being dropped between
voyager and grex. Here is an excerpt from the results of a such test
from right now:
} 10 rback0.flnt.mi.voyager.net (216.93.15.210) 56 ms 51 ms 51 ms
} 11 cyberspacecomm.flnt.mi.voyager.net (216.93.107.238) 113 ms 63 ms 65 ms
} 12 grex.cyberspace.org (216.93.104.34) 65 ms 59 ms 67 ms
It's right after hop 10 I see trouble.
Earlier today, I noticed such things, when I was logged in (via ssh)
between 14:56 and 15:38. I guess my ssh client was more tolerant,
because I did not lose my connection.
|
davel
|
|
response 179 of 251:
|
Feb 10 02:06 UTC 2003 |
Earlier, I was dialed in & telnetted out (Grex is the only ISP I've got),
and kept getting hung up (um, frozen, not disconnected - if I pressed ^]
I got immediate response from telnet). A bit later, Jon was on (dialed in)
and kept getting disconnected. The fact that dialins were disconnected
at that point suggests something local to Grex, but possibly in the
network connection to the termserver.
|
jhudson
|
|
response 180 of 251:
|
Feb 10 20:27 UTC 2003 |
I'm getting something similar now.
Telnet connections need 1 minute to login prompt.
Backtalk slogs rather badly too.
Normal (non-cgi) HTTP is fine.
|
keesan
|
|
response 181 of 251:
|
Feb 22 16:27 UTC 2003 |
Pine keeps dumping me when I try to send a mail (several times a week):
ld.so call to undefined procedure _sigpause from 0xef785528
|
russ
|
|
response 182 of 251:
|
Feb 24 00:10 UTC 2003 |
Grex took over 140 seconds to give a login prompt.
|
gelinas
|
|
response 183 of 251:
|
Feb 24 00:47 UTC 2003 |
DNS for grex.org isn't working. Both dns.gibbard and grex.cyberspace
fail:
res_send to server dns.gibbard.org 209.142.209.52: Connection
refused
and
res_send to server grex.cyberspace.org 216.93.104.34: Connection
timed out
|
keesan
|
|
response 184 of 251:
|
Feb 24 00:50 UTC 2003 |
I gave up dialing in but could telnet. Took a bit of a wait.
|
keesan
|
|
response 185 of 251:
|
Feb 24 01:30 UTC 2003 |
This time I waited a couple of minutes and could dial in.
|
russ
|
|
response 186 of 251:
|
Feb 24 02:28 UTC 2003 |
This response has been erased.
|
russ
|
|
response 187 of 251:
|
Feb 24 02:29 UTC 2003 |
It took over 2 minutes to get a login prompt. Again.
I've finally got the lowdown on the mail errors cited above:
> 250 grex.cyberspace.org Hello [209.142.229.137], pleased to meet you
> mail from: nobody@nowhere.net
> 250 nobody@nowhere.net... Sender ok
> rcpt to: russ@cyberspace.org
> 553 russ@cyberspace.org... One generation passeth away, and another
> generation c
> ometh: but the earth abideth for ever.
> data
> 503 Need RCPT (recipient)
> rcpt to: russ
> 553 russ... One generation passeth away, and another generation cometh: but
> the
> earth abideth for ever.
WTF does THAT mean?
|
other
|
|
response 188 of 251:
|
Feb 24 02:53 UTC 2003 |
You've somehow fallen afoul of mdw's bible-quoting trouble filter.
|
gull
|
|
response 189 of 251:
|
Feb 24 04:22 UTC 2003 |
I don't know which filter that is. I know replies I send to a mailing list
I'm on sometimes run afoul of the 'my skin is black upon me' filter if I
don't remove excess spaces from the subject line.
|
tsty
|
|
response 190 of 251:
|
Feb 24 07:49 UTC 2003 |
a bible filter is rather refreshing!
able to get through with cyberspace.org bt not with grex.org.
|
davel
|
|
response 191 of 251:
|
Feb 24 12:40 UTC 2003 |
The Bible quotes mean that Marcus's filtering thinks it's spam. You may be
able to get more specific info on what triggered this from him.
|
davel
|
|
response 192 of 251:
|
Feb 24 12:46 UTC 2003 |
... though (whatever it is) I doubt you'll have any luck getting him to change
it to let your mail through; it's probably keeping lots of real spam from
people.
Hmm. The headers you cite would suggest that there's a problem with the russ
account itself, not with other contents of the message. ("would suggest"
meaning "suggest to me", & I'm not particularly up on this stuff.)
|
russ
|
|
response 193 of 251:
|
Feb 24 22:33 UTC 2003 |
Re #192: My correspondent got that last error from a telnet session
to the smtp port; that may have triggered the spam-trap. However,
it wouldn't account for spurious mailbox-full indications (which may
actually be mail-filesystem full - I don't know).
|
mdw
|
|
response 194 of 251:
|
Feb 25 04:16 UTC 2003 |
"One generation passeth away"... indicates a failure to follow certain
basic parts of RFC 822. I wasn't patient enough to find Russ's
attempts, but I found a spammer using
ntsaga007231.saga.nt.adsl.ppp.infoweb.ne.jp and
adsl-65-71-169-27.dsl.tpkaks.swbell.net who ran afoul of this trying to
send spam to russ.
Most of the spam checks (including this one) don't care which grex
mailbox is named. There is one check for "generic" mailboxes -- ie,
outside machines supplying a RFC 823 To: field of "you@grex.org" and so
forth. Note even this check isn't looking at the forward path where the
mail will actually be sent, it's looking to see if spammers have used a
generic "somewhere at the realm in question" -- and this is no longer so
common since most people have caught on to this.
The "mailbox is full" message is separate logic (well, as separate as it
can be given it's one big monolithic program). It will be generated if
and only if your loginid is named in /var/adm/badmail . A better way to
check to see if your mailbox is full is to say
!umailck
In addition to seeing if you're on the list, this can actually take you
off the list if you were on it, but have managed to free up enough
mailbox space to receive more mail. If your mailbox is full when you
log in, login will spit out a message that includes information on how
to run umailck. There is also an automatic process that will remove you
from /var/adm/badmail if you free up space, but forget how to run
umailck .
|
scott
|
|
response 195 of 251:
|
Mar 2 20:13 UTC 2003 |
Grex was down for several hours - apparently a power blip last night tripped
up our UPS (plans to replace the batteries are in the works).
|
