1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

clamdscan error reports from qmail-scanner

Discussion in 'Plesk for Linux - 8.x and Older' started by spiritquest, Sep 26, 2005.

  1. spiritquest

    spiritquest Guest


    I wanted to ask some of the more experienced members here if they could help me understand this error message in a little more detail.

    I have been running qmail-scanner / clamav using clamd and spamassasin successfully for a approx two months now. I have, however, been experiencing "outages" in the mail service (although courier-imap and qmail are active) recently.

    Originally i was forced to reboot the server to fix the issues, and this does fix the issue. But looking at the qmailscanner logs has shown that the messages have been showing these errrors:

    There are threads talking about permissions, but I don't think this applies to my case, as it works for days at a time .. ?

    My main problem is that there were messages scanned in the log that have not yet shown up and I am worrying that these messages have somehow been lost, I am not sure how to check if this is the case.

    I am considering adding a clamd restart cron job when my clients sites and db's are backed up with my nightly cron job to see if that fixes any clamd memory problems ..

    If any one has any links or could explain why the system may be reporting these errors I would greatly appreciate it.

    Kind Regards,

  2. spiritquest

    spiritquest Guest

    So the messages eventually arrived, but I am worried about the memory errors.
  3. spiritquest

    spiritquest Guest

    I've found that clamd occassionally crashes, as it did alst night ... I ran /sbin/service clamd restart and it failed to shutdown but started ok. Which answered my question as to why emails hadn't arrived for an hour or so.

    I have set up a cron job /sbin/service clamd status every hour, so i can monitor its activity.