Okta Access Gateway Logs Periodically Show "Systemd Reached Target Shutdown" Message

Okta Access Gateway (OAG) logs periodically display a systemd shutdown message because systemd restarts specific services based on a timer. Running a command to check the shutdown and reboot history verifies the system status.

The following log message appears periodically in the Okta Access Gateway logs:

2024-06-06T17:00:12.843-07:00 server_hostname systemd Reached target Shutdown.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Access Gateway (OAG)
• Systemd

Following are the two services Systemd restarts based on a timer that results in generation of the mentioned log message:

• systemd-tmpfiles-clean.service
  • If this option is passed, all files and directories with an age parameter configured will be cleaned up
• dnf-makecache.service 
  •  Like plain makecache, but instructs DNF to be more resource-aware, meaning it will not do anything if running on battery power and will terminate immediately if it's too soon after the last successful makecache run (see dnf.conf(5), metadata_timer_sync)

The following command can be used to check the specifics on the timer:
  

sudo systemctl list-timers
NEXT                         LEFT       LAST                         PASSED  UNIT                         ACTIVATES
Fri 2024-06-07 08:51:01 PDT  47min left n/a                          n/a     dnf-makecache.timer          dnf-makecache.service
Sat 2024-06-08 08:03:06 PDT  23h left   Fri 2024-06-07 08:03:06 PDT  42s ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

2 timers listed.

How is the system shutdown and reboot history verified?

Run the provided command to check the shutdown and reboot history and confirm the system status.

last -wx