11 Troubleshooting #

This chapter lists common problems and possible solutions, sorted into categories.

Generating Output

Q: 1.Profiling does not work as expected?

Check the values of your profiling attributes in the XML files: They must use consistent spelling throughout a documentation project. If you assigned multiple values to a profiling attribute, check if the values are separated with a semicolon, for example, os="linux;unix".
Check the DC file for your documentation project: Does it contain one or multiple PROF* parameters? Otherwise DAPS does not know which profiling attributes to interpret. Do the PROF* parameters match the profiling attributes used in the XML files? Do the values of the PROF* parameters match the attribute values used in the XML files?
Check the MAIN file of your documentation projects: Does its header contain the following line?
```
href="urn:x-daps:xslt:profiling:docbook45-profile.xsl" type="text/xml"
```
If not, any profiling parameters in the DC file will be ignored during generation of the output.

For more details, refer to Section 3.5, “Profiling—Support for Document Variants” and http://www.sagehill.net/docbookxsl/Profiling.html.

Miscellaneous

Q: 1.Why does DAPS not talk to me?: By default DAPS only shows the result of the current subcommand. To increase the verbosity run daps with the option -v, -vv, or -vvv. For the highest verbosity, use the --debug option.

Q: 2.Where do I find the log files?

If you run into problems with DAPS that you cannot classify, check the DAPS log files in YOUR_DOC_DIR/build/BOOKNAME/log. A complete log file of the latest daps subcommand that was executed is available in YOUR_DOC_DIR/build/BOOKNAME/log/make_SUBCOMMAND.log

In case of an error the complete log file will be shown on the screen (STDOUT).

Q: 3.Are all changes to DAPS backward-compatible?

No. If you have recently updated to a higher DAPS version and afterward experience strange behavior that are difficult to debug, check your custom DAPS configuration file (~/.config/daps/dapsrc) against the system-wide configuration file (/etc/daps/config). Search for any parameters that may have changed. By default, the settings in the custom DAPS configuration file will override the settings in /etc/daps/config. Therefore any parameter incompatibilities between the files may lead to unexpected behavior of DAPS.

When switching from DAPS 1.x to DAPS 3.1, especially check the syntax of any XSLT parameters that you are using (on the command line, in scripts or in DC files). If you have not adjusted the parameters to the new syntax, this may result in strange error messages. For details, refer to Chapter 10, Configuring DAPS.

Print this page