On Mon, 2009-06-08 at 08:06 +0900, Randy Bush wrote: > where is exim_tidydb called? on freebsd 8-current, a number of systems > running amd64 and i386, i have not been able to solve the following:
I've no idea where you're calling it from - you might have to follow your nose on that, since it's clearly a daily cron job... > Jun 6 00:20:06 work kernel: swap_pager_getswapspace(4): failed > Jun 6 00:20:06 work kernel: swap_pager_getswapspace(16): failed > Jun 6 00:20:06 work kernel: swap_pager_getswapspace(14): failed > Jun 6 00:20:06 work kernel: swap_pager_getswapspace(16): failed > Jun 6 00:20:06 work kernel: swap_pager_getswapspace(3): failed > Jun 6 00:20:06 work kernel: swap_pager_getswapspace(16): failed > Jun 6 00:20:06 work kernel: swap_pager_getswapspace(16): failed > Jun 6 00:20:06 work kernel: pid 12159 (exim_tidydb), uid 0, was killed: > out of swap space > > and i was looking for where exim_tidydb was run to see if commenting it > out would move the problem. i assumed exicyclog, but if it is there it > is too subtle for first cuppa. No, it'll be a separate task. If you can afford it, you could simply delete the retry DB file and let it start growing again to see whether or not a recent update (as previously discussed in another thread!) has broken the DB file format. If it doesn't report this error after that, job done. Graeme -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
