[cvs] [Wiki] changed: FAQ/Admin/Troubleshoot

[Jan Schneider]

jan  Wed, 04 Oct 2006 14:17:24 -0700

Modified page: http://wiki.horde.org/FAQ/Admin/Troubleshoot
New Revision:  6.16
Change log:  More words on Horde's log

@@ -15,9 +15,11 @@
  
  In order to get an idea of what really happened, take a look in the web server's error log, in which more verbose errors should be found, at least if you properly configured [http://de2.php.net/manual/en/ref.errorfunc.php error logging in your PHP setup].
  
  Possible reasons could be a fatal PHP error, not being displayed to the browser (which is a good thing on production systems, but bad if you are trying to hunt down a problem)[http://www.php.net/manual/en/ref.errorfunc.php#ini.display-errors], or a segfaulting server process (happens most times in the [http://www.php.net/manual/en/ref.imap.php c-client library] while using IMP). If you correctly configured your web server and PHP to log all errors, you should find more information in your web server's or PHP's log files, or whereever you log the errors (syslog etc.).
-Another place to see is /tmp/horde.log
+
+Another place to see is the Horde log which is being configured in Horde's setup. By default Horde is logging to the file /tmp/horde.log.
+
  +++ "Failed opening test.php for inclusion"
  The set_perms.sh script and some packaged distributions change the permissions on the {{test.php}} script so that it can't be run. This increases the security of your web server by not revealing to intruders information about how PHP is compiled/configured or what Horde applications are installed. To use the script while setting up Horde, add read permission for your web server to the script:
  
  <code>