Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: New logrotate errors in journal.

  1. #11
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,352
    Blog Entries
    5

    Default Re: New logrotate errors in journal.

    More trouble:
    Code:
    erlangen:~ # journalctl -b -u logrotate.service 
    Sep 10 21:22:12 erlangen systemd[1]: Starting Rotate log files... 
    Sep 10 21:22:12 erlangen sh[6842]: error: destination /var/log/zypper.log-20220910.xz already exists, skipping rotation 
    Sep 10 21:22:12 erlangen systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
    Sep 10 21:22:12 erlangen systemd[1]: logrotate.service: Failed with result 'exit-code'.
    Sep 10 21:22:12 erlangen systemd[1]: Failed to start Rotate log files.
    erlangen:~ #
    
    
    
    openSUSE Tumbleweed, KDE Plasma, Blogs/KeepItSimple, i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X, 5700U (2022)

  2. #12

    Default Re: New logrotate errors in journal.

    Quote Originally Posted by arvidjaar View Post
    Code:
    bor@tw:~> rpm -q --changelog libzypp
    * Fri Sep 02 2022 ma@suse.de
    - UsrEtc: Store logrotate files in %{_distconfdir} if defined
      (fixes #402)
    That is the last update I got before the errors started appearing. So, is that the regression I should report the bug against? I created the file in /etc/logrotate.d for the reasons mentioned by arvidjaar, it's preserved across updates.

    Gene

  3. #13

    Default Re: New logrotate errors in journal.

    I added a commen to this bug, https://bugzilla.opensuse.org/show_bug.cgi?id=1173319.

    Gene

  4. #14

    Default Re: New logrotate errors in journal.

    Quote Originally Posted by karlmistelberger View Post
    More trouble:
    Code:
    erlangen:~ # journalctl -b -u logrotate.service 
    Sep 10 21:22:12 erlangen systemd[1]: Starting Rotate log files... 
    Sep 10 21:22:12 erlangen sh[6842]: error: destination /var/log/zypper.log-20220910.xz already exists, skipping rotation 
    Sep 10 21:22:12 erlangen systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
    Sep 10 21:22:12 erlangen systemd[1]: logrotate.service: Failed with result 'exit-code'.
    Sep 10 21:22:12 erlangen systemd[1]: Failed to start Rotate log files.
    erlangen:~ #
    
    
    
    You might want to add a comment to https://bugzilla.opensuse.org/show_bug.cgi?id=1173319, because my earlier comment has generated a response. The responder can reproduce my error and is working on it.

    Gene

  5. #15
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,352
    Blog Entries
    5

    Default Re: New logrotate errors in journal.

    Quote Originally Posted by Gene_S View Post
    You might want to add a comment to https://bugzilla.opensuse.org/show_bug.cgi?id=1173319, because my earlier comment has generated a response. The responder can reproduce my error and is working on it.
    Machines are up to date:
    Code:
    Operating System: openSUSE Tumbleweed 20220910
    KDE Plasma Version: 5.25.5
    KDE Frameworks Version: 5.97.0
    Qt Version: 5.15.5
    Kernel Version: 5.19.8-1-default (64-bit)
    Graphics Platform: X11
    Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
    Memory: 31.3 GiB of RAM
    Graphics Processor: AMD Radeon RX 550 / 550 Series
    Manufacturer: Micro-Star International Co., Ltd.
    Product Name: MS-7C56
    System Version: 2.0
    logrotate works:
    Code:
    erlangen:~ # systemctl status logrotate 
    ○ logrotate.service - Rotate log files 
         Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static) 
         Active: inactive (dead) since Mon 2022-09-12 18:12:05 CEST; 10s ago 
    TriggeredBy:  logrotate.timer 
           Docs: man:logrotate(8) 
                 man:logrotate.conf(5) 
        Process: 3888 ExecStartPre=/bin/sh -c /usr/bin/systemctl set-environment etc_conf= (code=exited, status=0/SUCCESS) 
        Process: 3891 ExecStartPre=/bin/sh -c if [ -f /etc/logrotate.conf ]; then /usr/bin/systemctl set-environment etc_conf=/etc/logrotate.conf; fi (code=exited, status=0/SUCCESS) 
        Process: 3895 ExecStartPre=/bin/sh -c /usr/bin/systemctl set-environment etc_dir= (code=exited, status=0/SUCCESS) 
        Process: 3896 ExecStartPre=/bin/sh -c if [ -d /etc/logrotate.d ]; then /usr/bin/systemctl set-environment etc_dir=/etc/logrotate.d; fi (code=exited, status=0/SUCCESS) 
        Process: 3898 ExecStart=/bin/sh -c /usr/sbin/logrotate /usr/etc/logrotate.conf ${etc_conf} ${etc_dir} (code=exited, status=0/SUCCESS) 
       Main PID: 3898 (code=exited, status=0/SUCCESS) 
            CPU: 98ms 
    
    Sep 12 18:12:05 erlangen systemd[1]: Starting Rotate log files... 
    Sep 12 18:12:05 erlangen systemd[1]: logrotate.service: Deactivated successfully. 
    Sep 12 18:12:05 erlangen systemd[1]: Finished Rotate log files. 
    erlangen:~ #
    
    
    
    openSUSE Tumbleweed, KDE Plasma, Blogs/KeepItSimple, i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X, 5700U (2022)

  6. #16

    Default Re: New logrotate errors in journal.

    Good that it's working now. Mine is as well, now that I merged my changes into the /usr/etc/logrotate.d file. However, I'll have to add them back the next time that package is updated.

    Gene

  7. #17

    Default Re: New logrotate errors in journal.

    The latest version of logrotate, logrotate-3.20.1-3.1, fixes this issue. You can now use a zypp-history.lr file in /etc/logrotate.d to override the package files in /usr/etc/logrotate.d without errors. Thanks to Stefan Schubert for fixing this issue in https://bugzilla.opensuse.org/show_bug.cgi?id=1173319.

    Gene

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •