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.

Sign up for GitHub

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

Jump to bottom

Logrotate job must not use absolute paths / datadir change issue #20628

Closed
2 tasks
PVince81 opened this issue Nov 20, 2015 · 4 comments
Closed
2 tasks

Logrotate job must not use absolute paths / datadir change issue #20628

PVince81 opened this issue Nov 20, 2015 · 4 comments
Labels
comp:core status/STALE Type:Bug
Milestone
maybe some day

Comments

@PVince81
Copy link
Contributor

PVince81 commented Nov 20, 2015 •
edited by DeepDiver1975

See #20621 (comment)

It looks like the logrotate oc_job is using an absolute path to the data directory.
This means that whenever someone moves the data dir, this job will fail.

So the fix would be as follows:

  • make logrotate work with relative paths, if possible
  • repair step to make the existing paths in oc_jobs relative to datadir
@PVince81 PVince81 added this to the backlog milestone Nov 20, 2015
@PVince81 PVince81 mentioned this issue Nov 20, 2015
Closed
@ghost ghost mentioned this issue Nov 20, 2015
Closed
@ghost ghost mentioned this issue Mar 19, 2016
Closed
@ghost ghost mentioned this issue Apr 28, 2016
Closed
@PVince81
Copy link
Contributor Author

Still exists on 9.1.0beta2

@tflidd tflidd mentioned this issue Jun 17, 2016
Closed
@ghost ghost mentioned this issue Oct 17, 2016
Closed
@ghost ghost mentioned this issue Dec 8, 2016
Closed
@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@PVince81 PVince81 reopened this Jan 15, 2018
@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@PVince81 PVince81 reopened this Feb 23, 2018
@stale
Copy link

stale bot commented Sep 21, 2021

This issue has been automatically closed.

@stale stale bot closed this as completed Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
comp:core status/STALE Type:Bug
Projects
None yet
Milestone
maybe some day
Development

No branches or pull requests
3 participants
@PVince81 @felixboehm @ownclouders