Hi, > On Nov 11, 2017, at 3:06 AM, J Doe <gene...@nativemethods.com> wrote: > > Hello, > > I have an admittedly basic question, but I have been trying to troubleshoot > this for a while with no success. > > I have enabled postscreen(8) on Postfix 3.1 and receive a warning in > mail.log: > > “close database /var/spool/postfix/var/lib/postscreen_cache.db: No such file > or directory (possible Berkeley DB bug)” > > A quick Google of this returns that this is caused on Debian systems that run > Postfix in a jail (which matches my system). The most recent post regarding > this appears to be here: > https://tech.feedyourhead.at/content/postscreen_cache_db_no_such_file > > As per the blog posting, I stopped Postfix and created a directory in the > jail for the postscreen_cache.db: > > $ sudo systemctl stop postfix.service > $ sudo mkdir -p /var/spool/postfix/var/lib/postfix > > I moved the postscreen_cache.db file to this location: > > $ sudo mv /var/lib/postfix/postscreen_cache.db > /var/spool/postfix/var/lib/postfix > > I set the permission and ownership on this file: > > $ sudo chown postfix:postfix > /var/spool/postfix/var/lib/postfix/postscreen_cache.db > $ sudo chmod 0660 /var/spool/postfix/var/lib/postfix/postscreen_cache.db > > I checked that the postfix user can access this file: > > $ sudo -u postfix namei -m > /var/spool/postfix/var/lib/postfix/postscreen_cache.db > > I *DIFFER* from the blog in that I do not create a symbolic link - I use the > Postfix main.cf configuration parameter below: > > postscreen_cache_map = > btree:/var/spool/postfix/var/lib/postfix/postscreen_cache > > I then start Postfix: > > $ sudo systemctl start postfix.service > > When I check: /var/spool/postfix/var/lib/postfix I can see that > postscreen_cache.db is updated as time progress, but I still get the warning > about not being able to close the postscreen_cache.db database.
An update on this initial e-mail ... Checking mail.log, Postfix outputted a helpful warning about me attempting the following in main.cf: postscreen_cache_map = btree:/var/spool/postfix/var/lib/postfix/postscreen_cache Postfix notes that the path I created in the jail does not point to the expected Postfix data directory. It then displayed that the data directory was: /var/lib/postfix My initial response was to update the data_directory in main.cf to point to the jail path: data_directory = /var/spool/postfix/var/lib/postfix ...however this caused other parameters to display warnings because the jail path I specified was not expected. I checked the default setting: $ postconf | grep -i data_directory ...which revealed that it was: /var/lib/postfix I then tried setting the postscreen_cache_map to this in main.cf: postscreen_cache_map = btree:/var/lib/postfix/postscreen_cache ...but received the original warning message when postscreen(8) attempted to close the postscreen cache map. I went back and moved the postscreen_cache.db to the jail location and created a symbolic link (as per the instructions in the blog I referenced in the original e-mail): $ sudo mv /var/lib/postfix/postscreen_cache.db /var/spool/postfix/var/lib/postfix $ sudo ln -s /var/spool/postfix/var/lib/postfix/postscreen_cache.db /var/lib/postfix/postscreen_cache.db ...and restarted Postfix . . . and the warnings from postscreen stop (success) ! Is this really the only way to fix this, though ? This feels a bit like a workaround as opposed to the “correct” solution (assuming that there is a “more correct” solution). Thanks, - J
