Hello Michael,
I've just reviewed the code, and found the matching part for each
open() and fopen() calls. Can you provide more clues, error messages,
etc. on the matter?
Janos
On 2016-01-14 16:57, Michael Volz wrote:
I kind of solved the problem. The problem was that the pilerimport
process had too many open file handles. I could finish the process by
increasing the limit. But I still guess it's not "right" of pilerimport
to keep all those files open, is it?
Am 04.01.2016 um 16:40 schrieb Michael Volz:
The files pilerimport complains about (e.g. 9964-imap-10014.txt) do
exist in the folder and contain email messages.
Am 04.01.2016 um 16:31 schrieb Michael Volz:
Hey everybody!
I have problems with pilerimport. I am running several imports from
imap
folders and I am using the folder feature. After importing
successfully
for some time (several hours), pilerimport begins many of the
following
errors:
error importing '9964-imap-10014.txt'
failed to import: 9964-imap-10015.txt (id:
40000000568a8e0a3a35d13c0068f88e0e35)
There are no errors in maillog or other logs. What could be the
problem?
I invoke pilerimport as root, but in a directory that belongs to the
piler user. There are about 250000 files in this folder. The command
line is like that:
pilerimport -i server -u user -p password -P port -f imap_folder_name
-F
piler_folder_name
or:
pilerimport -i server -u user -p password -P port -R
Thanks for any help!
Michael
