Re: Command died with status 134

Ian Zimmerman wrote on Thu-06-Aug 15  2:43AM
> On 2015-08-05 09:16 +0200, Eric Smith wrote:
> 
> > Command died with status 134: "/usr/bin/procmail -a
> > "$EXTENSION"". Command output: Aborted
> 
> So procmail dies from the SIGABORT signal.  AFAIK that can only happen
> if a program calls abort(2) of its own volition.  So it should be
> possible to isolate all the possibilities by looking at procmail
> source.  To be sure, there may be many, probably in reaction to any
> syscall failure.  But I would imagine in most of those cases procmail
> would log some other info to stderr or the logfile.  If you don't see
> anything specific in the logfile you can just focus on abort() calls not
> preceded by such log activity.
> 

I find the following in my log file, which corresponds to a bounce
event:

 Subject: RE: Blah blah blah
  Folder: gmail-forwarding-trap                   13037
procmail: [11995] Mon Aug 10 17:37:05 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:37:13 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:37:21 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:37:29 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:37:37 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:37:45 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:37:53 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:01 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:09 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:17 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:25 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:33 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:41 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:49 2015
procmail: Locking "uudeview2.lock"
procmail: [11995] Mon Aug 10 17:38:57 2015
procmail: Locking "uudeview2.lock"
procmail: [12269] Mon Aug 10 17:38:57 2015
procmail: Assigning "LOG=
LOG ==============   TOP OF PROCMAILRC  ===========

[The above line is a log entry signifying the next invocation of procmail]

Here is the delivery block, where the `uudeview2.lock' file is defined in my procmailrc:

{
   :0 c:
   $DEFAULT
   :0c:
     {
      foo=`rm /tmp/last`
      :0:
      /tmp/last
     }
   :0f
   * ! ^X-Forwarded-To:.*<some-special-signifier-in-my-gmail-forwards>
   * ! ^X-Forwarded-For:.*<some-special-signifier-in-my-gmail-forwards>
   ! [email protected]
   :0wc:uudeview.lock
   | /usr/bin/uudeview -i +a  -p /home/eric/ -e .html -e .txt -e .001 - 
   :0wc:uudeview1.lock
   | /usr/bin/uudeview -i -p /www/eric/existing_dir -e .html -e .txt -e .001 -
   :0w:uudeview2.lock
   | sleep 1;chmod 644 /www/eric/existing_dir/*
   :0
   | for i in /_/*.zip;do unzip -f -d /_/ $i;done
   :0:
   /dev/null
 }

The only thing I changed recently is the X-Forwarded-To and X-Forwarded-For lines
to prevent occasional mail loops to gmail and back.

The above has worked to my satisfaction for years and only since the changes to
these filters, am I getting occasional error messages to senders, but procmail
is delivering their mail to me (when it crashes).

Thanks for any advice.

Eric