<html> <head> <meta content="text/html; charset=KOI8-R" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 06/17/2015 02:27 PM, Alexander Frolushkin wrote: </div> <blockquote cite="mid:6a9ee184a0a549eab53054c5d71beb73@sib-ums03.Megafon.ru" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=KOI8-R"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)">  <style></style> <div class="WordSection1"> Except:<o:p></o:p> “unable to decode: {replica 22} 5576b83e000200160000 5576ba4b000200160000<o:p></o:p> unable to decode: {replica 20} 55716e57000300140000 55716e57000300140000<o:p></o:p> unable to decode: {replica 16} 548a8126000000100000 548a8126000000100000<o:p></o:p> unable to decode: {replica 24} 557fb7d4000400180000 557fb9a1001000180000<o:p></o:p> unable to decode: {replica 21} 5576ac96000000150000 5576b52e000200150000”<o:p></o:p> records, all replicas are unique and have corresponding id’s.<o:p></o:p> Total number of not “unable to decode” servers is equal to real number of replicas in domain.<o:p></o:p> <o:p> </o:p> I can confirm some of cleanallruv processes was not finished correctly after some replica remove.<o:p></o:p> <o:p> </o:p> Slapd on replica id 10 last restarted yesterday 15:05 server local time. </div> </blockquote> It was restarted 16/Jun/2015:15:05 and send the update one day after ! [17/Jun/2015:14:39:46 +0600] conn=237 op=93 ADD dn="cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru"<o:p></o:p> [17/Jun/2015:14:39:46 +0600] conn=237 op=93 RESULT err=0 tag=105 nentries=0 etime=0 csn=555ac936000000140000 May be it was very very slow. <blockquote cite="mid:6a9ee184a0a549eab53054c5d71beb73@sib-ums03.Megafon.ru" type="cite"> <div class="WordSection1"> <o:p></o:p> <o:p> </o:p> The same question, may it help if I tomorrow will do re-initialize all replicas from our relatively good-conditioned site? </div> </blockquote> If you reinit all replicas, it will clear their CL so such very old updates will no long exist. Now if it exists very slow replica (like replica10) that holds their updates for long before replicating then it increases the possibility of creating conflicts. <blockquote cite="mid:6a9ee184a0a549eab53054c5d71beb73@sib-ums03.Megafon.ru" type="cite"> <div class="WordSection1"> <o:p></o:p> <o:p> </o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p> </o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: thierry bordaz [<a class="moz-txt-link-freetext" href="mailto:tbordaz@redhat.com">mailto:tbordaz@redhat.com</a>] Sent: Wednesday, June 17, 2015 6:16 PM To: Alexander Frolushkin (SIB) Cc: 'Ludwig Krispenz'; <a class="moz-txt-link-abbreviated" href="mailto:freeipa-users@redhat.com">freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p> </o:p> <div> On 06/17/2015 01:38 PM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Ok, I’ll try this soon, thank you!<o:p></o:p> Also, please note, most of today dups appeared when 4 of 19 servers was very busy in IO (all our servers are VMs), because dirsrv debug was enabled to gather logs for our case about <o:p></o:p> attrlist_replace - attr_replace (nsslapd-referral, <a moz-do-not-send="true" href="ldap://xxx-rhidm0x.unix.megafon.ru:389/o%3Dipaca">ldap://xxx-rhidm0x.unix.megafon.ru:389/o%3Dipaca</a>) failed. <o:p></o:p> </blockquote> This message comes if you have duplicated ReplicaID. 'list-ruv' would show you a same url appearing several times with different RID. To be back on the original problem (dup), I wonder if it is not related to cleanruv/corrupted RUV. A new replica26 is created and is initialized from a master and it does not contain entry 555ac936000000140000. That allows the creation of 5580f3210000001a0000. Then replica10 sends 555ac936000000140000 to replica26. That means that changelog/ruv of replica10 contained that update, so either cleanallruv20 did not happen on replica10 or fail to clean its CL. Replica10 has a very old update that was not known from the master used to init replica26. Was replica10 restarted recently. thanks theirry <o:p></o:p> errors<o:p></o:p> Also during collection some of dirsrv instances hangs and was restarted.<o:p></o:p> <o:p></o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Ludwig Krispenz [<a moz-do-not-send="true" href="mailto:lkrispen@redhat.com">mailto:lkrispen@redhat.com</a>] Sent: Wednesday, June 17, 2015 5:34 PM To: Alexander Frolushkin (SIB) Cc: 'thierry bordaz'; <a moz-do-not-send="true" href="mailto:freeipa-users@redhat.com">freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p></o:p> <o:p></o:p> <div> On 06/17/2015 12:57 PM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Unfortunately, number of duplicates grows dramatically on most sites. Some servers already have over 40 duplicates.<o:p></o:p> Could you please say, may I use re-initialize on falling replica from the good one to fix this?<o:p></o:p> </blockquote> If you have a good one, this should work, "dups" are only created when a replicated ADD is received for an existing entry. But what really puzzles me is that you do not have them on all servers, something weird seems to happen, this entry seems to exist whit several replicaids, and why would replica 10 replicate this 4 hrs after the replica installation. <o:p></o:p> <o:p></o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Ludwig Krispenz [<a moz-do-not-send="true" href="mailto:lkrispen@redhat.com">mailto:lkrispen@redhat.com</a>] Sent: Wednesday, June 17, 2015 4:35 PM To: Alexander Frolushkin (SIB) Cc: 'thierry bordaz'; <a moz-do-not-send="true" href="mailto:freeipa-users@redhat.com">freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p></o:p> conn=237 is from 10.99.75.82 which replica is this ?<o:p></o:p> <div> On 06/17/2015 12:13 PM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> This is not a good news, because replica id 20 is not exist for a some days already. It was recreated and now have id 23<o:p></o:p> <o:p></o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: thierry bordaz [<a moz-do-not-send="true" href="mailto:tbordaz@redhat.com">mailto:tbordaz@redhat.com</a>] Sent: Wednesday, June 17, 2015 4:10 PM To: Alexander Frolushkin (SIB) Cc: 'Ludwig Krispenz'; <a moz-do-not-send="true" href="mailto:freeipa-users@redhat.com">freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p></o:p> <div> On 06/17/2015 11:56 AM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Will this be enough?<o:p></o:p> <o:p></o:p> # grep "conn=237 op=93" ./access<o:p></o:p> [17/Jun/2015:14:39:46 +0600] conn=237 op=93 ADD dn="cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru"<o:p></o:p> [17/Jun/2015:14:39:46 +0600] conn=237 op=93 RESULT err=0 tag=105 nentries=0 etime=0 csn=555ac936000000140000<o:p></o:p> </blockquote> This operation is a replicated one and the CSN is from May 19th. So why a replica (26) created today was initialized without that entry ? This updates was originated from replica20. Was it stopped and restarted recently ? <o:p></o:p> <o:p></o:p> # grep "conn=293" ./access<o:p></o:p> [17/Jun/2015:15:33:04 +0600] conn=293 fd=75 slot=75 connection from 10.99.75.82 to 10.61.8.2<o:p></o:p> [17/Jun/2015:15:33:04 +0600] conn=293 op=0 BIND dn="" method=sasl version=3 mech=GSSAPI<o:p></o:p> [17/Jun/2015:15:33:04 +0600] conn=293 op=0 RESULT err=14 tag=97 nentries=0 etime=0, SASL bind in progress<o:p></o:p> [17/Jun/2015:15:33:04 +0600] conn=293 op=1 BIND dn="" method=sasl version=3 mech=GSSAPI<o:p></o:p> [17/Jun/2015:15:33:04 +0600] conn=293 op=1 RESULT err=14 tag=97 nentries=0 etime=0, SASL bind in progress<o:p></o:p> [17/Jun/2015:15:33:04 +0600] conn=293 op=2 BIND dn="" method=sasl version=3 mech=GSSAPI<o:p></o:p> [17/Jun/2015:15:33:04 +0600] conn=293 op=2 RESULT err=0 tag=97 nentries=0 etime=0 dn=<a moz-do-not-send="true" href="mailto:krbprincipalname=ldap/msk-rhidm-03.unix.megafon.ru@unix.megafon.ru,cn=services,cn=accounts,dc=unix,dc=megafon,dc=ru">"krbprincipalname=ldap/msk-rhidm-03.unix.megafon.ru@unix.megafon.ru,cn=services,cn=accounts,dc=unix,dc=megafon,dc=ru"</a><o:p></o:p> <o:p></o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Ludwig Krispenz [<a moz-do-not-send="true" href="mailto:lkrispen@redhat.com">mailto:lkrispen@redhat.com</a>] Sent: Wednesday, June 17, 2015 3:53 PM To: thierry bordaz Cc: Alexander Frolushkin (SIB); <a moz-do-not-send="true" href="mailto:freeipa-users@redhat.com"> freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p></o:p> <o:p></o:p> <div> On 06/17/2015 11:45 AM, thierry bordaz wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <div> On 06/17/2015 11:22 AM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> This was a usual “ipa-replica-install --setup-ca --setup-dns” and after that ipa-adtrust-install.<o:p></o:p> <o:p></o:p> No DEL found:<o:p></o:p> # grep "cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru" ./access<o:p></o:p> [17/Jun/2015:10:08:01 +0600] conn=2 op=89 SRCH base="cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru" scope=0 filter="(objectClass=*)" attrs="ipaPermRight ipaPermTargetFilter ipaPermBindRuleType ipaPermissionType cn objectClass memberOf member ipaPermTarget ipaPermDefaultAttr ipaPermLocation ipaPermIncludedAttr ipaPermExcludedAttr"<o:p></o:p> [17/Jun/2015:10:08:01 +0600] conn=2 op=91 ADD dn="cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru"<o:p></o:p> </blockquote> There is something I miss. conn=2 op=91 was a direct update on replica26 (not replicated) because it received its own CSN=5580f3210000001a0000. But it created a conflict entry, so at that time it existed the same entry (the one created 20150408070720Z) . So the direct update should have been rejected.<o:p></o:p> </blockquote> I think the search in op=89 did not return an entry, so it was added in op 91, that seems to be ok, but then 4 hrs later there is conn=237 adding it again. Alexander, could you get the complete 'conn=237 op=93' and also the start of conn 293, to show where teh connection comes from <o:p></o:p> Would you check if the replicaID=26 is unique in the topology (list-ruv for example) ? <o:p></o:p> [17/Jun/2015:14:39:46 +0600] conn=237 op=93 ADD dn="cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru"<o:p></o:p> <o:p></o:p> It is also possible this entry on affected servers was previously duplicated and not correctly managed to delete (more recent dup was deleted). <o:p></o:p> Is there any natural way to fix such issues? Maybe ipa-replica-manage force-sync, or ipa-replica-manage re-initialize on affected site servers from normal servers could help?<o:p></o:p> <o:p></o:p> <o:p></o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: thierry bordaz [<a moz-do-not-send="true" href="mailto:tbordaz@redhat.com">mailto:tbordaz@redhat.com</a>] Sent: Wednesday, June 17, 2015 3:15 PM To: Alexander Frolushkin (SIB) Cc: 'Ludwig Krispenz'; <a moz-do-not-send="true" href="mailto:freeipa-users@redhat.com">freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p></o:p> <div> Hello Alexander, How did you initialize that new replica 26. Either 'cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru' was not part of the total init data, or a DEL of that entry happened on replica 26 (before a new ADD) but the DEL was not replicated to replica12. Would you check in replica26 access logs if that entry was deleted ? thanks theirry On 06/17/2015 11:03 AM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> This is correct, thank you for understanding and for helping!<o:p></o:p> Replica with id 26 was created today, this is our new server which was included in domain just a few hours ago. Looks like this dup came right after this new replica creation.<o:p></o:p> <o:p></o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Ludwig Krispenz [<a moz-do-not-send="true" href="mailto:lkrispen@redhat.com">mailto:lkrispen@redhat.com</a>] Sent: Wednesday, June 17, 2015 2:58 PM To: Alexander Frolushkin (SIB) Cc: <a moz-do-not-send="true" href="mailto:freeipa-users@redhat.com">freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p></o:p> Hi, you did send the data directly to me, maybe not wanting to share them to everyone. I'll continue discussion here, trying to be careful. The "good" entry was created in April on replica 12 "0x0c" createTimestamp;vucsn-5524d42b0067000c0000: 20150408070720Z the "nsuniqueid" entry was created today on replica 26 "0x1a" createTimestamp;vucsn-5580f3210000001a0000: 20150617040801Z if the original entry would have existed on replica26 the new add should have been rejected, if it was not there the question is why. Do you have any additional info on replica 26, when was it created, was it disconnected for some time ?? Ludwig<o:p></o:p> <div> On 06/17/2015 08:13 AM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Hello.<o:p></o:p> Another example. Today appeared on servers of different site.<o:p></o:p> <o:p></o:p> Original LDIF:<o:p></o:p> # extended LDIF<o:p></o:p> #<o:p></o:p> # LDAPv3<o:p></o:p> # base <cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru> with scope subtree<o:p></o:p> # filter: (objectclass=*)<o:p></o:p> # requesting: ALL<o:p></o:p> #<o:p></o:p> <o:p></o:p> # System: Manage Host Keytab, permissions, pbac, unix.megafon.ru<o:p></o:p> dn: cn=System: Manage Host Keytab,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc<o:p></o:p> =ru<o:p></o:p> ipaPermTargetFilter: (objectclass=ipahost)<o:p></o:p> ipaPermRight: write<o:p></o:p> ipaPermBindRuleType: permission<o:p></o:p> ipaPermissionType: V2<o:p></o:p> ipaPermissionType: MANAGED<o:p></o:p> ipaPermissionType: SYSTEM<o:p></o:p> cn: System: Manage Host Keytab<o:p></o:p> objectClass: ipapermission<o:p></o:p> objectClass: top<o:p></o:p> objectClass: groupofnames<o:p></o:p> objectClass: ipapermissionv2<o:p></o:p> member: cn=Host Enrollment,cn=privileges,cn=pbac,dc=unix,dc=megafon,dc=ru<o:p></o:p> member: cn=Host Administrators,cn=privileges,cn=pbac,dc=unix,dc=megafon,dc=ru<o:p></o:p> ipaPermDefaultAttr: krbprincipalkey<o:p></o:p> ipaPermDefaultAttr: krblastpwdchange<o:p></o:p> ipaPermLocation: cn=computers,cn=accounts,dc=unix,dc=megafon,dc=ru<o:p></o:p> <o:p></o:p> # search result<o:p></o:p> search: 2<o:p></o:p> result: 0 Success<o:p></o:p> <o:p></o:p> # numResponses: 2<o:p></o:p> # numEntries: 1<o:p></o:p> <o:p></o:p> Duplicate:<o:p></o:p> # extended LDIF<o:p></o:p> #<o:p></o:p> # LDAPv3<o:p></o:p> # base <cn=System: Manage Host Keytab+nsuniqueid=708bba65-14a611e5-8a48fd19-df27ff01,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru> with scope subtree<o:p></o:p> # filter: (objectclass=*)<o:p></o:p> # requesting: ALL<o:p></o:p> #<o:p></o:p> <o:p></o:p> # System: Manage Host Keytab + 708bba65-14a611e5-8a48fd19-df27ff01, permissio<o:p></o:p> ns, pbac, unix.megafon.ru<o:p></o:p> dn: cn=System: Manage Host Keytab+nsuniqueid=708bba65-14a611e5-8a48fd19-df27ff<o:p></o:p> 01,cn=permissions,cn=pbac,dc=unix,dc=megafon,dc=ru<o:p></o:p> ipaPermTargetFilter: (objectclass=ipahost)<o:p></o:p> ipaPermRight: write<o:p></o:p> ipaPermBindRuleType: permission<o:p></o:p> ipaPermissionType: V2<o:p></o:p> ipaPermissionType: MANAGED<o:p></o:p> ipaPermissionType: SYSTEM<o:p></o:p> cn: System: Manage Host Keytab<o:p></o:p> objectClass: ipapermission<o:p></o:p> objectClass: top<o:p></o:p> objectClass: groupofnames<o:p></o:p> objectClass: ipapermissionv2<o:p></o:p> member: cn=Host Enrollment,cn=privileges,cn=pbac,dc=unix,dc=megafon,dc=ru<o:p></o:p> member: cn=Host Administrators,cn=privileges,cn=pbac,dc=unix,dc=megafon,dc=ru<o:p></o:p> ipaPermDefaultAttr: krbprincipalkey<o:p></o:p> ipaPermDefaultAttr: krblastpwdchange<o:p></o:p> ipaPermLocation: cn=computers,cn=accounts,dc=unix,dc=megafon,dc=ru<o:p></o:p> <o:p></o:p> # search result<o:p></o:p> search: 2<o:p></o:p> result: 0 Success<o:p></o:p> <o:p></o:p> # numResponses: 2<o:p></o:p> # numEntries: 1<o:p></o:p> <o:p></o:p> No other servers in IPA domain have such duplicates.<o:p></o:p> <o:p></o:p> <div> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: <a moz-do-not-send="true" href="mailto:freeipa-users-bounces@redhat.com">freeipa-users-bounces@redhat.com</a> [<a moz-do-not-send="true" href="mailto:freeipa-users-bounces@redhat.com">mailto:freeipa-users-bounces@redhat.com</a>] On Behalf Of Ludwig Krispenz Sent: Tuesday, June 16, 2015 3:52 PM To: <a moz-do-not-send="true" href="mailto:freeipa-users@redhat.com">freeipa-users@redhat.com</a> Subject: Re: [Freeipa-users] replication conflicts<o:p></o:p> </div> </div> <o:p></o:p> <o:p></o:p> <div> On 06/16/2015 11:42 AM, Alexander Frolushkin wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Hello.<o:p></o:p> Just to remind if somebody still not familiar with our IPA installation J<o:p></o:p> We currently have 18 IPA servers in domain, on 8 sites in different regions across the Russia.<o:p></o:p> And now, our new problem.<o:p></o:p> Regularly we getting a nsds5ReplConflict records on some of our servers, very often on servers from specific site. Usually it is simply a doubles and we can remove the renamed change to get everything back. But why do we have them at all?<o:p></o:p> May be someone could explain, how we can detect the cause of this replication conflicts?<o:p></o:p> </blockquote> if you are talking about having two "duplicate" entries, one: uid=xxxxx,<suffix> one: nsuniqueid=nnnnnnnn+uid=xxxxx,<suffix> these entries appear if the entry uid=xxxxx was added, simultaneously, on two servers. I think this can happen if a client tries to add an entry and if it doesn't get a response in some time retries on another server. to find out which client this is you need to check on which servers the entries were originally added and then see which client was doing it <o:p></o:p> Sometime it is moderately harmful, because, for example HBAC stops working on specific server while doubles still present.<o:p></o:p> Thanks in forward…<o:p></o:p> <o:p></o:p> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> Cell +79232508764<o:p></o:p> Work +79232507764<o:p></o:p> <o:p></o:p> <o:p></o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50 <o:p></o:p> <o:p></o:p> <o:p></o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50<o:p></o:p> </blockquote> <o:p></o:p> <o:p></o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50 <o:p></o:p> </blockquote> <o:p></o:p> <o:p></o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50<o:p></o:p> <o:p></o:p> <o:p></o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50<o:p></o:p> </blockquote> <o:p></o:p> <o:p></o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50<o:p></o:p> <o:p></o:p> <o:p> </o:p> <div class="MsoNormal" style="text-align:center" align="center"> <hr size="2" width="100%" align="center"> </div> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50<o:p></o:p> <o:p> </o:p> </div> <hr> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50 </blockquote> </body> </html>