if the dbhome directory is set, eg to /dev/shm/instance then an online backup fails because it looks for the log.000000x file in the wring diretcory.
[29/Apr/2020:17:58:57.268949526 +0200] - ERR - dblayer_copyfile - Failed to open source file /dev/shm/dirsrv/slapd-master1/log.0000000001 by "No such file or directory" [29/Apr/2020:17:58:57.275365122 +0200] - ERR - dblayer_backup - Error in copying file '/dev/shm/dirsrv/slapd-master1/log.0000000001' (err=-1)
unfortunately this is hidden because the return code is overwritten before checking
/* tell it to archive */ return_value = dblayer_backup(li, directory, task); return_value = plugin_call_plugins(pb, SLAPI_PLUGIN_BE_POST_BACKUP_FN);
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue assigned to lkrispen - Issue priority set to: critical - Issue set to the milestone: 1.4.2
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1851967
Issue linked to Bugzilla: Bug 1851967
Metadata Update from @spichugi: - Issue assigned to spichugi (was: lkrispen)
https://pagure.io/389-ds-base/pull-request/51207
ed5b13c..22c5149 master -> origin/master 88006a6..48572f6 389-ds-base-1.4.2 -> 389-ds-base-1.4.2 7ab8bad..7624c59 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
Metadata Update from @spichugi: - 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/4112
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)
Login to comment on this ticket.