There is a integer overflow when getting the system time for uuid calculation, which then writes invalid nsState information.
This is detected during an upgrade
# setup-ds.pl -u ... ... Updating instance (slapd-AUSIL-US)... Error: could not parse nsstate 00f38b11d21db201d28880b54b3f89010100000000000000 - tsdiff is 6882719651.34442 seconds or 79661.1070757456 days [18/02/13:22:07:33] - [Setup] Info Error: could not parse nsState from cn=uniqueid generator,cn=config. Value: 00f38b11d21db201d28880b54b3f89010100000000000000 [18/02/13:22:07:33] - [Setup] Fatal Error: could not update the directory server. [18/02/13:22:07:33] - [Setup] Fatal Exiting . . . Log file is '/tmp/setup_Axodi.log'
armv7hl (possibly other 32 bit platforms)
<img alt="0001-Ticket-49568-Fix-integer-overflow-on-32bit-platforms.patch" src="/389-ds-base/issue/raw/files/bdc1e16ec6b026be823802df25197fd121be666398b3a4f3ede4f71bee280ba9-0001-Ticket-49568-Fix-integer-overflow-on-32bit-platforms.patch" />
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to review - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1529442 - Custom field type adjusted to None - Custom field version adjusted to None
Error: could not parse nsstate 00f38b11d21db201d28880b54b3f89010100000000000000 - tsdiff is 6882881288.34442 seconds or 79662.9778743567 days Error: could not parse nsState from cn=uniqueid generator,cn=config. Value: 00f38b11d21db201d28880b54b3f89010100000000000000 Error: could not update the directory server.
not quite enough
Error: could not parse nsstate 00f38b11d21db201d28880b54b3f89010100000000000000 - tsdiff is 6882881288.34442 seconds or 79662.9778743567 days Error: could not parse nsState from cn=uniqueid generator,cn=config. Value: 00f38b11d21db201d28880b54b3f89010100000000000000 Error: could not update the directory server. not quite enough
Did you test the patch attached to this ticket? Becuase I can not reproduce it on ARM with the above patch
Revised patch
<img alt="0001-Ticket-49568-Fix-integer-overflow-on-32bit-platforms.patch" src="/389-ds-base/issue/raw/files/c1b8841ec4fc96a1beac0bb882fdfac8a3f43aa95e2ec8a9e26b5c09fe8e8f3f-0001-Ticket-49568-Fix-integer-overflow-on-32bit-platforms.patch" />
Okay, this will fix this problem, but it doesn't fix the remaining 32bit problems that exist ...
So I'm okay to ack this, with a HUGE disclaimer that "32bit platforms are not safe for consumption with DS still".
:(
ack from me,
I did not mean to imply that it did. Just fixing the upgrade :-)
So I'm okay to ack this, with a HUGE disclaimer that "32bit platforms are not safe for consumption with DS still". :( ack from me,
e62a443..774ee3e master -> master
4e2694f..229f76c 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
144fb64..de82415 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2627
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Log in to comment on this ticket.