>> 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 > /usr/local/etc/periodic/daily/150.exim-tidydb
thanks > But IMNSHO, running out of swap space calls for providing more swap space > (and/or RAM). of course. the only problem is that these a 4G machines, with 8G of swap, and not a lot happening. like no problems building kernel, world, ... > Killing off tidydb could be expected to make the problem worse over > time, not better, as an ever-growing DB size has to be waded through. that an even kinkier thing. these machines have no email other than shipping their nightly logs out. the database is negligible. if i delete it all before the nightly run that crashes, it still crashes. Graeme Fowler: > 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!) running exim-4.69-3. this is why i wanna try just not running it to see if anything else starts to act funny. i am wondering about things like compiler bugs. but old compiler geeks suspect that path way too often. randy -- ## 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/
