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

Put daemon.log under faster rotation #3055

Open
justinsb opened this issue Jul 26, 2017 · 7 comments
Open

Put daemon.log under faster rotation #3055

justinsb opened this issue Jul 26, 2017 · 7 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone

Comments

@justinsb
Copy link
Member

We need to make sure that all our log files rotate sufficiently fast, e.g. daemon.log is currently defaulting to weekly rotation.

(Likely a dup of some others, but this is a work-tracking issue rather than a general issue)

@justinsb justinsb added this to the 1.7.1 milestone Jul 26, 2017
@krogon-dp
Copy link
Contributor

#2816 #3047

@cmaloney
Copy link

cmaloney commented Sep 8, 2017

Would it be feasible to make it so that someone could disable the rsyslogd/classic log handling, and just rely on journald/journalctl (Possibly opt in). journald is much better at not allowing disk space to fill up (Works when messages come in for rotation / fixed size log, rather than trying to "guess" when files will get so big they need to be rotated).

Definitely journald is a sysadmin consideration, and has other behaviors which people may/may not like, but would give people who can/want to move to it (esp. since things already log to it) an option to fairly simply solve this.

@chrislovecnm
Copy link
Contributor

Move to 1.9?

@chrislovecnm chrislovecnm modified the milestones: 1.7.1, 1.9 Nov 23, 2017
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 21, 2018
@blakebarnett
Copy link

doesn't seem like a release blocker

@chrislovecnm
Copy link
Contributor

I agree ...

/lifecycle frozen
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 22, 2018
@justinsb justinsb modified the milestones: 1.9.0, 1.10 May 26, 2018
@justinsb justinsb modified the milestones: 1.10, 1.12 Mar 14, 2019
@mikesplain
Copy link
Contributor

I was taking a look at this, @justinsb what's the best way to do this? I don't see a existing task to modify a config file. Logrotate doesn't support duplicates so, should we modify the overrides in /var/log/rsyslog?

@rifelpet rifelpet modified the milestones: v1.12, backlog Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

9 participants