Thousands of emails stuck in /var/piler/tmp/

Issue #49 resolved
Former user created an issue

Comments (13)

  1. Janos SUTO repo owner

    try the latest master branch. Someone else reported a very similar bug, and it's been fixed. Also please report the following output:

    ldd --version gcc -v 2>&1|tail -1

  2. Robert Chavers

    ldd --version

    ldd (Ubuntu EGLIBC 2.15-0ubuntu10.3) 2.15

    gcc -v 2>&1|tail -1

    gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

    I just upgraded to .22, but this problem has been happening ever since I installed piler a few months ago. I'll pull the master branch if there is a bug fix since .22 was released.

    Anyway, thanks for the great software. So far it is working great!

  3. Janos SUTO repo owner

    OK, if you still encounter a buffer overflow (you can test it with the pilertest utility in the source directory), then please reopen this issue.

  4. Robert Chavers

    I pulled the master branch and tested with both debug and pilertest. The problem still exists. I can send you a copy of some of the emails if you want.

  5. Robert Chavers

    Email with attachment has been sent.

    Also, once this issue is fixed, what do I do with the emails in the tmp folder? Should I just delete them or should I run them through piler again?

  6. Janos SUTO repo owner

    I've checked all of these emails, and on an ubuntu host (glibc 2.15 + gcc 4.6.3) I couldn't reproduce the problem with build >= 739. Btw. have you replaced the libpiler.so* files, too?

  7. Robert Chavers

    You are right, replacing the lib files fixed the problem.

    I had run configure and did a make to test the emails, but did not actually "make install" the new version. After running "make install", the emails are working correctly now.

    What should I do with all the left over tmp files?

  8. Janos SUTO repo owner

    you can remove them. Be careful and remove only the stale files in the directory. Or if you can afford stopping piler, then stop it, and issue an rm /var/piler/tmp/*, then start piler again.

  9. Log in to comment