Hello Jeff,
On 2015-04-30 20:45, Jeff Larsen wrote:
unrtf is version 0.19.3-1.1 from Ubuntu 12.04 LTS repository.
I guess I'll have to see about finding a newer copy and see if that
fixes it.
However, unless I can identify a test case, I won't really know if it's
fixed.
Is there anyway to identify a specific mail message based on the file
name in the unrtf command line that piler launches?
piler assigns an internal id (piler_id) to all messages. In this case
it's
400000005542367a08ccec0c00f0dee541ab. Chances are that you have some
files
under /var/piler/tmp starting with such name.
Unfortunately it may occur that some external helpers (eg. unrtf) can't
handle
the given attachment properly, and they freeze. To mitigate such cases
the parser
calls them with the timeout binary to make sure either they finish or
die soon.
For 1.1.0 you may check if you compiled with --with-plugin-timeout
option.
Note that the master branch uses a different approach: to fork the
external
helper, and set the alarm for 20-30 sec which terminates the helper if
can't
finish in a timely manner.
Anyway it's worth to try fixing unrtf if a newer version is available.
Janos
Jeff
On Thu, Apr 30, 2015 at 11:37 AM, André Peters
<[email protected]> wrote:
Hi,
I am on my cell phone, so I will keep it short.
I see there were bug reports for unrtf about this issue a few years
back.
The devs answered in December 2014 that they fixed it, one is here:
http://savannah.gnu.org/bugs/?34677
Can you check your version? You can get the sources right here:
http://ftp.gnu.org/gnu/unrtf/?C=M;O=A
Regards,
André
Am 30. April 2015 17:27:13 MESZ, schrieb Jeff Larsen
<[email protected]>:
In the last 24 hours I've been seeing the load and CPU on my Piler
system get out of control. I'm finding one or more processes owned by
the piler user with the command "unrtf" that is pegging the CPU.
The man page says this a converter for Rich Text Format. I would
guess
that perhaps piler is decoding attachments so they can be searchable.
That's all well and good, but how to I track down these messages that
unrtf is choking on? And then what do I do with them?
The ps command shows me this:
/usr/bin/unrtf --text 400000005542367a08ccec0c00f0dee541ab.a1.bin
I can kill the process, but eventually the problem returns.
Is piler returning to finish up the message from the killed process,
or do we have a series of problematic attachments coming in?
I am suspicious of a new contact of mine that is sending mail with
the
dreaded winmail.dat attachments. I've given
her info on how to stop
it, but she may not cooperate. It's not something I've seen much of
lately, maybe she has a really old Outlook version. In any case,
that's just my guess at the root of this issue.
Full disclosure: The piler store folder is on NFS, which sometimes
gives us trouble, but this particular issue is a new one. I've been
running piler for a year or more.
Piler version is 1.1.0.
Thanks,
Jeff
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
gesendet.
