Komisches CRON-Verhalten seit Update auf 6.3-6

B

Bob22

New Member
Sep 11, 2019
17
0
1
32
Gestern habe ich auf Proxmox 6.3-6 geupdated, seitdem läuft jede Stunde ein Cronjob, der sich merkwürdig verhält:

Code: 
Apr 22 15:30:01 server1 CRON[19416]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 15:30:01 server1 CRON[19417]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Apr 22 15:30:01 server1 CRON[19416]: pam_unix(cron:session): session closed for user root
Apr 22 15:34:30 server1 systemd[1]: Started Run anacron jobs.
Apr 22 15:34:30 server1 anacron[20947]: Anacron 2.3 started on 2021-04-22
Apr 22 15:34:30 server1 anacron[20947]: Normal exit (0 jobs run)
Apr 22 15:34:30 server1 systemd[1]: anacron.service: Succeeded.
Apr 22 15:35:01 server1 CRON[21125]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 15:35:01 server1 CRON[21126]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 22 15:35:01 server1 CRON[21125]: pam_unix(cron:session): session closed for user root
Apr 22 15:45:01 server1 CRON[24726]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 15:45:01 server1 CRON[24727]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 22 15:45:01 server1 CRON[24726]: pam_unix(cron:session): session closed for user root
Apr 22 15:55:01 server1 CRON[28201]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 15:55:01 server1 CRON[28202]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 22 15:55:01 server1 CRON[28201]: pam_unix(cron:session): session closed for user root
Apr 22 16:05:01 server1 CRON[31655]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 16:05:01 server1 CRON[31656]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 22 16:05:01 server1 CRON[31655]: pam_unix(cron:session): session closed for user root
Apr 22 16:15:01 server1 CRON[2933]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 16:15:01 server1 CRON[2934]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 22 16:15:01 server1 CRON[2933]: pam_unix(cron:session): session closed for user root
Apr 22 16:17:01 server1 CRON[3630]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 16:17:01 server1 CRON[3631]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 22 16:17:01 server1 CRON[3630]: pam_unix(cron:session): session closed for user root
Apr 22 16:25:01 server1 CRON[6413]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 16:25:01 server1 CRON[6414]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 22 16:25:01 server1 CRON[6413]: pam_unix(cron:session): session closed for user root
Apr 22 16:30:01 server1 CRON[8168]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 16:30:01 server1 CRON[8169]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Apr 22 16:30:01 server1 CRON[8168]: pam_unix(cron:session): session closed for user root
Apr 22 16:31:04 server1 systemd[1]: Started Run anacron jobs.
Apr 22 16:31:04 server1 anacron[8561]: Anacron 2.3 started on 2021-04-22
Apr 22 16:31:04 server1 anacron[8561]: Normal exit (0 jobs run)
Apr 22 16:31:04 server1 systemd[1]: anacron.service: Succeeded.
Apr 22 16:35:01 server1 CRON[9969]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 16:35:01 server1 CRON[9970]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 22 16:35:01 server1 CRON[9969]: pam_unix(cron:session): session closed for user root

Dasselbe Command wird wieder und wieder aufgerugen, aber es laufen gar keine Jobs - was passiert da?

Meine /etc/crontab:
Code: 
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# Example of job definition:
# .---------------- minute (0 - 59)
# |  .------------- hour (0 - 23)
# |  |  .---------- day of month (1 - 31)
# |  |  |  .------- month (1 - 12) OR jan,feb,mar,apr ...
# |  |  |  |  .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  * user-name command to be executed
17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

/etc/anacrontab
Code: 
# /etc/anacrontab: configuration file for anacron

# See anacron(8) and anacrontab(5) for details.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/root
LOGNAME=root

# These replace cron's entries
1       5       cron.daily      run-parts --report /etc/cron.daily
7       10      cron.weekly     run-parts --report /etc/cron.weekly
@monthly        15      cron.monthly    run-parts --report /etc/cron.monthly

Code: 
# /etc/cron.d/anacron: crontab entries for the anacron package

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

30 7-23 * * *   root    [ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi

/etc/cron.d/sysstat:
Code: 
# The first element of the path is a directory where the debian-sa1
# script is located
PATH=/usr/lib/sysstat:/usr/sbin:/usr/sbin:/usr/bin:/sbin:/bin

# Activity reports every 10 minutes everyday
5-55/10 * * * * root command -v debian-sa1 > /dev/null && debian-sa1 1 1

# Additional run at 23:59 to rotate the statistics file
59 23 * * * root command -v debian-sa1 > /dev/null && debian-sa1 60 2



Ich habe das Gefühl, dass es da zu irgendeiner Überschneidung kommt - oder ist das normal? Es macht die Logs leider relativ unübersichtlich.
 
die eintraege stammen vom sysstat paket.. wenn du die resultierenden daten nicht verwendest, kannst du den cron job auch disablen..
 
  • Like
Reactions: Moayad
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back