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

Failed Units #2510

Open
oded-dd opened this Issue Oct 16, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@oded-dd

oded-dd commented Oct 16, 2018

Issue Report

There are failed unit on CoreOS (1855.4.0)

Bug

Container Linux Version

NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1855.4.0
VERSION_ID=1855.4.0
BUILD_ID=2018-09-11-0003
PRETTY_NAME="Container Linux by CoreOS 1855.4.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

AWS

What hardware/cloud provider/hypervisor is being used to run Container Linux?

Expected Behavior

We are getting logrotate.service failed units on all our CoreOS instances
See attached the logrotate configuration

# create new (empty) log files after rotating old ones.
create

# use date as a suffix of the rotated file.
dateext

# compress rotated log files.
compress

missingok
notifempty
nomail
noolddir

# accept user provided configuration files in /etc.
include /etc/logrotate.d

# must match creation rules in /usr/lib/tmpfiles.d/var.conf
/var/log/wtmp {
    create 0664 root utmp
    size 1M
}
/var/log/btmp {
    create 0600 root utmp
    size 1M
}

Actual Behavior

Reproduction Steps

  1. ...
  2. ...

Other Information

@lucab

This comment has been minimized.

Member

lucab commented Oct 16, 2018

@oded-dd what does sudo journalctl -b 0 -u logrotate.service say?

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