OK I checked and it is not a disk space issue, there is plenty of space for the
changelog. It does not appear to be a an issue with not flushing the RUV at
shutdown. The shutdown is clean in the logs, there are no errors. I shutdown
and restarted twice and the only thing I get is the warning on startup.
"The server will not be able to send the changes to a consumer if the
consumer's maxcsn no longer exists in the server's changelog." Is there some
way I can look in the change log to see the maxcsn? All the cosumers maxcsn
must be there because replication is working.
From: 389-users-boun...@lists.fedoraproject.org
[mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Grzegorz
Dwornicki
Sent: Friday, January 11, 2013 5:54 PM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] NSMMReplicationPlugin - replica_check_for_data_reload:
Warning:
This is your call :).
Keep in mind that in case something will be wrong with replication, I am not
telling that case like this. But when you post that theoretical problem, then
this warrning can make people trying to help you endup following ghosts and not
the real problem.
If you leave this as it is then consider checking replication from time to
time. Now it is working but tomorow it can break...
Greg.
11 sty 2013 23:29, "James Lee" <jm...@advance.net<mailto:jm...@advance.net>>
napisał(a):
Thanks Greg.
In answer to my own email. Google has turned up this:
http://www.centos.org/docs/5/html/CDS/ag/8.0/Managing_Replication-Troubleshooting_Replication_Related_Problems.html
Error:
Warning: data for replica's was reloaded, and it no longer matches the data in
the changelog. Recreating the changelog file. This could affect replication
with replica's consumers, in which case the consumers should be reinitialized.
Reason:
This message may appear only when a supplier is restarted. It indicates that
the supplier was unable to write the changelog or did not flush out its RUV at
its last shutdown. The former is usually because of a disk-space problem, and
the latter because a server crashed or was ungracefully shut down.
Impact:
The server will not be able to send the changes to a consumer if the consumer's
maxcsn no longer exists in the server's changelog.
Remedy:
Check the disk space and the possible core file (under the server's logs
directory). If this is a single-master replication, reinitialize the consumers.
Otherwise, if the server later complains that it can't locate some CSN for a
consumer, see if the consumer can get the CSN from other suppliers. If not,
reinitialize the consumer.
So I will take a look and see if this helps and report back my findings. At the
moment from my tests, replication is working so maybe there is no need to
reinitialize.
From:
389-users-boun...@lists.fedoraproject.org<mailto:389-users-boun...@lists.fedoraproject.org>
[mailto:389-users-boun...@lists.fedoraproject.org<mailto:389-users-boun...@lists.fedoraproject.org>]
On Behalf Of Grzegorz Dwornicki
Sent: Friday, January 11, 2013 3:10 PM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] NSMMReplicationPlugin - replica_check_for_data_reload:
Warning:
It apears that you need to reinitialize consumers again. In your case three
masters from fourth. I think this can do some harm. Lets asume that 389 uses
some version numbers to tell consumers when they need to replicate data from
master server (this will be the change log).
Now lets say that one consumer have wrong number. It will not replicate as it
should. If this consumer is master aswell then it can write wrong data to other
consumers.
Well I'm not expert and this is how I see this warning. I would make sure that
one master have good data and initialize from it other masters.
Greg.
11 sty 2013 20:36, "James Lee" <jm...@advance.net<mailto:jm...@advance.net>>
napisał(a):
Hi,
Each time I restart my master server I get the following warning message in the
error log:
[11/Jan/2013:14:04:29 -0500] - CentOS-Directory/8.2.8 B2012.041.1227 starting up
[11/Jan/2013:14:04:29 -0500] NSMMReplicationPlugin -
replica_check_for_data_reload: Warning: data for replica dc=<my_domain>,dc=net
was reloaded and it no longer matches the data in the changelog (replica data >
changelog). Recreating the changelog file. This could affect replication with
replica's consumers in which case the consumers should be reinitialized.
[11/Jan/2013:14:04:29 -0500] - slapd started. Listening on All Interfaces port
389 for LDAP requests
My env:
CentOS release 5.5 (Final)
Multi master setup with consumers
centos-ds-8.2.0-2.el5.centos
centos-ds-base-8.2.8-2.el5.centos
I guess this is just a warning, but does it mean there is a problem? I get this
on all four of my master servers when I restart dirsrv. I tested and
replication is working. Would be nice to get rid of this error.
James.
________________________________
This e-mail, including attachments, is intended for the person(s) or company
named and may contain confidential and/or legally privileged information.
Unauthorized disclosure, copying or use of this information may be unlawful and
is prohibited. If you are not the intended recipient, please delete this
message and notify the sender.
--
389 users mailing list
389-users@lists.fedoraproject.org<mailto:389-users@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/389-users
________________________________
This e-mail, including attachments, is intended for the person(s) or company
named and may contain confidential and/or legally privileged information.
Unauthorized disclosure, copying or use of this information may be unlawful and
is prohibited. If you are not the intended recipient, please delete this
message and notify the sender.
--
389 users mailing list
389-users@lists.fedoraproject.org<mailto:389-users@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/389-users
------------------------------------------------------------------------------------------------
This e-mail, including attachments, is intended for the person(s)
or company named and may contain confidential and/or legally
privileged information. Unauthorized disclosure, copying or use of
this information may be unlawful and is prohibited. If you are not
the intended recipient, please delete this message and notify the
sender.
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
