Openleap16 and logrotate 3.22: Script logrotate-all conflicts with include directive

Updating from OpenLeap 15.6 to 16 I encountered this problem: logrotate.service now uses ExecStart=/usr/sbin/logrotate-all which collects all possible config-files. If either /usr/etc/logrotate.conf or /etc/logrotate.conf contains the line include logrotate.d then logrotate produces an “duplicate log entry” error for all files in logrotate.d. For decades (?) I have used include logrotate.d in my /etc/logrotate.conf, so this threw me a bit. In /usr/etc/logrotate.conf the line has been wisely commented out. Either do this also in your private /etc/logrotate.conf or change the ExecStart line.

Hi, welcome

A couple of things:

  • There is no such thing as OpenLeap. It’s called just Leap. The distro is part of the openSUSE Project ( a lot more than just the distros )
  • Please use preformatted text ( </> in the edit window ) to post output etc.
  • Question: how did you perform the upgrade 15.6 → 16.0
1 Like

Thanks for your reply. Have yet to find out about preformatted text in this forum. Next time, I promise.
I used the opensuse-migration-tool. For a couple of test installations it worked, for some it didn’t.

I edited your post, using some markdown. That makes reading more easy, since it shows the system more clearly.

Don’t ever touch stuff in /usr/etc/ since everything in there is owned by packages. An update will destroy your changes, the way to change defaults is through snippets in /etc/$whatever.d/
Could you please show your repos? zypper lr -d

1 Like

Thanks again. I never change things in /usr/etc.
Here is the output of zypper lr -d. From the repo-non-oss I use only nmap.

# | Alias                            | Name                                     | Enabled | GPG Check | Refresh | Keep | Priority | Type   | URI
--+----------------------------------+------------------------------------------+---------+-----------+---------+------+----------+--------+-----------------------------------------------------------------------
1 | Leap                             | Leap 16.0                                | Nein    | ----      | ----    | -    |   99     | rpm-md | hd:/install?device=/dev/disk/by-id/usb-UFD_3.0_Silicon-Power16G_P20022
2 | devel_languages_python_backports | Backport builds of Python Modules (16.0) | Nein    | ----      | ----    | -    |   99     | rpm-md | https://download.opensuse.org/repositories/devel:/languages:/python:/b
3 | openSUSE:repo-non-oss            | repo-non-oss (16.0)                      | Ja      | (r ) Ja   | Ja      | -    |   99     | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss/x86_64
4 | openSUSE:repo-non-oss-debug      | repo-non-oss-debug (16.0)                | Nein    | ----      | ----    | -    |   99     | N/A    | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/non-oss/x86_
5 | openSUSE:repo-openh264           | repo-openh264 (16.0)                     | Ja      | (r ) Ja   | Ja      | -    |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap_16
6 | openSUSE:repo-oss                | repo-oss (16.0)                          | Ja      | (r ) Ja   | Ja      | -    |   99     | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/x86_64
7 | openSUSE:repo-oss-debug          | repo-oss-debug (16.0)                    | Nein    | ----      | ----    | -    |   99     | N/A    | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/oss/x86_64
8 | openSUSE:repo-oss-source         | repo-oss-source (16.0)                   | Nein    | ----      | ----    | -    |   99     | N/A    | http://cdn.opensuse.org/source/distribution/leap/16.0/repo/oss

You can / should remove #1 ( it’s the installer USB ).
Most likely you could/should also remove #2, it may lead to conflicts.

Even if those repos aren’t enabled? Didn’t know this.

Conflicts with what you have installed.

Good to know. Thanks.

@wogrow25 I’d suggest zypper -vvv dup --allow-vendor-change to see what the damage may be…

Thanks. I still have one server to upgrade. I will see what this reports. But not in the next days.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.