[Freeipa-users] Feature request

[Dan Scott]

On Fri, Feb 24, 2012 at 15:48, Rich Megginson <rmeggins at redhat.com> wrote:
> On 02/24/2012 01:34 PM, Dan Scott wrote:
>>
>> On Fri, Feb 24, 2012 at 13:43, Rob Crittenden<rcritten at redhat.com>  wrote:
>>>
>>> Dan Scott wrote:
>>>>
>>>> Hi,
>>>>
>>>> I have an idea for a new feature. I've been having a lot of problems
>>>> with replication recently and I think the following would be useful.
>>>>
>>>> Can we show the replication status of the masters/replicas? And also
>>>> show whether they contain a CA?
>>>>
>>>> Something like:
>>>>
>>>> ipa-replica-manage -v list
>>>>
>>>> server1.example.com: master,CA [Up-to-date]
>>>> server2.example.com: master,CA  [Not replicating!]
>>>> server3.example.com: master  [Up-to-date]
>>>
>>>
>>> Add a server name to the end of that command and you'll get the status:
>>>
>>> # ipa-replica-manage list -v rawhide.greyoak.com
>>> Directory Manager password:
>>>
>>> pony.greyoak.com: replica
>>>  last init status: None
>>>  last init ended: None
>>>  last update status: 0 Replica acquired successfully: Incremental update
>>> succeeded
>>>  last update ended: 2012-02-24 18:12:59+00:00
>>> win2003.greyoak.com: replica
>>>  last init status: 0 Total update succeeded
>>>  last init ended: 2012-02-24 18:07:26+00:00
>>>  last update status: 0 Replica acquired successfully: Incremental update
>>> succeeded
>>>  last update ended: 2012-02-24 18:37:25+00:00
>>
>> Excellent! Thanks. Unfortunately, I have a problem:
>>
>> [root at fileserver1 ~]# ipa-replica-manage -v list fileserver1
>> fileserver2: replica
>>   last init status: None
>>   last init ended: None
>>   last update status: -1 Incremental update has failed and requires
>> administrator actionSystem error
>>   last update ended: 2012-02-15 22:02:39+00:00
>> fileserver4: replica
>>   last init status: 0 Total update succeeded
>>   last init ended: 2012-02-24 18:13:51+00:00
>>   last update status: -1  - System error
>>   last update ended: 2012-02-24 18:09:22+00:00
>>
>> Neither of those look good.... :( Any ideas to solve the problems?
>
> I would suggest upgrading to 389-ds-base-1.2.10.2 - then we can investigate
> further

When I updated Fedora last week on one of my replicas, it completely
killed my LDAP server..... I sent another mail to the list about this.

Thanks,

Dan