Scheduled Task Did Not Run: Checking the systemd Timer
How to link a timer to the service it launches, verify past and next executions, and avoid mistaking an active timer for a successful task.
Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в панели.
Practical tips and verified solutions for Linux, servers and websites.
How to link a timer to the service it launches, verify past and next executions, and avoid mistaking an active timer for a successful task.
Filter messages by service, boot, and time to analyze a specific failure without dumping the entire journal and losing critical lines.
How to read the systemd service state, distinguish process startup from application readiness, and gather facts before changing the server state.
We explain Linux load average: why it cannot be read as CPU percentages and how to correlate it with the number of processors and resource wait times.
We analyze the situation where Linux reports no space despite free disk capacity: how to check inodes and find directories with a high number of files.
How to identify the filesystem running out of space and compare its metrics with directory sizes without blindly deleting data.
Check the user, schedule, and Cron environment without manually re-running a potentially dangerous task or modifying crontab.
How to link a site path to a mount point and block device without confusing disk size, partition, and file system.
First look at the query plan: selected indexes, row estimates, and access order. We explain why EXPLAIN ANALYZE requires a separate solution.
Compare current connections, active threads, and the server limit to identify the cause of failures before increasing the connection limit.
Examining CLI and PHP-FPM: How to Check the Command-Line Environment and Understand Why Its Settings Do Not Guarantee Web Request Configuration
How to determine the version and build parameters, verify the configuration, and distinguish between a successful file check and the actual application of settings.
Page 2 of 3