>
> we have another host with same version and suppose same cfg but never saw the
> error,
>
> [24/Jun/2020:09:22:54.687024072 -0700] - ERR - Security Initialization -
> _conf_setallciphers - Failed to get the default state of cipher (null)
I'm curious - how did you make a host with the same
> On 24 Jun 2020, at 16:43, DaV wrote:
>
> Yes, it is.
> So I have to change the UidNumber to 5007 on AD side manually after the first
> winsync.
> emm, not convenient.
>
Yep ... I think DNA was designed with different use cases in mind :(
Your best bet may to be avoiding DNA completely,
I wonder if there is some sssd configuration issue going on? Honestly I'm not
very experienced with this part of the code base and these interactions ...
> On 23 Jun 2020, at 18:19, Nicolas Martin wrote:
>
> I have installed 389 server on its own; I'm not using FreeIPA.
>
> On Mon, Jun 22,
I will let others confirm, but the message "_conf_setallciphers - Failed to
get the default state of cipher" may not be an actual error, but more a
warning that could be ignored, as the the default ciphers are
configured later, per the log entries provided.
Could you add the nss package version,
Our new DS env is running:
389-ds-base-libs-1.3.9.1-10.el7.x86_64
389-ds-base-1.3.9.1-10.el7.x86_64
After DS was upgrade to above version seeing this error when restarting the DS,
we have another host with same version and suppose same cfg but never saw the
error, please advise a fix for this
Yes, it is.
So I have to change the UidNumber to 5007 on AD side manually after the first
winsync.
emm, not convenient.
Sincerely,
--
DaV
On Wed, Jun 24, 2020, at 09:56, William Brown wrote:
>
>
> > On 23 Jun 2020, at 17:08, DaV wrote:
> >
> > Hi,
> > I find the DNA Plugin NextValue
