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

[Jan Schneider]

jan  Fri, 03 Jun 2011 08:49:47 +0000

Modified page: http://wiki.horde.org/FAQ/Admin/Troubleshoot
New Revision:  7.26
Change log:  Add some troubleshooting for problems with horde_dir or  
failed installations

@@ -25,8 +25,20 @@
  : Make sure that you are using the correct cookie domain and path  
settings in Horde's setup. : Cookies are not stored in the browser if  
you don't use a FQDN (fully qualified domain name), e.g.  
``http://localhost/horde/``, or if the specified cookie path  
({{/horde}} by default) doesn't match the webroot of your Horde  
installation, e.g. ``http://webmail.example.org/``,  
``http://www.example.org/horde-3.1.2/``. To find this, go to the Horde  
configuration page on the General tab, and the last box on that page  
says "What path should we set cookies to?". Alternatively, in  
conf.php, look for the value $conf['cookie']['path']. Set that to the  
base URL for horde.
  : If session.auto_start is set to 1 in the php.ini file the login  
page will loop. : Set it to 0.
  : Delete any cookies in your browser for Horde to test any of the  
above changes. : Otherwise wrong cookies might be stored in your  
browser and the above actions still fail
  : Check the session storage. : By default sessions are stored on the  
file system, check that your hard-disc partitions still have plenty of  
room for session storage.
+
++++ After installation I only have a js/ directory in the web root.
++++ Some !JavaScript files seem to be missing, I get a 404 error  
message in the web server log files.
++++ Some classes cannot be found, even though I installed the package  
that should contain them.
+These symptoms may be caused by two issues:
+
+# The installation failed and you didn't notice. Installing Horde  
through PEAR produces a //lot// of output, and it's too easy to miss  
the single error message that's buried in all that informational  
output. Search the output of the installation process carefully for  
any failed installations or required dependencies that cannot be  
installed.
+# The PEAR configuration setting "horde_dir" is not set correctly. If  
this configuration is not correctly set, or cannot be received from  
PEAR, then some files are not installed into the correct web root, or  
cannot be found there. This can be caused by any of:
+
+ * You didn't run the Horde_Role post-install script. One of the  
steps of installing Horde through PEAR is to install the Horde_Role  
package:  
http://www.horde.org/apps/horde/docs/INSTALL#installing-with-pear. You  
forgot to run {{pear run-scripts horde/horde_role}}.
+ * You ran the Horde_Role post-install script, but entered a wrong  
path. The path you need to enter there must be an **existing**  
directory on the **filesystem** inside the **web root** directory of  
your server (aliases and symlinks aside). If for example your web  
server's web root (http://www.example.com/) directory is {{/var/www}},  
and you want Horde to be accessed through  
http://www.example.com/groupware/, you need to create the directory  
{{/var/www/groupware}} and enter exactly that when running the  
post-install script for Horde_Role.
+ * You have a correct horde_dir set (verify by running {{pear  
config-show -c horde}}), but it's not correct received when running  
Horde. This was reported to happen with some web server setups if the  
user that is running the web server has a local PEAR configuration,  
e.g. a {{.pearrc}} in his home directory. This local configuration is  
overriding the system-wide configuration for the {{horde_dir}}. Remove  
that configuration, or use it to set {{horde_dir}} manually.

  +++ After logging in the message "Last login: Never" is displayed. Always.
  You didn't configure a permanent preference backend like SQL or  
LDAP. Preference backends are used to store user settings and personal  
stuff like the last login time. As an administrator go the the setup  
screen for Horde, select the {{Preference System}} tab, and enter the  
necessary settings. The {{PHP Sessions}} backend does //not// store  
the user settings permanently. You might also need to create some  
storage resource in the backend of your choice, e.g. a table in your  
SQL database or a scheme in your LDAP directory. But this is covered  
in the [http://www.horde.org/horde/docs/?f=INSTALL.html installation  
documentation].