[Bug 954375] New: package logrotate is missing logrotate.service, logrotate.timer
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 Bug ID: 954375 Summary: package logrotate is missing logrotate.service, logrotate.timer Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: bug-report-12204@forward.cat QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Package logrotate in Version 3.8.7-7.1 is missing the files: logrotate.service logrotate.timer These were present as of opensuse 13.2 . The file logrotate.timer is required by the line: enable logrotate.timer in file /usr/lib/systemd/system-preset/90-default-openSUSE.preset of package systemd-presets-branding-openSUSE-0.3.0-23.2.noarch . Instead it is called via /etc/cron.daily/logrotate . I guess this change (among others) from Changes is missing:" - Migrate from cron to systemd timer units, this is overall the most important package to migrate since it is one of the very few base components that hard-require cron." The package from Leap should be updated to latest in 13.2 (or) "enable logrotate.timer" should be removed from /usr/lib/systemd/system-preset/90-default-openSUSE.preset . -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c2 --- Comment #2 from Paul Pfeiffer <bug-report-12204@forward.cat> --- I can confirm that there is no conflict. There is only a lot of lines (during install) in the log: systemd[1]: Cannot add dependency job for unit logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such file or directory. With some unrelated logging problem it took me some time to figure out why the file is missing. I thought somebody might have overseen that leap is not migrated here. Is there some information about it on the web? Like what services get migrated back when upgrading 13.2->42.1 . Are there any plans for porting the rest to systemd in leap? Are such cases handled via openfate? I would have been happy if there would have been a line in the Release Notes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c4 Kristyna Streitova <kstreitova@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@suse.com --- Comment #4 from Kristyna Streitova <kstreitova@suse.com> --- Adding Stephan Kulow to CC. @coolo: Would you please be so kind and answer the questions about Leap from comment 2? Thanks in advance! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c5 --- Comment #5 from Stephan Kulow <coolo@suse.com> --- No, there is no such list - but I suppose switching logrotate in SLE12 to use systemd is something we should do. And then leap will get the same. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 Javier Llorente <javier@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |javier@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |9b3e05a5@opayq.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c8 Archie Cobbs <archie.cobbs@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |archie.cobbs@gmail.com --- Comment #8 from Archie Cobbs <archie.cobbs@gmail.com> --- Since this bug is not fixed yet, what is the recommended workaround in the meantime? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c9 --- Comment #9 from Kristyna Streitova <kstreitova@suse.com> --- (In reply to Archie Cobbs from comment #8)
Since this bug is not fixed yet, what is the recommended workaround in the meantime?
As Marcus said in the comment 1, the absence of the systemd timer isn't critical. It only adds some "there is no such file" warnings. Therefore, there is no special workaround needed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c10 --- Comment #10 from Archie Cobbs <archie.cobbs@gmail.com> --- (In reply to Kristyna Streitova from comment #9)
(In reply to Archie Cobbs from comment #8)
Since this bug is not fixed yet, what is the recommended workaround in the meantime?
As Marcus said in the comment 1, the absence of the systemd timer isn't critical. It only adds some "there is no such file" warnings. Therefore, there is no special workaround needed.
OK thanks. What I meant was a workaround that stops the annoying messages (I get a text message every time one of my servers logs a warning to /var/log/warn). Will this work? (I don't know the syntax for these files) --- 90-default-openSUSE.preset.orig 2016-04-14 10:19:29.061551868 -0500 +++ 90-default-openSUSE.preset 2016-04-14 10:19:35.174795098 -0500 @@ -16,7 +16,7 @@ enable iscsid.socket enable iscsi.service enable epmd.socket -enable logrotate.timer +#enable logrotate.timer enable haveged.service enable irqbalance.service enable auditd.service Then what? systemctl daemon-reexec ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c12 andreas bittner <abittner@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abittner@opensuse.org --- Comment #12 from andreas bittner <abittner@opensuse.org> --- Is this bug going anywhere? Is leap 42.1 gonna get a properly working logrotate? I am seeing lot loglines and pollution about this logrotate stuff not working May 31 17:33:10 tux01 systemd[1]: Cannot add dependency job for unit logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such file or directory. 42.1 (came from previous 13.2 or maybe even earlier). Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954375 http://bugzilla.opensuse.org/show_bug.cgi?id=954375#c14 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |per@computer.org Resolution|--- |FIXED --- Comment #14 from Per Jessen <per@computer.org> --- opensuse Leap 421 has reached end-of-life and is no longer being maintained. As of Leap423, logrotate moved from being cron-driven to a systemd timer, and now includes the logrotate.service and logrotate.timer units. The timer still needs being activated though, see bug#1054353 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com