update for rename of Apoc/Documentation/TroubleShooting.mdwn to Documentation/TroubleShooting.mdwn

1 files changed, 27 insertions, 27 deletions

diff --git a/Documentation/TroubleShooting.mdwn b/Documentation/TroubleShooting.mdwn
index d3c7b4a..8730303 100644
--- a/Documentation/TroubleShooting.mdwn
+++ b/Documentation/TroubleShooting.mdwn
@@ -20,31 +20,31 @@ This page describes commonly encountered problems using the Configuration Manage
 
 * Symptom: you've pointed your browser to the appropriate URL, i.e `https://<your.server>:6789`, but it tells you the connection is refused. 
 * Possible causes: 
-   * the Web Console is [[not running|Apoc/Documentation/TroubleShooting]] on the server. 
+   * the Web Console is [[not running|Documentation/TroubleShooting]] on the server. 
 
 ### Cannot Login
 
 * Symptom: you've reached the login page of the Web Console, but the user/password combination is rejected. 
 * Possible causes: 
-   * the LDAP server is [[not running|Apoc/Documentation/TroubleShooting]]. 
-   * the Web Console LDAP authentication module is [[misconfigured|Apoc/Documentation/TroubleShooting]]. 
-   * the user [[doesn't exist|Apoc/Documentation/TroubleShooting]] in the LDAP server. 
-   * the user has a [[different password|Apoc/Documentation/TroubleShooting]] in the LDAP server. 
+   * the LDAP server is [[not running|Documentation/TroubleShooting]]. 
+   * the Web Console LDAP authentication module is [[misconfigured|Documentation/TroubleShooting]]. 
+   * the user [[doesn't exist|Documentation/TroubleShooting]] in the LDAP server. 
+   * the user has a [[different password|Documentation/TroubleShooting]] in the LDAP server. 
 
 ### No Configuration Manager Link
 
 * Symptom: you've logged in the Web Console, but the application list page doesn't display the APOC Manager. 
 * Possible causes: 
-   * the APOC Manager module is [[not installed|Apoc/Documentation/TroubleShooting]]. 
-   * the user [[doesn't exist|Apoc/Documentation/TroubleShooting]] in the LDAP server but does exist in the users map on the machine. 
+   * the APOC Manager module is [[not installed|Documentation/TroubleShooting]]. 
+   * the user [[doesn't exist|Documentation/TroubleShooting]] in the LDAP server but does exist in the users map on the machine. 
 
 ### Null Pointer Exception, Tomcat/Java Error or Blank Page
 
 * Symptom: you've entered the APOC Manager but nothing of value is displayed, just a blank page or some errors. 
 * Possible causes: 
-   * if the error mentions `NoClassDefFoundError: sun/tools/javac/Main`, the Web Console uses the [[wrong Java|Apoc/Documentation/TroubleShooting]]. 
-   * the APOC Manager module is [[misconfigured|Apoc/Documentation/TroubleShooting]]. 
-   * the LDAP server has been [[incorrectly prepared|Apoc/Documentation/TroubleShooting]]. 
+   * if the error mentions `NoClassDefFoundError: sun/tools/javac/Main`, the Web Console uses the [[wrong Java|Documentation/TroubleShooting]]. 
+   * the APOC Manager module is [[misconfigured|Documentation/TroubleShooting]]. 
+   * the LDAP server has been [[incorrectly prepared|Documentation/TroubleShooting]]. 
 
 ## Desktop Issues
 
@@ -53,16 +53,16 @@ This page describes commonly encountered problems using the Configuration Manage
 
 * Symptom: no matter which setting is valued using the APOC Manager, no matter for which application (Gnome, Mozilla, [[StarOffice|StarOffice]], Evolution), the central values are not visible on the desktop. 
 * Possible causes: 
-   * the APOC Agent is [[not enabled|Apoc/Documentation/TroubleShooting]]. 
-   * the LDAP server is [[not running|Apoc/Documentation/TroubleShooting]]. 
-   * the LDAP server has been [[incorrectly prepared|Apoc/Documentation/TroubleShooting]]. 
-   * the current user [[doesn't exist|Apoc/Documentation/TroubleShooting]] in the LDAP server. 
+   * the APOC Agent is [[not enabled|Documentation/TroubleShooting]]. 
+   * the LDAP server is [[not running|Documentation/TroubleShooting]]. 
+   * the LDAP server has been [[incorrectly prepared|Documentation/TroubleShooting]]. 
+   * the current user [[doesn't exist|Documentation/TroubleShooting]] in the LDAP server. 
 
 ### Cannot See Any Gnome or Evolution Settings
 
 * Symptom: [[StarOffice|StarOffice]] and Mozilla work fine, but the central settings for Gnome applications, including Evolution are not taken into account. 
 * Possible causes: 
-   * the GConf adapter is [[not installed or not setup properly|Apoc/Documentation/TroubleShooting]]. 
+   * the GConf adapter is [[not installed or not setup properly|Documentation/TroubleShooting]]. 
 
 ### Cannot See Any Mozilla Settings
 
@@ -74,20 +74,20 @@ This page describes commonly encountered problems using the Configuration Manage
 
 * Symptom: some settings set using the APOC Manager are not taken into account, while others for the same application are fine. 
 * Possible causes: 
-   * a [[local user preference|Apoc/Documentation/TroubleShooting]] has been defined for that setting. 
+   * a [[local user preference|Documentation/TroubleShooting]] has been defined for that setting. 
 
 ### Settings Are Not Refreshed
 
 * Symptom: the value of a setting has been changed using the APOC Manager and the new value is not propagated to the desktop application. 
 * Possible causes: 
-   * a [[local user preference|Apoc/Documentation/TroubleShooting]] with the same value as the old value has been defined for that setting. 
-   * the APOC Agent [[change detection cycle|Apoc/Documentation/TroubleShooting]] has not yet taken place. 
+   * a [[local user preference|Documentation/TroubleShooting]] with the same value as the old value has been defined for that setting. 
+   * the APOC Agent [[change detection cycle|Documentation/TroubleShooting]] has not yet taken place. 
 
 ### Staroffice And Mozilla Crash On Linux Sun Ray
 
 * Symptom: [[StarOffice|StarOffice]] crashes ( crash reporter displayed ) and Mozilla crashes ( appears not to start ). Look for **ordinal="<ins>os_exists+0x50"** near the top of the [[StarOffice|StarOffice]] crash reporter stack. 
 * Possible causes: 
-   * incompatibility between [[/usr/lib/libc_ut.so|Apoc/Documentation/TroubleShooting]] ( provided by Sun Ray to address audio problems with Sun Ray devices ) and BerkeleyDB used by apoc. 
+   * incompatibility between [[/usr/lib/libc_ut.so|Documentation/TroubleShooting]] ( provided by Sun Ray to address audio problems with Sun Ray devices ) and BerkeleyDB used by apoc. 
 
 ## Tests & Solutions
 
@@ -108,7 +108,7 @@ To ensure that the LDAP server has been properly setup, perform the following co
 
     ldapsearch [-x] -h <host> -p <port> -b ou=apocregistry,ou=default,ou=organizationconfig,ou=1.0,ou=apocservice,ou=services<base> ou=apocregistry sunkeyvalue`
 
-where <host>, <port>, and <base> match the values found in either the [[APOC Manager configuration|Apoc/Documentation/TroubleShooting]] or the [[APOC Agent configuration|Apoc/Documentation/TroubleShooting]]. The result of this search should be one entry with unreadable attributes (base 64 encoded values). The `-x` flag may be required or not depending on the version of `ldapsearch` used, try with it and remove it if a usage message is displayed. If no entry is found, that particular <base> on that particular <host> has not been prepared for use with APOC. 
+where <host>, <port>, and <base> match the values found in either the [[APOC Manager configuration|Documentation/TroubleShooting]] or the [[APOC Agent configuration|Documentation/TroubleShooting]]. The result of this search should be one entry with unreadable attributes (base 64 encoded values). The `-x` flag may be required or not depending on the version of `ldapsearch` used, try with it and remove it if a usage message is displayed. If no entry is found, that particular <base> on that particular <host> has not been prepared for use with APOC. 
 
 Follow the instructions in the installation guide to run the deployment tool and prepare the LDAP server, please note that if the LDAP server uses non-standard attributes or object classes for its organisations, roles or users, or if users are not stored in `ou=People` containers, the file named [[OrganisationMapping|OrganisationMapping]] needs to be modified to reflect these differences *prior* to running the `deployApoc` or `createServiceTree` scripts. 
 
@@ -119,14 +119,14 @@ To check whether a given user identified by its <username> exists in the LDAP se
 
 `ldapsearch [-x] -h <host> -p <port> -b <base> <attribute>=<username> dn` 
 
-where <host>, <port>, and <base> match the values found in either the [[APOC Manager configuration|Apoc/Documentation/TroubleShooting]] or the [[APOC Agent configuration|Apoc/Documentation/TroubleShooting]], and <attribute> is the unique identifier attribute specified during the [[Web Console configuration|Apoc/Documentation/TroubleShooting]] or found in the [[organisational mapping file|Apoc/Documentation/TroubleShooting]]. The `-x` flag may be required or not depending on the version of `ldapsearch` used, try with it and remove it if a usage message is displayed. 
+where <host>, <port>, and <base> match the values found in either the [[APOC Manager configuration|Documentation/TroubleShooting]] or the [[APOC Agent configuration|Documentation/TroubleShooting]], and <attribute> is the unique identifier attribute specified during the [[Web Console configuration|Documentation/TroubleShooting]] or found in the [[organisational mapping file|Documentation/TroubleShooting]]. The `-x` flag may be required or not depending on the version of `ldapsearch` used, try with it and remove it if a usage message is displayed. 
 
-If the above command returns `Cannot connect`, the LDAP server is [[not running|Apoc/Documentation/TroubleShooting]]. If it returns no entries, the user doesn't exist in the server or the attribute used is wrong. Add the user to the server and/or verify the [[APOC Manager configuration|Apoc/Documentation/TroubleShooting]] and the [[organisational mapping file|Apoc/Documentation/TroubleShooting]]. If it returns multiple entries, this means the attribute used doesn't uniquely identify a user in the LDAP server and this must be changed, either by using a different attribute or by modifying one of the duplicate entries. 
+If the above command returns `Cannot connect`, the LDAP server is [[not running|Documentation/TroubleShooting]]. If it returns no entries, the user doesn't exist in the server or the attribute used is wrong. Add the user to the server and/or verify the [[APOC Manager configuration|Documentation/TroubleShooting]] and the [[organisational mapping file|Documentation/TroubleShooting]]. If it returns multiple entries, this means the attribute used doesn't uniquely identify a user in the LDAP server and this must be changed, either by using a different attribute or by modifying one of the duplicate entries. 
 
 <a name="TestPassword"></a> 
 #### Testing a User Password in LDAP
 
-To check that a user/password combination is valid for use with the APOC Manager, first run the command used to [[find that user|Apoc/Documentation/TroubleShooting]]. The result of that command will contain a line formatted like `dn: uid=username,<blablabla>,<base>`. The string after `dn:` is the full DN of the user. Then perform the same search, but this time authenticated as that user, by adding before the `-h` flag in the command the string `-D "<full DN>" -w <password>`. If the command returns `Invalid credentials`, the user/password combination is invalid. The best course of action is then to reset the password to a known value using an LDAP administrative tool. 
+To check that a user/password combination is valid for use with the APOC Manager, first run the command used to [[find that user|Documentation/TroubleShooting]]. The result of that command will contain a line formatted like `dn: uid=username,<blablabla>,<base>`. The string after `dn:` is the full DN of the user. Then perform the same search, but this time authenticated as that user, by adding before the `-h` flag in the command the string `-D "<full DN>" -w <password>`. If the command returns `Invalid credentials`, the user/password combination is invalid. The best course of action is then to reset the password to a known value using an LDAP administrative tool. 
 
 
 ### Web Console
@@ -161,7 +161,7 @@ To check if the APOC Manager is installed in the Web Console, run `smreg list -a
 <a name="ConfigureAPOCMgr"></a> 
 #### Configuring the APOC Manager
 
-To check if the APOC Manager is pointing to the proper LDAP server, check the contents of the file named `policymgr.cfg` located in  `/usr/share/webconsole/apoc/WEB-INF`. That file should contain the host name, port number and base DN of the LDAP repository. If the data in that file is not correct, use the `configure` script as described in the second half of the section on [[configuring the Web Console|Apoc/Documentation/TroubleShooting]] to provide the proper values. Checking the values are correct can be done by trying to [[find a user|Apoc/Documentation/TroubleShooting]] in the directory using these parameters. 
+To check if the APOC Manager is pointing to the proper LDAP server, check the contents of the file named `policymgr.cfg` located in  `/usr/share/webconsole/apoc/WEB-INF`. That file should contain the host name, port number and base DN of the LDAP repository. If the data in that file is not correct, use the `configure` script as described in the second half of the section on [[configuring the Web Console|Documentation/TroubleShooting]] to provide the proper values. Checking the values are correct can be done by trying to [[find a user|Documentation/TroubleShooting]] in the directory using these parameters. 
 
 <a name="DebugAPOCMgr"></a> 
 #### Enabling Debug Log Level for the APOC Manager
@@ -191,7 +191,7 @@ To enable the APOC Agent you need to configure the policymgr.properties, file lo
 
 The configuration of the APOC agent is done running the `apoc-config` tool.  
 
-It is important that the details of the LDAP server, specifically the host name, port number and base DN accurately allow the agent to communicate with the server. One good way of ensuring this is by using the values in these tools to [[find a user|Apoc/Documentation/TroubleShooting]] in the LDAP repository. 
+It is important that the details of the LDAP server, specifically the host name, port number and base DN accurately allow the agent to communicate with the server. One good way of ensuring this is by using the values in these tools to [[find a user|Documentation/TroubleShooting]] in the LDAP repository. 
 
 <a name="DebugAPOCAgent"></a> 
 #### Enabling Debug Log Level for the APOC Agent
@@ -201,7 +201,7 @@ To get the APOC agent to generate as many traces as possible to facilitate the i
 <a name="ChangeDetection"></a> 
 #### Managing Change Detection in the APOC Agent
 
-By default, the APOC agent checks for changes to the configuration of currently logged in users every hour. It can be forced to perform a change detection by running `/usr/lib/apoc/apocd change-detect`. To modify the change detection frequency use the [[agent configuration tool|Apoc/Documentation/TroubleShooting]]. Another way is to edit the file `apocd.properties`, located in `/etc/apoc` and, if a line containing `ChangeDetectionInterval` (**not** `DaemonChangeDetectionInterval`) exists, replace it with the string `ChangeDetectionInterval=<period>`, where `<period>` is the number of minutes between detection cycles, or if no such line exists, just add the string at the end of the file. Force the agent to reload its configuration by running the command `/usr/lib/apoc/apocd reload`. 
+By default, the APOC agent checks for changes to the configuration of currently logged in users every hour. It can be forced to perform a change detection by running `/usr/lib/apoc/apocd change-detect`. To modify the change detection frequency use the [[agent configuration tool|Documentation/TroubleShooting]]. Another way is to edit the file `apocd.properties`, located in `/etc/apoc` and, if a line containing `ChangeDetectionInterval` (**not** `DaemonChangeDetectionInterval`) exists, replace it with the string `ChangeDetectionInterval=<period>`, where `<period>` is the number of minutes between detection cycles, or if no such line exists, just add the string at the end of the file. Force the agent to reload its configuration by running the command `/usr/lib/apoc/apocd reload`. 
 
 
 ### GConf Daemon
@@ -226,7 +226,7 @@ We are currently working with the Sun Ray team to figure out exactly why this in
 
 ## When All Else Fails
 
-If the problem doesn't fit one of the above issues, or the tests and solutions offered failed to remedy it, contact [[the mailing list|http://lists.freedesktop.org/mailman/listinfo/apoc]], providing a description of the problem and if possible root access to the machine affected by the problem (either the Web Console machine or a desktop one). If providing a root access is not possible, enable debug information on the appropriate machine (the [[Web Console|Apoc/Documentation/TroubleShooting]] or the [[desktop|Apoc/Documentation/TroubleShooting]]), recreate the problem and depending on the nature of the problem, gather and make available (by attaching to the mail or otherwise) the following information: 
+If the problem doesn't fit one of the above issues, or the tests and solutions offered failed to remedy it, contact [[the mailing list|http://lists.freedesktop.org/mailman/listinfo/apoc]], providing a description of the problem and if possible root access to the machine affected by the problem (either the Web Console machine or a desktop one). If providing a root access is not possible, enable debug information on the appropriate machine (the [[Web Console|Documentation/TroubleShooting]] or the [[desktop|Documentation/TroubleShooting]]), recreate the problem and depending on the nature of the problem, gather and make available (by attaching to the mail or otherwise) the following information: 
 
 * if everything seems to be started and running, but no access to the LDAP server, i.e login or data retrieval, can be achieved, get from the LDAP server: 
    * a copy of the log files located on a Sun Directory Server in `/var/Sun/mps/slapd-<instance>/logs` and named `access` and `errors`, making sure that the logs cover the time at which the problem occurred (these log files are rotated when they reach a certain size, the old files are named with timestamps indicated the period they cover).