Summary:
Apache Service doesn't start on FileCloud Server, the issue might happen due to multiple reasons; this article provides some insights on how to find the cause of a similar issue.
Question/Issue Description:
Apache service doesn't start causing FileCloud Service downtime.
Environment Details:
Product - FileCloud Server
Version - Any
Platform - OnPremise
Resolution/Workaround:
1. Check the latest entries in the Apache error logs located at below path:
Windows: C:\xampp\apache\logs\error.log
Ubuntu: /var/log/apache2/error.log
RHEL: /var/log/httpd/error.log
In windows, running the command C:\xampp\apache\bin\httpd.exe from the command line will also give details on why service is failing to start.
2. Check the Apache configuration syntax errors by running the command
Windows: C:\xampp\apache\bin\httpd.exe -t
Linux: httpd -t
If configuration syntax shows errors related to the certificate files being inaccessible, make sure the file extension is properly set. It's recommended to verify this by setting the Windows File Explorer view with "File name extensions" enabled.
3. Check if ports 80 and 443 are being used by another application.
In Windows, this can be found from Resource Monitor > Network > Listening Ports.
Or from command line by running:
netstat -ano |findstr 80
netstat -ano |findstr 443
In Linux you can run the below commands:
netstat -tunlp |grep 80
netstat -tunlp |grep 443
If other applications/services are using the port, either stop the service or change the Apache port for FileCloud. This can be changed in the configuration files; please refer to the sections "Change the default listening port" and "Change the default HTTPS port" in the documentation here.
4. Check Windows Event Viewer or Syslog or Messages logs for any system level errors
5. In Windows environments, if Apache is running with a logon account in Windows Services, please make sure the service has permission on the "xampp" folder to read/write and also verify the correct password is used or update the password if it was changed.