Re: attempt to open lmdb:postscreen_cache with both "open" lock and "access" lock

2022-03-17 Thread Stefan Foerster
Hello Wietse, * Wietse Venema : Stefan F?rster: Mar 17 13:24:40 servername postfix/proxymap[166]: panic: dict_open: attempt to open lmdb:/var/lib/postfix/postscreen_cache with both "open" lock and "access" lock Please do not open the postscreen cache through the proxymap daemon. It cannot

Re: attempt to open lmdb:postscreen_cache with both "open" lock and "access" lock

2022-03-17 Thread Wietse Venema
Stefan F?rster: > Mar 17 13:24:40 servername postfix/proxymap[166]: panic: dict_open: attempt > to open lmdb:/var/lib/postfix/postscreen_cache with both "open" lock and > "access" lock Please do not open the postscreen cache through the proxymap daemon. It cannot meet postscreen performance

attempt to open lmdb:postscreen_cache with both "open" lock and "access" lock

2022-03-17 Thread Stefan Förster
Hello World, I'm running Postfix 3.6.4 in a container on Alpine 3.15 main. After a bit of time, I'm starting to get error messages like that: #v+ Mar 17 13:24:40 servername postfix/postscreen[164]: CONNECT from [167.248.133.120]:52756 to [172.17.13.3]:25 Mar 17 13:24:40 servername