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

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

Open
PVince81 opened this issue Nov 20, 2015 · 3 comments

Comments

@PVince81
Copy link
Member

commented Nov 20, 2015

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

This comment has been minimized.

Copy link
Member Author

commented Jun 14, 2016

Still exists on 9.1.0beta2

@ownclouders

This comment has been minimized.

Copy link
Contributor

commented Jan 13, 2018

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.)

@ownclouders

This comment has been minimized.

Copy link
Contributor

commented Feb 23, 2018

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.