...
This will print the log to the screen. You can use this information to troubleshoot a problem yourself (depending on your level of Fedora knowledge), or to provide more detail to a technical support contact.
Apache Tomcat Logs
The location of the apache error log and what other logs (access, etc) are available will depend on your operating system, apache version, and apache settings. The error log will contain any problems that occurred while processing a request. Errors generated by PHP code that are not caught by Drupal will usually be logged here. The access log will typically contain requests made to apache and if apache denied them access.
Here are some typical locations for the log files:
Ubuntu/Apache 2:
- Error Log: /var/log/apache2/error.log
- Access Log: /var/log/apache2/access.log
CentOS/Apache 2:
- Error Log: /var/log/httpd/error_log
- Access Log: /var/log/httpd/access_log
Check these logs when:
- The page white screens, check the Apache error log first, it most likely will be a PHP syntax error.
- The watchdog didn't provide any useful information.
To customize the output of the apache logs (Set the log level, etc) follow the instructions provided here: (http://httpd.apache.org/docs/1.3/logs.html) Any changes to the configuration of Apache require that Apache be restarted.
Ubuntu:
Code Block |
---|
service apache2 restart |
CentOS:
Code Block |
---|
service https restart |
The Apache Tomcat logs may also be useful in diagnosing problems. You can access these logs by navigating to your Tomcat logs directory; for example:cd /usr/local/fedora
Code Block |
---|
cd $FEDORA_HOME/tomcat/logs |
The most relevant log file in this directory is catalina.out. As with fedora.log, you can view this file in various ways; for example:
Code Block |
---|
less catalina.out |
...
...