saptune status
, so it's time to talk about it.
# saptune status
...
system state: running
...
# saptune status
...
system state: degraded
...
systemctl is-system-running
. If we check the man page of systemctl
, we find:
...
is-system-running
Checks whether the system is operational. This returns success (exit code 0) when the system is
fully up and running, specifically not in startup, shutdown or maintenance mode, and with no
failed services.
...
degraded The system is operational but one or more units failed.
...
...
saptune_check
or systemctl list-units --state=failed
:
# saptune_check
...
[WARN] System is in status "degraded". Failed services are: saptune.service -> Check the cause and reset the state with systemctl reset-failed
!
...
# systemctl list-units --state=failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● saptune.service loaded failed failed Optimise system for running SAP workloads
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
saptune.service
failed for some reason and caused the degraded state.
# systemctl status saptune.service
● saptune.service - Optimise system for running SAP workloads
Loaded: loaded (/usr/lib/systemd/system/saptune.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2022-08-11 14:52:20 CEST; 12min ago
Process: 2048 ExecStart=/usr/sbin/saptune service apply (code=exited, status=1/FAILURE)
Main PID: 2048 (code=exited, status=1/FAILURE)
Aug 11 14:52:20 sles4sap15sp3 systemd[1]: Starting Optimise system for running SAP workloads...
Aug 11 14:52:20 sles4sap15sp3 saptune[2048]: ERROR: found an active sapconf, so refuse any action
Aug 11 14:52:20 sles4sap15sp3 systemd[1]: saptune.service: Main process exited, code=exited, status=1/FAILURE
Aug 11 14:52:20 sles4sap15sp3 systemd[1]: saptune.service: Failed with result 'exit-code'.
Aug 11 14:52:20 sles4sap15sp3 systemd[1]: Failed to start Optimise system for running SAP workloads.
saptune
refused to start, because sapconf
has already tuned the system!saptune status
and saptune_check
report issues with systemd's system state.sapconf.service
or saptune.service
are the once listed as failed, but other units.saptune status
found issues, which have most likely nothing to do with saptune
itself and most times not even will prevent saptune
from doing its job.saptune
will work, why reporting it and raise concerns?sapconf.service
or saptune.service
are involved, most certainly your tuning for SAP workload is fine. Best check it out with saptune note verify
to be on the safe side.systemd system status
and add a few explanatory lines to the output, so that it s more obvious what is going on and what to do next.You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |