This appendix lists possible causes and solutions for some problems that you may encounter when administering a DynaWeb server. The sections in this appendix are
You cannot find a DynaWeb directory using the pathname specified in a DynaWeb guide.
A directory pathname without a leading slash indicates that the path is relative to the DynaWeb home (root) directory.
Clients are unexpectedly accessing directories outside of the DynaWeb root directory tree.
Ensure that symbolic links exist only where expected. Web clients can navigate downwards within a linked directory. Moreover, if a linked directory is, itself, linked to another directory, Web clients can jump to and move downwards from there.
Collections are not restricted to being relative to root. If the definition of DWEB_COLLECTIONS parameter contains a full pathname, clients may gain access to files below that pathname or to symbolically linked directories.
The server does not display your site-specific home page.
The filename of the home page is set by the DWEB_HOMEPAGE configuration parameter. To use a different filename for the home page, you must assign your own filename as the value of DWEB_HOMEPAGE.
The hypertext link to your collections fails to bring up your collection list.
Ensure that the XREF value in the link matches the value of the DWEB_COLLECTMAGIC configuration parameter.
The server cannot find your home page after you change its name in the server configuration file.
Verify the file and pathname of the file.
The values of resource parameters must contain a leading slash (for example, /docs/my-homepage.html). This slash is necessary, because the server appends the value of file parameters to the value of DWEB_ROOTDIR to produce the full directory path.
A client can't access the DynaWeb server.
Possible causes for this problem are:
The server is not responding.
There is an error in the configuration file /usr/lib/Insight/dweb/data/config/dynaweb.cfg.tmpl.
The file /usr/lib/Insight/dweb/data/config/dynaweb.cfg (created by the command /etc/init.d/dynaweb start) doesn't exist.
A button does not appear on the button bar.
Check the server configuration file to ensure that the button assignment is not disabled (by the insertion of a # at the start of the line). Ensure that the icon file is present in the servroot/icons directory and uses the same name as defined in the server configuration file.
Note: An unavailable icon causes no problem for the server. A client displays a browser-specific icon, instead of the correct server icon.
If the .gif file of an icon is corrupt, the server displays some generic client icon, but the button operates as usual.
The server cannot find an icon after you change its name in the configuration file.
The values of resource parameters must contain a leading slash (for example, /icons/button_up.gif). This slash is necessary, because the server appends the value of file parameters to the value of DWEB_ROOTDIR, to produce full directory paths; for example, if DWEB_ROOTDIR equals /usr/pro/dynaweb/servroot, the full pathname of the unknown-button file is /usr/pro/dynaweb/servroot/icons/button_up.gif.
Users cannot find the button bar.
If the button bar is at the bottom, and the returned information is longer than the document view, users must move downwards before the button bar appears. In the middle of a block of text, the button bar is out of view (at either the top or bottom of the text).
A bookshelf is missing or a removed bookshelf or book still appears.
When a new bookshelf is added (by performing the first installation of an InSight book that appears on that bookshelf), the DynaWeb server must be restarted (see the section “Running DynaWeb” in Chapter 2).
A user complains that the server is acting weirdly.
Verify whether the user is specifying either of the following parameters in URLs: DWEB_NAVHINTS or DWEB_REDIRECT. The server uses these parameters to pass state information to itself. Setting them in a URL causes the server to behave in unpredictable ways.
After you supply your ID and password and they have been validated by the server, when you switch books, collections, or other documents, you are again prompted for your information.
Make sure all URLs match the DWEB_HOST parameter. Otherwise the server thinks you are not authenticated and tries to validate you again. This will happen every time you link to a URL that contains a different hostname. For example, mycomputer:88 does not match mycomputer.mycompany.com:88.