Could you discribe your problem some more? nss-3.21.0 is pretty new.
Although it's tested in house, there could be something slipped...
If you still keep the error/access logs of 389-ds-base and share them
with us, it'd be a great help, too.
On 04/08/2016 05:49 AM, Paul Whitney wrote:
We upgraded our CentOS 6 build yesterday and managed to break our
389DS service. We have isolated the problem to a package:
nss-3.21.0-0.3. When we role back the update to a previous version
the 389ds service works fine. Has anyone else experienced this?
Paul M. Whitney
Sent from my browser.
389 users mailing list