[389-users] PassSync issue

from windows AD to 389ds(one way), no any other data.Could you please provide some advice? Thanks in advance! Sincerely, -- DaV ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le

[389-users] Re: can't start dirsrv-admin service after reboot

console.conf console.conf.bkp 35,36c35,36 < User dirsrv < Group dirsrv --- > User nobody > Group nobody Sincerely, -- DaV On Tue, Oct 9, 2018, at 07:18, DaVwrote: > Hi Mark, > Thanks for your reply. > In fact, I follow this link and resolve missing config file > > https://bugz

[389-users] Re: can't start dirsrv-admin service after reboot

)$[Wed Oct 10 05:43:20.562775 2018] [:debug] [pid 3447:tid 140517964691584] mod_admserv/mod_admserv.c(2620): [3447] adminsdk [0xbogus %p flag 0 in output file there is pid of 3447, but I can't find this pid. Sincerely, -- DaV On Tue, Oct 9, 2018, at 05:46, Mark Reynolds wrote: > > On 1

[389-users] can't start dirsrv-admin service after reboot

entered failed state.Oct 03 17:34:52 vdi-ds-1 systemd[1]: dirsrv-admin.service failed. Sincerely, -- DaV ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code

[389-users] Windows Sync Agreement issue

20/Aug/2019:08:50:59.533268105 +0800] - WARN - NSMMReplicationPlugin - > prot_stop - Incremental protocol for replica "agmt="cn=389ds" (tc-dc-2:389)" > did not shut down properly. > [20/Aug/2019:09:01:00.155477769 +0800] - WARN - NSMMReplicationPlugin - > prot_stop

[389-users] Re: Windows Sync Agreement issue

it at all) 4. The time interval sync from AD to 389ds controlled by WinSyncInterval, it's 5 minutes default. But I can't find any error log on my 389ds server, the sync doesn't happen. Sincerely, -- DaV On Tue, Aug 27, 2019, at 08:54, William Brown wrote: > > > > On 27 Aug 2019, a

[389-users] Re: Windows Sync Agreement issue

sers,dc=example,dc=com > nsDS5ReplicaBindMethod: SIMPLE > nsDS5ReplicaCredentials: > *oneWaySync: fromWindows* > nsds50ruv: {replicageneration} 5d5a75d8 > nsDS5ReplicaUpdateSchedule: 1211-1220 4 > Sincerely, -- DaV On Tue, Aug 27, 2019, at 02:18, Mark Reynolds wrote:

[389-users] Re: Windows Sync Agreement issue

win2k16 can't open. BTW, I have many windows sync agreements, but I only see one agmt debug log. Sincerely, -- DaV On Thu, Aug 29, 2019, at 07:23, William Brown wrote: > > > > On 27 Aug 2019, at 11:25, DaV wrote: > > > > OK. > > 1. I have win2016 AD and 389ds

[389-users] Re: Windows Sync Agreement issue

the "Initiate full Re-synchronization" on the console to sync from AD to 389ds. Sincerely, -- DaV On Mon, Aug 26, 2019, at 06:58, William Brown wrote: > > > > On 23 Aug 2019, at 19:38, DaV wrote: > > > > Hi all, > > For OneWaySync, AD to 389ds. &g

[389-users] Re: Windows Sync Agreement issue

ndows_inc_run - agmt="cn=chuxun" (tc-dc-2:389): Replica has > no update vector. It has never been initialized. > [21/Aug/2019:08:56:59.581808252 +0800] - WARN - NSMMReplicationPlugin - > windows sync - windows_inc_run - agmt="cn=wangxun" (tc-dc-2:389): Replica has >

[389-users] 389ds automount issue

mple.com on client-side. I don't know whether this is a bug. Just write this to let you know. Thanks! My solution is: change the 389ds server-side using nisMapEntry: ldap tc-389ds.example.com. Sincerely, -- DaV ___ 389-users mailing list -- 389-users@l

[389-users] Re: Windows Sync Agreement issue

never been initialized. [23/Aug/2019:08:15:01.071494645 +0800] - WARN - NSMMReplicationPlugin - windows sync - windows_inc_run - agmt="cn=others" (tc-dc-2:389): Replica has no update vector. It has never been initialized. I don't want the sync agreement to be bi-directional. So how to r

[389-users] Re: 389ds automount issue

oami" with -H > ldap://389ds.example.com? YES. the ldapsearch can work propertly. Just the automount part has some issue. I will double check this today and reply. Thanks! Sincerely, -- DaV On Fri, Aug 23, 2019, at 08:53, William Brown wrote: > > > > On 23 Aug 2019, at 10:39, DaV

[389-users] Re: Windows Sync Agreement issue

interval from Windows to 389ds. Is there a relationship between the two attributes? nsDS5ReplicaUpdateSchedule and WinSyncinterval. Sincerely, -- DaV On Wed, Sep 4, 2019, at 15:15, Ludwig Krispenz wrote: > > On 09/04/2019 08:21 AM, DaV wrote: >> Hi William, >> I set nss

[389-users] Re: Windows Sync Agreement issue

interval from Windows to 389ds. Is there a relationship between the two attributes? nsDS5ReplicaUpdateSchedule and WinSyncinterval. Sincerely, -- DaV On Wed, Sep 4, 2019, at 15:15, Ludwig Krispenz wrote: > > On 09/04/2019 08:21 AM, DaV wrote: >> Hi William, >> I set nss

[389-users] sync AD account state

Hi guys, How can I sync account state from Windows AD to 389ds 1. account disabled 2. account lockout 3. password expired I want to sync these attributes from Windows AD to 389ds, would you please tell me? Thanks in advance. Sincerely, -- DaV

[389-users] DNA Plugin NextValue automatically added every time for same uid

side, user will get a UidNumber through DNA plugin. For example, an user get a uidNumber 5007 for the first sync, when I update user entry attribute(add telephone), this user will get a new uidNumber 5008 for the second sync. I don't know whether this is normal. Sincerely, -- DaV

[389-users] Re: DNA Plugin NextValue automatically added every time for same uid

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