This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dead scanner blocks the spool queue

We have been encountering this issue consistently over the past three years. Whenever we receive emails with large scanned PDF files, it causes a blockage in the spool work queue. As a result, the CPU usage spikes to 100%. Upon inspection of the files in the /chroot-smtp/spool/work directory, we often find "dead_scanner" files present. In some cases, the entire queue stops processing, resulting in a backlog of thousands of emails and a complete halt of inbound and outbound email functionality.

We have attempted various solutions, including adjusting the scanner_timeout to 30 and 60, as well as experimenting with different values for max_pool ranging from 5 to 10. However, none of these attempts have successfully resolved the issue.

Did anyone else here encounter a similar issue or have insights on how to address this problem? We have typically resorted to manually removing the "dead_scanner" file and its related files, followed by a server restart to resume queue processing. Any suggestions or assistance would be greatly appreciated in resolving this recurring issue.



This thread was automatically locked due to age.
Parents Reply Children
No Data