Technical Notes |
|
If a Verastream Host Integrator service (such as AADS) is unable to start, you can generate atstart debug logs for troubleshooting.
In Verastream Host Integrator (VHI), the atstart command is used to start and stop services. The syntax for manually running atstart is described in Technical Note 10004.
To determine whether services are started, see Technical Note 10054.
Startup problems typically do not generate errors or warnings in Log Manager runtime logging. However, you can generate atstart debug logs to troubleshoot startup problems.
To generate atstart debug logs, insert an additional parameter as the first option on the atstart executable command line. The parameter options are as follows:
-d |
Generates limited debug output files |
-d1 |
Displays Java console output |
-d2 |
(Recommended) Generates verbose debug output files |
The following example demonstrates generating verbose debug output files when starting the AADS service.
Windows: C:\Program Files\VHI\bin\atstart.exe -d2 -start aads
UNIX/Linux: /usr/vhi/bin/atstart -d2 -start aads
Note: On Windows, debug options cannot be used with -start all. You must manually start services individually, in the order described in Technical Note 10004. Service components are logmgr, aads, server, webstation, webserver, smonitor, and hostemul.
Debugging output files atstart.debug.out and atstart.<component>.java.out are written in the <VHI>/etc directory, where:
If the files already exist, additional messages are appended with time stamps.
To troubleshoot service startup problems, examine the generated output files in a text editor or provide the files to Technical Support.