A Linux system administrator has found that a web server service is failing to start automatically at system boot, which necessitates a manual start each time. After booting, systemctl status of the service reports a failed state, yet no errors are recorded in the standard service logs. What is the most likely cause of this issue?
The web server service is missing a dependency on network-online.target in the unit file, causing it to start before the network stack is ready.
The primary configuration file for the service contains syntax errors that are only checked during automated starts.
There is an error with the ExecStart command that only manifests during the automated start sequence.
The server's network Time Protocol (NTP) configuration is incorrect, leading to time-related service start failures.