Difference between revisions of "No Free Workers Error"
From Roaring Penguin
Line 2: | Line 2: | ||
If you have not already, you should install PgBouncer as per Appendix G in the Administration Guide. This can greatly increase database performance. | If you have not already, you should install PgBouncer as per Appendix G in the Administration Guide. This can greatly increase database performance. | ||
− | You can increase the maximum number of MIMEDefang processes by editing /etc/mail/canit/canit.conf and adjusting the: | + | You can increase the maximum number of MIMEDefang processes by editing <code>/etc/mail/canit/canit.conf</code> and adjusting the: |
mx_maximum= | mx_maximum= | ||
− | setting in the [mimedefang] section | + | setting in the <code>[mimedefang]</code> section. Make sure that you don't increase the maximum too much; each process uses about 50MB of memory. Also, the sum of mx_maximum values cluster-wide should not exceed the max_connections PostgreSQL setting (if you are not using PgBouncer) or should not exceed it by a factor of more than 5 (if you are using PgBouncer). |
<div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div> | <div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div> | ||
[[category:All]][[category:Errors]] | [[category:All]][[category:Errors]] |
Latest revision as of 10:25, 20 September 2018
If you have not already, you should install PgBouncer as per Appendix G in the Administration Guide. This can greatly increase database performance.
You can increase the maximum number of MIMEDefang processes by editing /etc/mail/canit/canit.conf
and adjusting the:
mx_maximum=
setting in the [mimedefang]
section. Make sure that you don't increase the maximum too much; each process uses about 50MB of memory. Also, the sum of mx_maximum values cluster-wide should not exceed the max_connections PostgreSQL setting (if you are not using PgBouncer) or should not exceed it by a factor of more than 5 (if you are using PgBouncer).