| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| development:troubleshooting [2020/02/19 14:57] – [Debug on the Fly] demiankatz | development:troubleshooting [2022/10/07 14:31] – demiankatz |
|---|
| |
| 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. |
| | |
| | If you cannot find your Apache error logs, you should check whether any <VirtualHost> definitions in your Apache configuration are sending logs to a non-standard location using the ErrorLog directive. |
| |
| 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). | 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). |
| |
| If Apache is not allowed to read or write certain directories (particularly the cache), VuFind may have problems. The $VUFIND_LOCAL_DIR/cache directory (and all of its subdirectories except "cli") should be writable by the user running Apache (often named www-data or apache, depending on your operating system). The $VUFIND_LOCAL_DIR/cache/cli directory (and all of its subdirectories) should be writable by the user running command-line utilities. Also make sure that SELinux is not interfering with VuFind's operations; see the [[installation:fedora|Fedora Installation Instructions]] for more details on SELinux. | If Apache is not allowed to read or write certain directories (particularly the cache), VuFind may have problems. The $VUFIND_LOCAL_DIR/cache directory (and all of its subdirectories except "cli") should be writable by the user running Apache (often named www-data or apache, depending on your operating system). The $VUFIND_LOCAL_DIR/cache/cli directory (and all of its subdirectories) should be writable by the user running command-line utilities. Also make sure that SELinux is not interfering with VuFind's operations; see the [[installation:fedora|Fedora Installation Instructions]] for more details on SELinux. |
| | |
| | If you are not sure which user is allowed to write to the cache, try running "chmod -R 777 $VUFIND_LOCAL_DIR/cache" to make the cache world-writable. After accessing VuFind, you can then "ls -l $VUFIND_LOCAL_DIR/cache/" and see which user owns the files. You can then run: "sudo rm -rf $VUFIND_LOCAL_DIR/cache/* ; sudo chmod 775 $VUFIND_LOCAL_DIR/cache ; chown user:user $VUFIND_LOCAL_DIR/cache" (replacing user:user with the appropriate user/group) to make your cache settings secure again. |
| |
| ===== Turn on Debug Mode ===== | ===== Turn on Debug Mode ===== |
| See the [[configuration:ils:troubleshooting|ILS Driver Troubleshooting]] page for some more details on using the console (as well as tips on resolving problems specifically related to communication between VuFind and your Integrated Library System). | See the [[configuration:ils:troubleshooting|ILS Driver Troubleshooting]] page for some more details on using the console (as well as tips on resolving problems specifically related to communication between VuFind and your Integrated Library System). |
| ---- struct data ---- | ---- struct data ---- |
| | properties.Page Owner : |
| ---- | ---- |
| |
