|
Grex > Helpers > #134: Grex System Problems - Summer 2004 |  |
|
| Author |
Message |
| 25 new of 286 responses total. |
keesan
|
|
response 164 of 286:
| 
Sep 3 13:48 UTC 2004 |
Have I set up .procmailrc wrong? Why it is trying to do something it should
not do? MAIL=/var/spool/mail/k/e/keesan is my first line of the filter, which
is no longer working to catch spams. Maybe I broke it? But I was frequently
getting these lock messages before and about 1-2 spams a day that should have
been caught were not, and now ALL of the spams are getting through (8 in the
last 5 hours or so). I would appreciate if you could take a look at the
filter, or I could post the complete (verbose) log file for one spam. I am
wondering if this is something to do with the grex revival (a bug).
|
keesan
|
|
response 165 of 286:
|
Sep 3 14:55 UTC 2004 |
I checked my log and every single message (none of which were caught by the
filter) says I had a lock failure. I think previously only the ones that the
spam filter missed said that. Has something changed at grex or did I mess
up my filter? .procmailrc
|
keesan
|
|
response 166 of 286:
|
Sep 3 20:04 UTC 2004 |
Here is a typical entry in my log file
procmail: Lock failure on "/var/spool/mail/k/e/keesan.lock"
From dmawllet@hotmail.com Fri Sep 3 10:54:30 2004
Subject: Cailis for $6 ($3 a dose)
Folder: /var/spool/mail/k/e/keesan 925
When I get the lock failure, the spam is not filtered to /dev/null as it
should be. What is causing the lock failure and how can I (or staff) fix
it?. This is 10 times as bad as it was before the grex disaster.
Todd, are you having spam filter problems (you use my filter, I think).
|
keesan
|
|
response 167 of 286:
|
Sep 3 20:17 UTC 2004 |
I think I caught the problem - I am sending anything Received from ... grex
or cyberspace to my inbox and this part of the header includes not only the
sender's but also the recipient's address. Sorry to bother people but I still
don't understand the 'lock' business.
|
gelinas
|
|
response 168 of 286:
|
Sep 4 02:39 UTC 2004 |
According to the man page for procmailrc, the format of a block is:
:0 [flags] [ : [locallockfile] ]
<zero or more conditions (one per line)>
<exactly one action line>
In some cases, you do not have a newline immediately following the
second colon. For example:
:0:
* ^Received:.*zillion
/dev/null
Has a couple of spaces at the end of the first line. I don't know that the
spaces are significant, since I haven't tried to correlate the messages that
cause lock errors with specific blocks in your .procmailrc. Neither have
I looked at every block to see if you have specified a lockfile somewhere.
|
keesan
|
|
response 169 of 286:
|
Sep 4 05:58 UTC 2004 |
Thanks, I will delete spaces on a line after the :. How did you find them?
Is there some way to view them with pico?
Can I put all the lines beginning with * ^ in between just a single
I have no idea how to specify a lockfile.
|
tpryan
|
|
response 170 of 286:
|
Sep 4 23:08 UTC 2004 |
I'm no expert, but my the man, as I read the notation, if a
locallockfile is used, the colon must precede it. That structure is
optional, so the trailing colon should probably be removed, as it may
be thinking your locallockfile is named ' '.
|
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.
|