#47801 RHDS keeps on logging write_changelog_and_ruv: failed to update RUV for unknown
Closed: Fixed None Opened 5 years ago by rmeggins.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Directory Server): Bug 1096409

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
RHDS keeps on logging write_changelog_and_ruv: failed to update RUV for unknown
[25/Mar/2014:15:26:09 -0500] NSMMReplicationPlugin - write_changelog_and_ruv:
failed to update RUV for unknown (uniqid: unknown, optype: 0) to changelog csn
[25/Mar/2014:15:27:02 -0500] NSMMReplicationPlugin - write_changelog_and_ruv:
failed to update RUV for unknown (uniqid: unknown, optype: 0) to changelog csn

Version-Release number of selected component (if applicable):
389-ds-base-1.2.11.15-29.el6
RHEL 6.5

How reproducible:
Always in Customer Environment.


Additional info:

It looks like it is realted to .

https://fedorahosted.org/389/attachment/ticket/47392/0001-Ticket-47392-ldbm-err
ors-when-adding-modifying-delet.patch

rc = update_ruv_component(r, opcsn, pb);
if (RUV_COVERS_CSN == rc) {
        slapi_log_error(SLAPI_LOG_REPL, repl_plugin_name,
                        "write_changelog_and_ruv: RUV already covers csn for "
                        "%s (uniqid: %s, optype: %lu) csn %s\n",
                        REPL_GET_DN(&op_params->target_address),
                        op_params->target_address.uniqueid,
                        op_params->operation_type,
                        csn_as_string(op_params->csn, PR_FALSE, csn_str));
} else if (rc != RUV_SUCCESS) {
        slapi_log_error(SLAPI_LOG_FATAL, repl_plugin_name,
                        "write_changelog_and_ruv: failed to update RUV for "
                        "%s (uniqid: %s, optype: %lu) to changelog csn %s\n",
                        REPL_GET_DN(&op_params->target_address),
                        op_params->target_address.uniqueid,
                        op_params->operation_type,
                        csn_as_string(op_params->csn, PR_FALSE, csn_str));


in this case, It is coming for unknown value.

Increasing the error log level of RHDS to 8192 does not provide more
information.

Before, we did not log anything when update_ruv_component() returned an error, because we did not check the return value. Now we do, but unfortunately we don't know why it is returning an error.

Replying to [comment:1 rmeggins]:

Before, we did not log anything when update_ruv_component() returned an error, because we did not check the return value. Now we do, but unfortunately we don't know why it is returning an error.

It looks opcsn is NULL, doesn't it?
{{{
static int
update_ruv_component(Replica replica, CSN opcsn, Slapi_PBlock *pb)
{
int rc = RUV_NOTFOUND;
if (!replica || !opcsn)
return rc;
}}}

Replying to [comment:2 nhosoi]:

Replying to [comment:1 rmeggins]:

Before, we did not log anything when update_ruv_component() returned an error, because we did not check the return value. Now we do, but unfortunately we don't know why it is returning an error.

It looks opcsn is NULL, doesn't it?

Could be. Not sure if update_ruv_component can return some other error code. We should print the error code to the logs if so.

We need to find out why update_ruv_component is being called with a NULL opcsn.

{{{
static int
update_ruv_component(Replica replica, CSN opcsn, Slapi_PBlock *pb)
{
int rc = RUV_NOTFOUND;
if (!replica || !opcsn)
return rc;
}}}

Reviewed by Rich (Thank you!!)

Pushed to master:
2802f36..c170d95 master -> master
commit c170d95

Pushed to 389-ds-base-1.3.3:
06a5cc4..1e38fbe 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 1e38fbe

Pushed to 389-ds-base-1.2.11:
50910ac..423c15c 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 423c15c

Metadata Update from @rmeggins:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.2.11.33

2 years ago

Login to comment on this ticket.

Metadata