sudo systemctl status rvice -l -no-pager.The following systemctl commands will query systemd for the state of Apache’s processes. To troubleshoot common Apache errors using the systemd service manager, the first step is to inspect the state of the Apache processes on your system. Be sure to use the correct name for your Linux distribution. Apart from the differences between the service and running process names, starting, stopping, and checking Apache’s status, as well as logs with journalctl should work the same on any Linux system that uses systemd to manage the Apache service. Note: On Debian and Ubuntu systems, the Apache service and process name is apache2, whereas on CentOS, Fedora, and other RedHat-derived systems, Apache’s service and process name is httpd.
These commands, how to use them, and Apache’s log locations where you can find additional information about errors are described in further detail in the following sections.
Generally when you are troubleshooting Apache, you will use these commands in the order indicated here, and then examine log files for specific diagnostic data. There are three main commands, and a set of common log locations that you can use to get started troubleshooting Apache errors.
Subsequent tutorials examine specific errors in detail. The series begins with an overview of the commands and log files that you can use to troubleshoot Apache. This tutorial series explains how to troubleshoot and fix some of the most common errors that you may encounter when using the Apache web server.Įach tutorial in this series includes descriptions of common Apache configuration, network, filesystem, or permission errors.
0 kommentar(er)
