|
Grex > Helpers > #134: Grex System Problems - Summer 2004 |  |
|
| Author |
Message |
| 25 new of 286 responses total. |
cmcgee
|
|
response 171 of 286:
| 
Sep 4 23:10 UTC 2004 |
What's the deal with Grex being off the net?
|
krj
|
|
response 172 of 286:
|
Sep 5 00:56 UTC 2004 |
Grex remains off the net. Sigh.
|
gelinas
|
|
response 173 of 286:
|
Sep 5 01:54 UTC 2004 |
Sindi, I don't know how to find lines that end in ": " in pico. I used vi,
and searched for ": "
I don't know why grex is off the net; it is reachable from other machines
on the network in the Pumpkin, and those machines are reachable from the
Internet. I tried rebooting and a few other things that didn't help.
|
keesan
|
|
response 174 of 286:
|
Sep 5 14:33 UTC 2004 |
I searched with pico Ctrl-W for space-space and found a lot of places with
double spaces after the colon and deleted the spaces. I think you are saying
that the spaces are being misinterpreted and that Tim is saying that I don't
need the second colon - is that true? Joe, thanks for working on all our
problems.
|
bhoward
|
|
response 175 of 286:
|
Sep 5 16:50 UTC 2004 |
Grex was never off the net but something broke within our ISP's
routing tables for a time cutting off direct access. Seems to
have recovered in the last hour or so.
|
tpryan
|
|
response 176 of 286:
|
Sep 5 17:15 UTC 2004 |
If you are not sure you can subsitute space, multiples of, at the end
of a line with nothing: s/ *$// (?).
|
blaise
|
|
response 177 of 286:
|
Sep 5 18:27 UTC 2004 |
You do need the trailing colons because your incoming mail file is in
mbox format, so you need to prevent multiple processes from writing to
it at the same time. Just make sure that there are no trailing spaces
after the colons.
|
twenex
|
|
response 178 of 286:
|
Sep 5 18:32 UTC 2004 |
Procmail's syntax sounds as fascist as JCL.
|
janc
|
|
response 179 of 286:
|
Sep 5 21:46 UTC 2004 |
As Bruce said, we had some down time probably because our ISP modified our
routing table to route Grex off into cloud cuckoo land. After Joe and Walter
each spent some time poking at Grex to try to figure out why it wasn't on the
net, I began to suspect the ISP and phoned them. They said they'd ask their
engineer to look into it, and after a while connectivity came back.
|
cmcgee
|
|
response 180 of 286:
|
Sep 6 01:31 UTC 2004 |
Is there some reason that mail is still backed up? Someone just sent me an
email and it's been more than 30 mins and it hasn't arrived. Do we have a
mail backlog or is there a problem at the sender's end?
|
keesan
|
|
response 181 of 286:
|
Sep 6 03:22 UTC 2004 |
Thanks Joe - I was still getting locallockfile messages so I hunted for
colon-space and removed some of those. But my spam filter missed this:
From apsmith@aps.org Sun Sep 5 23:19:23 2004
Date: Sun, 5 Sep 2004 21:09:22 -0400
From: apsmith@aps.org
To: keesan@cyberspace.org
Subject: nqmqpnpxdbe
Dear user keesan@cyberspace.org,
We have found that your account has been used to send a huge amount of junk
email messages during the recent week. We suspect that your computer had been
infected by a recent virus and now contains a trojaned proxy server.
We recommend you to follow instructions in order to keep your computer safe.
Best regards,
cyberspace.org technical support team.
[Part 2, Application/OCTET-STREAM (Name: "INSTRUCTION.EXE") 39KB]
[Unable to print this part]
-----
I wonder why the technical support team here could not find a more
spellable subject line and why they chose to send out the fix in a DOS
format.
|
mcnally
|
|
response 182 of 286:
|
Sep 6 05:38 UTC 2004 |
Of course it's a trojan horse, and a really lame one at that.
The author apparently couldn't even forge the headers to appear
as though the mail was coming from the domain it claimed to
speak for..
|
krj
|
|
response 183 of 286:
|
Sep 9 04:26 UTC 2004 |
Party people are experiencing connection lockups and/or disconnects.
See the party log for the last hour or so for what meager evidence
there is.
|
keesan
|
|
response 184 of 286:
|
Sep 9 05:07 UTC 2004 |
I got several long lockups while dialed into grex and telnetted elsewhere.
2 min.
|
bru
|
|
response 185 of 286:
|
Sep 9 05:43 UTC 2004 |
Ssytem would not let me in thru telnet. But would let me telnet from the
homepage.
|
mcnally
|
|
response 186 of 286:
|
Sep 9 16:43 UTC 2004 |
Grex was unreachable on my first attempt this morning and I just had a
~3 minute lag while entering this response. Something is up with the DSL.
|
drew
|
|
response 187 of 286:
|
Sep 9 18:57 UTC 2004 |
I'm in through dialup now. The internet connection does not answer, and there
are few people online.
|
aruba
|
|
response 188 of 286:
|
Sep 9 21:30 UTC 2004 |
It looks like Grex is off the net.
|
albaugh
|
|
response 189 of 286:
|
Sep 9 23:25 UTC 2004 |
I'm sorry, I certainly won't blame anyone, but this unreliability of grex is
becoming intolerable. If things are going to continue like this indefinitely,
then that constitutes the beginning of the end...
|
i
|
|
response 190 of 286:
|
Sep 9 23:45 UTC 2004 |
I just "rebooted" the DSL modem again after finding grex off the net, that
seems to have "fixed" things. The "slowly goes bad" DSL connection issue
is an old issue, easily fixed with a few quick button pushes.
More bothersome to me is that i tried dialing in before coming down to
this-here pumpkin...and got the greeting from the terminal server, but
NOT the grex login prompt...leading to a preliminary mis-diagnosis of an
actual grex crash. Has anyone else seen problems getting all the way to
the grex login prompt when grex really is alive?
|
cmcgee
|
|
response 191 of 286:
|
Sep 10 00:20 UTC 2004 |
It just took 1.5 mins between the dial-in welcome screen and the login:
prompt.
|
aruba
|
|
response 192 of 286:
|
Sep 10 01:02 UTC 2004 |
Right - I had the same experience as Colleen. I suspect the ssh daemon was
trying to do something (a reverse lookup?) which didn't work because the net
connection was down, and it had to time out before it would let me lot in.
|
gelinas
|
|
response 193 of 286:
|
Sep 10 01:41 UTC 2004 |
hmm.... Load seems within normal limits. But it did take a while to get
a login prompt using ssh. Once I got the prompt, though, things seemed
to work fine. traceroute looks normal, as does top.
I dunno.
|
bru
|
|
response 194 of 286:
|
Sep 10 08:13 UTC 2004 |
just tried telnetting in and failed.
|
i
|
|
response 195 of 286:
|
Sep 10 09:36 UTC 2004 |
Ditto #194, it took a while to get the login: prompt via dial-in.
Wish i knew how to restart telnetd...or enough to deduce what the
problem really is.
|