If you don’t have permissions to bind Apache to some port, you’ll see this error: (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:port_number To bind Apache to privileged ports, start Apache as root. In case another process is using that port, use another port or stop that process.Ĭheck if you have permissions to bind Apache to the requested port. Look for the pid in the second column and you’ll get more information about that process. You can then use: $ ps aux | grep process_name In the last column you’ll see the process id or process name. Replace the PORT placeholder with the correct port number, such as 80 or 443. To see which process is already using that port you can run the following from a command prompt. No listening sockets available, shutting down If another process is using that address you’ll get: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:port_number If no error is found, you will see a message similar to: Syntax OKĬheck the Apache error log file on each node at /opt/bitnami/apache/logs/error_log for information about why the error occurred.Ĭheck if another process is listening to that port This is the first place to look when you run into a problem when using Apache.
This file includes error messages, startup messages, and any other significant events in the life cycle of the server. The error_log file is used to record important events. When a client requests a document from the server, Apache records several parameters associated with the request in this file, such as: the IP address of the client, the document requested, the HTTP status code, and the current time. The access_log file is used to track client requests. Once Apache starts, it will create two log files at /opt/bitnami/apache/logs/access_log and /opt/bitnami/apache/logs/error_log respectively.
0 kommentar(er)
