#51191 Issue 51188 - db2ldif crashes when LDIF file can't be accessed
Closed 2 years ago by spichugi. Opened 2 years ago by spichugi.
spichugi/389-ds-base i51188  into  master

@@ -871,6 +871,7 @@ 

              slapi_log_err(SLAPI_LOG_ERR, "bdb_db2ldif",

                      "db2ldif: %s: can't open %s: %d (%s) while running as user \"%s\"\n",

                      inst->inst_name, fname, errno, dblayer_strerror(errno), slapdFrontendConfig->localuserinfo->pw_name);

+             we_start_the_backends = 0;

              return_value = -1;

              goto bye;

          }

Bug Description: db2ldif crashes when we set '-a LDIF_PATH' to a place that
can't be accessed by the user (dirsrv by default)

Fix Description: Don't attempt to close DB if we bail after a failed
attempt to open LDIF file.

https://pagure.io/389-ds-base/issue/51188

Reviewed by: ?

rebased onto 68f8011

2 years ago

Pull-Request has been closed by spichugi

2 years ago

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/4244

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

2 years ago
Metadata