[SOLVED] logrotate Fehler

Discussion in 'Proxmox VE (Deutsch)' started by tony blue, May 19, 2018.

  1. tony blue

    tony blue New Member

    Joined:
    Dec 26, 2017
    Messages:
    17
    Likes Received:
    0
    Hallo,

    ich erhalte seit mehreren Wochen immer wieder Fehlermeldungen von logrotate:

    /etc/cron.daily/logrotate:
    error: destination /var/log/pveproxy/access.log.1.gz already exists, renaming to /var/log/pveproxy/access.log.1.gz-2018051900.backup
    error: error renaming already existing output file /var/log/pveproxy/access.log.1.gz to /var/log/pveproxy/access.log.1.gz-2018051900.backup: No such file or directory
    error: destination /var/log/pve-firewall.log.1.gz already exists, renaming to /var/log/pve-firewall.log.1.gz-2018051900.backup
    error: destination /var/log/kern.log.1.gz already exists, renaming to /var/log/kern.log.1.gz-2018051900.backup
    error: destination /var/log/auth.log.1.gz already exists, renaming to /var/log/auth.log.1.gz-2018051900.backup
    error: error renaming already existing output file /var/log/auth.log.1.gz to /var/log/auth.log.1.gz-2018051900.backup: No such file or directory
    run-parts: /etc/cron.daily/logrotate exited with return code 1

    /etc/cron.daily/logrotate:
    error: failed to rename /var/log/apt/history.log to (null): No such file or directory
    error: failed to rename /var/log/pveproxy/access.log to (null): No such file or directory
    error: destination /var/log/mail.info.1.gz already exists, renaming to /var/log/mail.info.1.gz-2018051900.backup
    error: destination /var/log/daemon.log.1.gz already exists, renaming to /var/log/daemon.log.1.gz-2018051900.backup
    error: destination /var/log/messages.1.gz already exists, renaming to /var/log/messages.1.gz-2018051900.backup
    error: error renaming temp state file /var/lib/logrotate/status.tmp
    run-parts: /etc/cron.daily/logrotate exited with return code 1

    /etc/cron.daily/logrotate:
    error: destination /var/log/apt/history.log.1.gz already exists, renaming to /var/log/apt/history.log.1.gz-2018051900.backup
    error: error renaming already existing output file /var/log/apt/history.log.1.gz to /var/log/apt/history.log.1.gz-2018051900.backup: No such file or directory
    error: destination /var/log/alternatives.log.1.gz already exists, renaming to /var/log/alternatives.log.1.gz-2018051900.backup
    error: failed to rename /var/log/alternatives.log to (null): No such file or directory
    error: destination /var/log/pveproxy/access.log.1.gz already exists, renaming to /var/log/pveproxy/access.log.1.gz-2018051900.backup
    error: error renaming already existing output file /var/log/pveproxy/access.log.1.gz to /var/log/pveproxy/access.log.1.gz-2018051900.backup: No such file or directory
    error: failed to rename /var/log/pve-firewall.log to (null): No such file or directory
    error: destination /var/log/mail.log.1.gz already exists, renaming to /var/log/mail.log.1.gz-2018051900.backup
    error: destination /var/log/kern.log.1.gz already exists, renaming to /var/log/kern.log.1.gz-2018051900.backup
    error: destination /var/log/auth.log.1.gz already exists, renaming to /var/log/auth.log.1.gz-2018051900.backup
    error: destination /var/log/messages.1.gz already exists, renaming to /var/log/messages.1.gz-2018051900.backup
    error: error renaming already existing output file /var/log/messages.1.gz to /var/log/messages.1.gz-2018051900.backup: No such file or directory
    error: error renaming temp state file /var/lib/logrotate/status.tmp
    run-parts: /etc/cron.daily/logrotate exited with return code 1

    Es handelt sich um ein seit wenigen Monaten installiertes Proxmox. An Logrotate habe ich keine Änderungen vorgenommen.

    Hat jemand eine Idee, was diese Fehlermeldung auslöst oder wie ich dieses Problem lösen kann?


    Vielen Dank!

    Tony
     
  2. wolfgang

    wolfgang Proxmox Staff Member
    Staff Member

    Joined:
    Oct 1, 2014
    Messages:
    3,356
    Likes Received:
    191
    Hi,

    kannst du bitte deine verwendete Version schicken.

    Code:
    pveversion -v
    
     
  3. tony blue

    tony blue New Member

    Joined:
    Dec 26, 2017
    Messages:
    17
    Likes Received:
    0
    Gerne:

    pveversion -v
    proxmox-ve: 5.1-43 (running kernel: 4.13.13-6-pve)
    pve-manager: 5.1-52 (running version: 5.1-52/ba597a64)
    pve-kernel-4.13: 5.1-44
    pve-kernel-4.15: 5.1-4
    pve-kernel-4.15.17-1-pve: 4.15.17-8
    pve-kernel-4.13.16-2-pve: 4.13.16-48
    pve-kernel-4.13.13-6-pve: 4.13.13-42
    pve-kernel-4.13.13-5-pve: 4.13.13-38
    pve-kernel-4.13.13-2-pve: 4.13.13-33
    corosync: 2.4.2-pve5
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: 1.2-2
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.0-8
    libpve-apiclient-perl: 2.0-4
    libpve-common-perl: 5.0-31
    libpve-guest-common-perl: 2.0-15
    libpve-http-server-perl: 2.0-8
    libpve-storage-perl: 5.0-21
    libqb0: 1.0.1-1
    lvm2: 2.02.168-pve6
    lxc-pve: 3.0.0-3
    lxcfs: 3.0.0-1
    novnc-pve: 0.6-4
    proxmox-widget-toolkit: 1.0-17
    pve-cluster: 5.0-27
    pve-container: 2.0-22
    pve-docs: 5.1-17
    pve-firewall: 3.0-8
    pve-firmware: 2.0-4
    pve-ha-manager: 2.0-5
    pve-i18n: 1.0-4
    pve-libspice-server1: 0.12.8-3
    pve-qemu-kvm: 2.11.1-5
    pve-xtermjs: 1.0-3
    qemu-server: 5.0-25
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    zfsutils-linux: 0.7.8-pve1~bpo9
     
  4. wolfgang

    wolfgang Proxmox Staff Member
    Staff Member

    Joined:
    Oct 1, 2014
    Messages:
    3,356
    Likes Received:
    191
    Please update to the current version and check again.
     
  5. tony blue

    tony blue New Member

    Joined:
    Dec 26, 2017
    Messages:
    17
    Likes Received:
    0
    OK. Ich habe ein update auf die neueste Version gemacht:

    pveversion -v
    proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)
    pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
    pve-kernel-4.15: 5.2-2
    pve-kernel-4.13: 5.1-45
    pve-kernel-4.15.17-2-pve: 4.15.17-10
    pve-kernel-4.15.17-1-pve: 4.15.17-9
    pve-kernel-4.13.16-3-pve: 4.13.16-49
    pve-kernel-4.13.16-2-pve: 4.13.16-48
    pve-kernel-4.13.13-6-pve: 4.13.13-42
    pve-kernel-4.13.13-5-pve: 4.13.13-38
    pve-kernel-4.13.13-2-pve: 4.13.13-33
    corosync: 2.4.2-pve5
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: 1.2-2
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.0-8
    libpve-apiclient-perl: 2.0-4
    libpve-common-perl: 5.0-31
    libpve-guest-common-perl: 2.0-16
    libpve-http-server-perl: 2.0-8
    libpve-storage-perl: 5.0-23
    libqb0: 1.0.1-1
    lvm2: 2.02.168-pve6
    lxc-pve: 3.0.0-3
    lxcfs: 3.0.0-1
    novnc-pve: 0.6-4
    proxmox-widget-toolkit: 1.0-18
    pve-cluster: 5.0-27
    pve-container: 2.0-23
    pve-docs: 5.2-4
    pve-firewall: 3.0-9
    pve-firmware: 2.0-4
    pve-ha-manager: 2.0-5
    pve-i18n: 1.0-5
    pve-libspice-server1: 0.12.8-3
    pve-qemu-kvm: 2.11.1-5
    pve-xtermjs: 1.0-5
    qemu-server: 5.0-26
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    zfsutils-linux: 0.7.9-pve1~bpo9

    Leider erhalte ich immer noch die gleichen Logrotate-Fehler:

    /etc/cron.daily/logrotate:
    error: destination /var/log/apt/term.log.1.gz already exists, renaming to /var/log/apt/term.log.1.gz-2018060200.backup
    error: error opening /var/log/dpkg.log: No such file or directory
    error: destination /var/log/syslog.1.gz already exists, renaming to /var/log/syslog.1.gz-2018060200.backup
    error: destination /var/log/daemon.log.1.gz already exists, renaming to /var/log/daemon.log.1.gz-2018060200.backup
    error: destination /var/log/kern.log.1.gz already exists, renaming to /var/log/kern.log.1.gz-2018060200.backup
    error: error renaming already existing output file /var/log/kern.log.1.gz to /var/log/kern.log.1.gz-2018060200.backup: No such file or directory
    error: destination /var/log/auth.log.1.gz already exists, renaming to /var/log/auth.log.1.gz-2018060200.backup
    error: destination /var/log/user.log.1.gz already exists, renaming to /var/log/user.log.1.gz-2018060200.backup
    error: error renaming already existing output file /var/log/user.log.1.gz to /var/log/user.log.1.gz-2018060200.backup: No such file or directory
    error: error opening /var/log/btmp.2: No such file or directory
    run-parts: /etc/cron.daily/logrotate exited with return code 1

    /etc/cron.daily/logrotate:
    error: destination /var/log/dpkg.log.1.gz already exists, renaming to /var/log/dpkg.log.1.gz-2018060200.backup
    error: error opening /var/log/pve-firewall.log.8.gz: No such file or directory
    error: destination /var/log/daemon.log.1.gz already exists, renaming to /var/log/daemon.log.1.gz-2018060200.backup
    error: destination /var/log/kern.log.1.gz already exists, renaming to /var/log/kern.log.1.gz-2018060200.backup
    error: error renaming already existing output file /var/log/kern.log.1.gz to /var/log/kern.log.1.gz-2018060200.backup: No such file or directory
    error: destination /var/log/user.log.1.gz already exists, renaming to /var/log/user.log.1.gz-2018060200.backup
    error: error renaming temp state file /var/lib/logrotate/status.tmp
    run-parts: /etc/cron.daily/logrotate exited with return code 1

    Woran könnte das liegen?

    Vielen Dank!

    Tony
     
  6. wolfgang

    wolfgang Proxmox Staff Member
    Staff Member

    Joined:
    Oct 1, 2014
    Messages:
    3,356
    Likes Received:
    191
    Wahrscheinlich hast du einen doppelten Eintrag oder eine falsche config.

    Das könnte dir helfen

    Code:
    man logrotate
    
     
  7. tony blue

    tony blue New Member

    Joined:
    Dec 26, 2017
    Messages:
    17
    Likes Received:
    0
    Nachdem ich die Proxmox-Installation auf ZFS umgestellt habe, habe ich alles neu installiert. Bisher ist der Fehler nicht mehr aufgetaucht.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice