Re: Last update message time stamp

[Mark Reynolds <mareynol@xxxxxxxxxx>]

On 08/28/2017 01:29 PM, Paul Whitney wrote:

I am referring to the admin console in "Last Update Message" section where "Begin time of last update:" and "End time of last update:"  If there is a problem with replication, the time stamps reset to "Wed Dec 31 1900 EST 1969" and not the last successful replication time.

Ditto for the Consumer Initialization Status, the time stamps get reset to "Wed Dec 31 1900 EST 1969"

What version of 389-ds-base?  rpm -qa | grep 389-ds-base

There was some work done in this area recently, so its potentially fixed, or it caused a regression, or neither :-)  This depends on what version you have. 

What kind of replication problem causes it to reset?  Is there a way to reproduce it easily?

Thanks,
Mark

Paul M. Whitney
E-mail: paul.whitney@xxxxxxx
Sent from my browser.

On Aug 28, 2017, at 12:41 PM, Mark Reynolds <mareynol@xxxxxxxxxx> wrote:

On 08/28/2017 11:54 AM, Paul Whitney wrote:

Hi guys,

Is there a reason why the update time stamp defaults to Dec 31, 19:00 EST 1969 in the console?

Hey Paul,

What exactly are you referring to?  Modifytimestamp?  Which entry?

Mark

 Is there a way to preserve the last successful or failed timestamp?

 

 

Paul M. Whitney
E-mail: paul.whitney@xxxxxxx

Sent from my browser.

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx