Your message dated Mon, 11 Feb 2008 15:33:21 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#463228: error spawning sub-processes (returning 255)
has caused the Debian Bug report #463228,
regarding error spawning sub-processes (returning 255)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
463228: http://bugs.debian.org/cgi-bin//463228
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: crm114
Version: 20060704a-5
Severity: normal
I've started having problems like this:
/usr/bin/crm: *ERROR*
This program tried a shell command that didn't run correctly. The command was
>>mkdir reaver_cache/empty << and returned exit code 255 .
Sorry, but this program is very sick and probably should be killed off.
This happened at line 1080 of file /home/jon/.crm114/mailreaver.crm
The line was:
--> syscall () () /mkdir :*:text_cache:\/empty /
I'm not sure why the syscall is failing, it does so only
sporadically it seems, but that's not the issue I'm
reporting here.
The problem is, mailreaver.crm doesn't appear to be
returning a non-zero exit code, so I can't catch the mails
that are failing via procmail. The following recipe works:
:0
* ^Subject: eicuhais
{
:0fw
| /bin/false
:0 e
$HOME/Maildir/to-filter/
}
("eicuhais" is just a token from pwgen to test this with)
The following does not:
:0fw: $HOME/.crm114/crm114.procmail.lock
| $HOME/.crm114/mailreaver.crm -u $HOME/.crm114/
:0 e
$HOME/Maildir/to-filter/
[EMAIL PROTECTED]:~$ gunzip -c /usr/share/doc/crm114/examples/mailreaver.crm.gz
| md5sum -
c60f5d6ab9f344b7545ad534a6ea29a1 -
[EMAIL PROTECTED]:~$ md5sum .crm114/mailreaver.crm
c60f5d6ab9f344b7545ad534a6ea29a1 .crm114/mailreaver.crm
--- End Message ---
--- Begin Message ---
On Mon, Feb 04, 2008 at 11:51:22AM +0000, Jon Dowland wrote:
> The errors continue to be logged in my procmail log, but there's no
> evidence that mkdir was actually called. I suspect that the fork()
> called by the system() call is failing, perhaps resource constraints on
> this machine (which is a bit light on RAM but has lots of swap to
> compensate).
My mail system went on to start failing to spawn crm114 at all, I ended
up adding 512M swap and that cured both problems. I suspect the above
conclusion is correct.
I'll therefore close this report, I don't suppose there's much more
crm114 could do in this situation, I just need to sort my mail server
out :-)
Thanks,
--
Jon Dowland
--- End Message ---
