Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

filed: fix vss during client initiated connections #1665

Merged

Conversation

sebsura
Copy link
Contributor

@sebsura sebsura commented Jan 19, 2024

Thank you for contributing to the Bareos Project!

Using client initiated connections lead to the filedaemon trying to open files on the live system and not on the shadow copy. This was caused by not setting up the thread local jcr pointer correctly. This pr fixes that issue.

It also includes:

  • Bad format specifier for jobid in a jmsg
  • list additional files to include/exclude in dmsgs.
  • removing the double newline in some windows error messages.

Please check

  • Short description and the purpose of this PR is present above this paragraph
  • Your name is present in the AUTHORS file (optional)

If you have any questions or problems, please give a comment in the PR.

Helpful documentation and best practices

Checklist for the reviewer of the PR (will be processed by the Bareos team)

Make sure you check/merge the PR using devtools/pr-tool to have some simple automated checks run and a proper changelog record added.

General
  • Is the PR title usable as CHANGELOG entry?
  • Purpose of the PR is understood
  • Commit descriptions are understandable and well formatted
  • Check backport line
  • Required backport PRs have been created
Source code quality
  • Source code changes are understandable
  • Variable and function names are meaningful
  • Code comments are correct (logically and spelling)
  • Required documentation changes are present and part of the PR

@sebsura sebsura force-pushed the dev/ssura/master/fix-client-connected-vss branch 2 times, most recently from 8491f84 to 5251048 Compare January 19, 2024 09:45
core/src/filed/dir_cmd.cc Outdated Show resolved Hide resolved
core/src/win32/filed/vss_generic.cc Show resolved Hide resolved
@sebsura sebsura requested a review from pstorz January 19, 2024 11:08
Copy link
Member

@pstorz pstorz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see updated comments

@sebsura sebsura force-pushed the dev/ssura/master/fix-client-connected-vss branch from 5251048 to 0ce992a Compare January 19, 2024 13:49
@sebsura sebsura force-pushed the dev/ssura/master/fix-client-connected-vss branch from 0ce992a to dc578f0 Compare January 19, 2024 13:57
@sebsura sebsura requested a review from pstorz January 19, 2024 14:01
Copy link
Member

@pstorz pstorz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work!

@sebsura sebsura force-pushed the dev/ssura/master/fix-client-connected-vss branch from dc578f0 to 4484237 Compare January 22, 2024 05:37
sebsura and others added 5 commits January 22, 2024 06:23
Now the error number is always printed and trailing whitespace is
trimmed.
When using client initiated connection we do not call the normal
procedure but instead directly call process_director_commands.  This
caused us to not correctly initialise the threadspecific jcr, which is
used in 1) debug messages and 2) for vss name lookup

This caused us to print bad jobids in debug messages as well as not
using the vss system at all.
jobids are 32bit, but are printed as 64bit -> bad things happens on
windows.
@BareosBot BareosBot force-pushed the dev/ssura/master/fix-client-connected-vss branch from 66c0cc2 to 98a50b0 Compare January 22, 2024 06:23
@BareosBot BareosBot merged commit 8e12c14 into bareos:master Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants