The Doctor: > On Sun, May 26, 2013 at 06:37:17AM -0600, The Doctor wrote: > > On Sun, May 26, 2013 at 08:04:47AM -0400, Wietse Venema wrote: > > > The Doctor: > > > > All right, I have been getting a lot of irregular throttling > > > > since Saturday midnight. > > > > > > > > May 25 08:05:53 doctor postfix/postscreen[29851]: fatal: set DB cache > > > > size 131072: Invalid argument > > > > > > Has your Berkeley DB library been updated? Perhaps you can revert > > > the update. > > > > > > Apparently, their set_cachesize() function now returns an error > > > when Postfix sets the cache size. > > > > > > This code has not changed since Postfix 2.0, more than 10 years ago: > > I take it back. > > Also the BDB is 5.3.21 which is the latest. > > Here are the logs from the latest backfire
That is the same Berkeley DB error. You can stop posting these now. You may make more progress if you can back out the "improved" Berkeley DB library. You may also play with berkeley_db_read_buffer_size. The Berkeley DB documentation promises that they accept buffer sizes of 20kB or more, and their default is 256kB. If someone has screwed up Berkeley DB, then perhaps it helps to specify berkeley_db_read_buffer_size of 262144 (262144 = 256*1024). Hopefully they still accept that. http://docs.oracle.com/cd/E17076_02/html/api_reference/C/dbset_cachesize.html Wietse
