About Features Downloads Getting Started Documentation Events Support GitHub

Site Tools


development:troubleshooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
development:troubleshooting [2019/05/03 11:47]
demiankatz
development:troubleshooting [2019/05/03 11:52] (current)
demiankatz [Check the Apache Error Log]
Line 3: Line 3:
 When VuFind doesn'​t behave as expected, there are several things you can do to gain more information about what is going wrong. When VuFind doesn'​t behave as expected, there are several things you can do to gain more information about what is going wrong.
  
-===== Check the Apache ​Error Log =====+===== Check Error Logs =====
  
 If you are not seeing on-screen errors, it is possible that they are being captured by the Apache error log (often found in /​var/​log/​apache2/​error.log,​ /​var/​log/​httpd/​error.log,​ or a similar path). Checking the end of this log (or watching it with the "tail -f" command) may reveal useful information. If you are not seeing on-screen errors, it is possible that they are being captured by the Apache error log (often found in /​var/​log/​apache2/​error.log,​ /​var/​log/​httpd/​error.log,​ or a similar path). Checking the end of this log (or watching it with the "tail -f" command) may reveal useful information.
 +
 +Some operating systems use [[https://​php-fpm.org/​|PHP-FPM]] to run PHP, and the PHP-FPM error log is another place to check in this case. It is often found at /​var/​log/​php-fpm/​www-error.log (or something similar).
  
 ===== Turn on Development Mode ===== ===== Turn on Development Mode =====
development/troubleshooting.txt · Last modified: 2019/05/03 11:52 by demiankatz