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

XrootD logrotate config file is deficient #135

Closed
wyang007 opened this issue Sep 4, 2014 · 0 comments
Closed

XrootD logrotate config file is deficient #135

wyang007 opened this issue Sep 4, 2014 · 0 comments

Comments

@wyang007
Copy link
Member

wyang007 commented Sep 4, 2014

There are two big problems with the default log rotate config file.

  1. Since log rotate runs as root, when it rotates the file and creates a new log file, the new log file is owned by root. At this point xrootd cannot write to the new file. This causes information loss. Either logrotate should preserve ownership on the new log file or simply not create it ahead of time as xrootd will create it when notified to close and reopen the log file (i.e. add the no create option). This has been a big out-of-the-box problem at many sites.

  2. The header line that tell whee log rotate should look for log files include two locations a) the default when no instance name is used, and b) the location where an instance name is used. Unfortunately, if one or the other does not exists then log rotate sends an error email to root which eventually gets to the sysadmin completely annoying them as one gets generated each day. While this is not a critical problem it is sufficiently annoying to require a fix. Perhaps by adding the missing option may solve this problem.

Andy & Wei on behalf of Ilija

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants