Re: WindowsSync - Replica has no update vector. It has never been initialized. It has never been initialized.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I should have included this snippet of the error log in my first
email, but I didn't catch it at first...

[09/Oct/2006:17:29:05 -0400] - _csngen_parse_state: replica id
mismatch; current id - 5, replica id in the state - 1
[09/Oct/2006:17:29:05 -0400] NSMMReplicationPlugin -
_replica_init_from_config: failed to create csn generator for replica
(cn=replica,cn=\22ou=People,dc=poc,dc=net\22,cn=mapping tree,
cn=config)
[09/Oct/2006:17:29:05 -0400] NSMMReplicationPlugin - Unable to
configure replica ou=People,dc=poc,dc=net: failed to create csn
generator for replica
(cn=replica,cn=\22ou=People,dc=poc,dc=net\22,cn=mapping tree,
cn=config)
[09/Oct/2006:17:29:05 -0400] - slapd started.  Listening on All
Interfaces port 389 for LDAP requests
[09/Oct/2006:17:29:05 -0400] - Listening on All Interfaces port 636
for LDAPS requests
[09/Oct/2006:17:31:04 -0400] NSMMReplicationPlugin -
agmtlist_add_callback: Can't start agreement "cn=infrapoc ad
sync,cn=replica,cn="ou=people,dc=poc,dc=net",cn=mapping
tree,cn=config"

After seeing this error, I have gone back and deleted the windows sync
agreement, disabled and then re-enabled the single master replication
with a Replica ID of '1' and finally re-created the windows sync.
Still no luck. :-(

-- Jon

On 10/9/06, Jon Miller <jonebird at gmail.com> wrote:
> Hello All,
>   I have just installed and setup Fedora DS 1.0.2 on a RHEL 4.0
> machine. I am interested in using the Windows Sync, but am running
> into one last issue that I can not seem to solve. I am getting the
> following error in my "errors" log file:
> [09/Oct/2006:14:54:43 -0400] NSMMReplicationPlugin - agmt="cn=Infrapoc
> Sync" (iwpoccorsrv01:636): Replica has no update vector. It has never
> been initialized.
> At this point, neither the incremental updates or the full sync work.
> Could someone please shed some light on this error and how to resolve it?
>
> Additionally, I have already attempted to research and solve this
> issue on my own.
> Restarting the Admin Server [1] did not help.
> Have also restarted my DS multiple times.
> --
> Any help is appreciated,
> Jon
>
>
> [1] http://www.redhat.com/archives/fedora-directory-users/2006-June/msg00075.html
>


-- 
Later,
Jon




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux