Daily Cleanup once per minute in rocky 9?

The log file /var/log/messages in my rocky9 shows that the “Daily Cleanup of User’s Temporary Directories” seams running once per minute not in Dailly. Is this normal?

Here is the logs: ( once per minus since the boot-up of the system )

Nov 16 08:23:11 hostname systemd[1]: user@0.service: Deactivated successfully.
Nov 16 08:23:11 hostname systemd[1]: Stopped User Manager for UID 0.
Nov 16 08:23:11 hostname systemd[1]: Stopping User Runtime Directory /run/user/0...
Nov 16 08:23:11 hostname systemd[1]: run-user-0.mount: Deactivated successfully.
Nov 16 08:23:11 hostname systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Nov 16 08:23:11 hostname systemd[1]: Stopped User Runtime Directory /run/user/0.
Nov 16 08:23:11 hostname systemd[1]: Removed slice User Slice of UID 0.
Nov 16 08:24:01 hostname systemd[1]: Created slice User Slice of UID 0.
Nov 16 08:24:01 hostname systemd[1]: Starting User Runtime Directory /run/user/0...
Nov 16 08:24:01 hostname systemd[1]: Finished User Runtime Directory /run/user/0.
Nov 16 08:24:01 hostname systemd[1]: Starting User Manager for UID 0...
Nov 16 08:24:01 hostname systemd[2058053]: Queued start job for default target Main User Target.
Nov 16 08:24:01 hostname systemd[2058053]: Created slice User Application Slice.
Nov 16 08:24:01 hostname systemd[2058053]: Mark boot as successful after the user session has run 2 minutes was skipped because of a failed condition check (ConditionUser=!@system).
Nov 16 08:24:01 hostname systemd[2058053]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 08:24:01 hostname systemd[2058053]: Reached target Paths.
Nov 16 08:24:01 hostname systemd[2058053]: Reached target Timers.
Nov 16 08:24:01 hostname systemd[2058053]: Starting D-Bus User Message Bus Socket...
Nov 16 08:24:01 hostname systemd[2058053]: PipeWire PulseAudio was skipped because of a failed condition check (ConditionUser=!root).
Nov 16 08:24:01 hostname systemd[2058053]: Listening on PipeWire Multimedia System Socket.
Nov 16 08:24:01 hostname systemd[2058053]: Starting Create User's Volatile Files and Directories...
Nov 16 08:24:01 hostname systemd[2058053]: Finished Create User's Volatile Files and Directories.
Nov 16 08:24:01 hostname systemd[2058053]: Listening on D-Bus User Message Bus Socket.
Nov 16 08:24:01 hostname systemd[2058053]: Reached target Sockets.
Nov 16 08:24:01 hostname systemd[2058053]: Reached target Basic System.
Nov 16 08:24:01 hostname systemd[2058053]: Reached target Main User Target.
Nov 16 08:24:01 hostname systemd[2058053]: Startup finished in 114ms.
Nov 16 08:24:01 hostname systemd[1]: Started User Manager for UID 0.
Nov 16 08:24:01 hostname systemd[1]: Started Session 1425 of User root.
Nov 16 08:24:01 hostname systemd[1]: session-1425.scope: Deactivated successfully.
Nov 16 08:24:11 hostname systemd[1]: Stopping User Manager for UID 0...
Nov 16 08:24:11 hostname systemd[2058053]: Activating special unit Exit the Session...
Nov 16 08:24:11 hostname systemd[2058053]: Stopped target Main User Target.
Nov 16 08:24:11 hostname systemd[2058053]: Stopped target Basic System.
Nov 16 08:24:11 hostname systemd[2058053]: Stopped target Paths.
Nov 16 08:24:11 hostname systemd[2058053]: Stopped target Sockets.
Nov 16 08:24:11 hostname systemd[2058053]: Stopped target Timers.
Nov 16 08:24:11 hostname systemd[2058053]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 08:24:11 hostname systemd[2058053]: Closed D-Bus User Message Bus Socket.
Nov 16 08:24:11 hostname systemd[2058053]: Closed PipeWire Multimedia System Socket.
Nov 16 08:24:11 hostname systemd[2058053]: Stopped Create User's Volatile Files and Directories.
Nov 16 08:24:11 hostname systemd[2058053]: Removed slice User Application Slice.
Nov 16 08:24:11 hostname systemd[2058053]: Reached target Shutdown.
Nov 16 08:24:11 hostname systemd[2058053]: Finished Exit the Session.
Nov 16 08:24:11 hostname systemd[2058053]: Reached target Exit the Session.
Nov 16 08:24:11 hostname systemd[1]: user@0.service: Deactivated successfully.
Nov 16 08:24:11 hostname systemd[1]: Stopped User Manager for UID 0.
Nov 16 08:24:11 hostname systemd[1]: Stopping User Runtime Directory /run/user/0...
Nov 16 08:24:11 hostname systemd[1]: run-user-0.mount: Deactivated successfully.
Nov 16 08:24:11 hostname systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Nov 16 08:24:11 hostname systemd[1]: Stopped User Runtime Directory /run/user/0.
Nov 16 08:24:11 hostname systemd[1]: Removed slice User Slice of UID 0.
Nov 16 08:25:01 hostname systemd[1]: Created slice User Slice of UID 0.
Nov 16 08:25:01 hostname systemd[1]: Starting User Runtime Directory /run/user/0...
Nov 16 08:25:01 hostname systemd[1]: Started Session 1428 of User apache.
Nov 16 08:25:01 hostname systemd[1]: Finished User Runtime Directory /run/user/0.
Nov 16 08:25:01 hostname systemd[1]: Starting User Manager for UID 0...
Nov 16 08:25:01 hostname systemd[2058262]: Queued start job for default target Main User Target.
Nov 16 08:25:01 hostname systemd[2058262]: Created slice User Application Slice.
Nov 16 08:25:01 hostname systemd[2058262]: Mark boot as successful after the user session has run 2 minutes was skipped because of a failed condition check (ConditionUser=!@system).
Nov 16 08:25:01 hostname systemd[2058262]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 08:25:01 hostname systemd[2058262]: Reached target Paths.
Nov 16 08:25:01 hostname systemd[2058262]: Reached target Timers.
Nov 16 08:25:01 hostname systemd[2058262]: Starting D-Bus User Message Bus Socket...
Nov 16 08:25:01 hostname systemd[2058262]: PipeWire PulseAudio was skipped because of a failed condition check (ConditionUser=!root).
Nov 16 08:25:01 hostname systemd[2058262]: Listening on PipeWire Multimedia System Socket.
Nov 16 08:25:01 hostname systemd[2058262]: Starting Create User's Volatile Files and Directories...
Nov 16 08:25:01 hostname systemd[2058262]: Finished Create User's Volatile Files and Directories.
Nov 16 08:25:01 hostname systemd[2058262]: Listening on D-Bus User Message Bus Socket.
Nov 16 08:25:01 hostname systemd[2058262]: Reached target Sockets.
Nov 16 08:25:01 hostname systemd[2058262]: Reached target Basic System.
Nov 16 08:25:01 hostname systemd[2058262]: Reached target Main User Target.
Nov 16 08:25:01 hostname systemd[2058262]: Startup finished in 116ms.

Mine seems to show like this:

[root@rocky9 ~]# cat /var/log/messages | grep -i daily

Nov 13 13:53:04 rocky9 systemd[8968]: Started Daily Cleanup of User's Temporary Directories.
Nov 13 13:53:59 rocky9 systemd[8968]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 14 09:54:24 rocky9 systemd[9586]: Started Daily Cleanup of User's Temporary Directories.
Nov 14 09:57:25 rocky9 systemd[9586]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 14 10:14:18 rocky9 systemd[10028]: Started Daily Cleanup of User's Temporary Directories.
Nov 14 10:15:44 rocky9 systemd[10028]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 14 20:02:23 rocky9 systemd[10532]: Started Daily Cleanup of User's Temporary Directories.
Nov 14 20:06:32 rocky9 systemd[10532]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 14 20:07:54 rocky9 systemd[10573]: Started Daily Cleanup of User's Temporary Directories.
Nov 14 20:08:44 rocky9 systemd[10573]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 15 21:25:24 rocky9 systemd[11374]: Started Daily Cleanup of User's Temporary Directories.
Nov 15 21:25:44 rocky9 systemd[11374]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 08:29:47 rocky9 systemd[11746]: Started Daily Cleanup of User's Temporary Directories.

as you can see I’ve filtered it so that the logs are clearer. You can see for example on Nov 14 that it runs a few times, but not every minute for 24 hours. Can you filter your logs more clearly using my example above - that way we can see exactly how often it is running on your system. But I expect it should be similar to the output I posted, unless something has changed on your server, or unless the number of times it runs, depends on the number of users on the system. But anyway we’ll see when the results are more filtered.

It does run every minute for 24 hours

Nov 16 00:11:01 hostname systemd[435699]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:11:11 hostname systemd[435699]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:12:01 hostname systemd[435836]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:12:11 hostname systemd[435836]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:13:01 hostname systemd[435946]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:13:12 hostname systemd[435946]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:14:02 hostname systemd[436081]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:14:12 hostname systemd[436081]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:15:01 hostname systemd[436200]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:15:11 hostname systemd[436200]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:16:01 hostname systemd[436342]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:16:11 hostname systemd[436342]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:17:01 hostname systemd[436454]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:17:11 hostname systemd[436454]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:18:01 hostname systemd[436574]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:18:12 hostname systemd[436574]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:19:02 hostname systemd[436689]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:19:12 hostname systemd[436689]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:20:01 hostname systemd[436821]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:20:30 hostname systemd[436821]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:21:01 hostname systemd[458363]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 00:21:11 hostname systemd[458363]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 00:22:01 hostname systemd[458514]: Started Daily Cleanup of User's Temporary Directories.
......
Nov 16 15:40:31 hostname systemd[3401804]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:41:01 hostname systemd[3423760]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:41:12 hostname systemd[3423760]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:42:02 hostname systemd[3423879]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:42:12 hostname systemd[3423879]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:43:01 hostname systemd[3423997]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:43:11 hostname systemd[3423997]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:44:01 hostname systemd[3424115]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:44:11 hostname systemd[3424115]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:45:01 hostname systemd[3424250]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:45:11 hostname systemd[3424250]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:46:01 hostname systemd[3424382]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:46:11 hostname systemd[3424382]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:47:01 hostname systemd[3424514]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:47:11 hostname systemd[3424514]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:48:01 hostname systemd[3424621]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:48:11 hostname systemd[3424621]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:49:01 hostname systemd[3424752]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:49:12 hostname systemd[3424752]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:50:02 hostname systemd[3424867]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:50:31 hostname systemd[3424867]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:51:01 hostname systemd[3446832]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:51:11 hostname systemd[3446832]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:52:01 hostname systemd[3446956]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:52:11 hostname systemd[3446956]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:53:01 hostname systemd[3447070]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:53:11 hostname systemd[3447070]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 16 15:54:01 hostname systemd[3447189]: Started Daily Cleanup of User's Temporary Directories.
Nov 16 15:54:12 hostname systemd[3447189]: Stopped Daily Cleanup of User's Temporary Directories.

Notice that my log shows failures like this:

Nov 16 08:24:01 hostname systemd[2058053]: Mark boot as successful after the user session has run 2 minutes was skipped because of a failed condition check (ConditionUser=!@system).
Nov 16 08:24:01 hostname systemd[2058053]: PipeWire PulseAudio was skipped because of a failed condition check (ConditionUser=!root).

However, I do not know what is that failure.

man systemd-tmpfiles states that both system and (each) user session runs their own systemd-tmpfiles-clean.timer and systemd-tmpfiles-clean.service

Run systemctl status systemd-tmpfiles-clean.timer as regular user. It should show time for next ‘Trigger’.

Run loginctl How many sessions are there?

1 Like

There are 7 sessions.

[root@hostname ~]# loginctl
SESSION  UID USER   SEAT  TTY
   4884 1000 user1        pts/0
   4886 1000 user1
   4893 1000 user1        pts/1
   4894 1000 user1
     c1 1001 user2
     c2   48 apache
     c4   42 gdm    seat0 tty1

7 sessions listed.

And the next ‘Trigger’ is not diffrent between root and regular user.

[root@hostname ~]# systemctl status systemd-tmpfiles-clean.timer
● systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.timer; static)
     Active: active (waiting) since Tue 2022-11-15 22:00:32 CST; 1 day 11h ago
      Until: Tue 2022-11-15 22:00:32 CST; 1 day 11h ago
    Trigger: Thu 2022-11-17 22:15:26 CST; 12h left
   Triggers: ● systemd-tmpfiles-clean.service
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)

Nov 15 22:00:32 nas systemd[1]: Started Daily Cleanup of Temporary Directories.

[user1@hostname ~]$ systemctl status systemd-tmpfiles-clean.timer
● systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.timer; static)
     Active: active (waiting) since Tue 2022-11-15 22:00:32 CST; 1 day 11h ago
      Until: Tue 2022-11-15 22:00:32 CST; 1 day 11h ago
    Trigger: Thu 2022-11-17 22:15:26 CST; 12h left
   Triggers: ● systemd-tmpfiles-clean.service
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)

[root@hostname ~]# sudo -u apache systemctl status systemd-tmpfiles-clean.timer
● systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.timer; static)
     Active: active (waiting) since Tue 2022-11-15 22:00:32 CST; 1 day 11h ago
      Until: Tue 2022-11-15 22:00:32 CST; 1 day 11h ago
    Trigger: Thu 2022-11-17 22:15:26 CST; 12h left
   Triggers: ● systemd-tmpfiles-clean.service
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)

I missed a “user” bit:

[root@xyz ~]# systemctl status systemd-tmpfiles-clean.timer
● systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.timer; static)
     Active: active (waiting) since Thu 2022-11-10 11:46:05 EET; 1 week 0 days ago
      Until: Thu 2022-11-10 11:46:05 EET; 1 week 0 days ago
    Trigger: Fri 2022-11-18 12:03:56 EET; 23h left
   Triggers: ● systemd-tmpfiles-clean.service
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)

Nov 10 11:46:05 cotton systemd[1]: Started Daily Cleanup of Temporary Directories.

[root@xyz ~]# systemctl --user status systemd-tmpfiles-clean.timer
Failed to connect to bus: No medium found

[jlehtone@xyz ~]$ systemctl --user status systemd-tmpfiles-clean.timer
● systemd-tmpfiles-clean.timer - Daily Cleanup of User's Temporary Directories
     Loaded: loaded (/usr/lib/systemd/user/systemd-tmpfiles-clean.timer; enabled; vendor preset: enabled)
     Active: active (waiting) since Tue 2022-11-15 09:43:57 EET; 2 days ago
      Until: Tue 2022-11-15 09:43:57 EET; 2 days ago
    Trigger: Fri 2022-11-18 09:51:46 EET; 21h left
   Triggers: ● systemd-tmpfiles-clean.service
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)

[jlehtone@xyz ~]$ systemctl status systemd-tmpfiles-clean.timer
● systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
     Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.timer; static)
     Active: active (waiting) since Thu 2022-11-10 11:46:05 EET; 1 week 0 days ago
      Until: Thu 2022-11-10 11:46:05 EET; 1 week 0 days ago
    Trigger: Fri 2022-11-18 12:03:56 EET; 23h left
   Triggers: ● systemd-tmpfiles-clean.service
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)

Do note how regular user has different access to information and that there are more than one timer:

  • /usr/lib/systemd/system/systemd-tmpfiles-clean.timer
  • /usr/lib/systemd/user/systemd-tmpfiles-clean.timer

Thank you all very much!

Besed on your reply, especially @jlehtone, I have got the reason of this issue.

This issue is come from the crontab, there is a minutely job in my crontab. So that, it will start a session of UID 0 (root) at every minute, and run Cleenup fellow that.

Here is my log: notes that the minutely job is disabled between 01:21:00 and 01:23:30.

[root@hostname ~]# grep Daily /var/log/messages | tail
Nov 18 01:17:01 hostname systemd[1167933]: Started Daily Cleanup of User's Temporary Directories.
Nov 18 01:17:31 hostname systemd[1167933]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 18 01:18:01 hostname systemd[1190748]: Started Daily Cleanup of User's Temporary Directories.
Nov 18 01:18:32 hostname systemd[1190748]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 18 01:19:02 hostname systemd[1213575]: Started Daily Cleanup of User's Temporary Directories.
Nov 18 01:19:32 hostname systemd[1213575]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 18 01:20:01 hostname systemd[1236415]: Started Daily Cleanup of User's Temporary Directories.
Nov 18 01:20:46 hostname systemd[1236415]: Stopped Daily Cleanup of User's Temporary Directories.
Nov 18 01:24:01 hostname systemd[1282693]: Started Daily Cleanup of User's Temporary Directories.
Nov 18 01:24:11 hostname systemd[1282693]: Stopped Daily Cleanup of User's Temporary Directories.

the systemctl --user status systemd-tmpfiles-clean.timer in my machine is similar to your results

This issue is come from the crontab, there is a minutely job in my crontab. So that, it will start a session of UID 0 (root) at every minute, and run Cleenup fellow that.

By the way, I just checked it in rocky8. The same crontab could not results in this Daily Cleanup issue in rocky8.
So, it is a little strange in rocky9.

Or, crontab is no longer the recommended package in RHEL9?

The systemd (units, timers) is probably the primary method, but one can still use cron too.
You just don’t want them both redundantly start the same tasks.

However, what did create that cron job for your root?

Yes, that’s the part I want to know too.

I am using a bash-shell-script to collect additional information for ganglia, such as collect the temperature of cpus:

#!/bin/bash
# this script read the cpu package temperature using lm-sensors then send it to the ganglia 
# using gmetric
# Based on the original from: http://computational.engineering.or.id/LM_Sensors#Integrasi_Dengan_Ganglia
# assumes that the lines reported by lm sensors are formated like this
# Package id 0:  +27.0°C  (high = +80.0°C, crit = +100.0°C)

SENSORS=/usr/bin/sensors
GMETRIC=/usr/bin/gmetric

#sensors
let count=0
for temp in $($SENSORS | grep "id" | sort | grep -e '+.*C' | cut -f 2 -d '+' | cut -f 1 -d ' ' | sed 's/°C//'); do
    temp_name=` echo cpu${count}_temp `
    $GMETRIC -t float -n "${temp_name}" -u "Celcius" -v $temp
    let count+=1
done

Minutely runs this script is necessary, since the default information collection frequency in ganglia is 4 times per minute. Minutely runing is enough in my condition.