Diagnosing N1 Provisioning Server Problems

Almost all farm operations are carried out asynchronously, that is, a request (message) is queued for the N1 Provisioning Server, which processes them in the order received. Use the request command to view all pending and in-progress requests in the N1 Provisioning Server.

Any critical error occurring during the execution of a farm operation is reported by the Monitoring Manager through the monitoring system. Critical messages are also logged to the /var/adm/messages file on the N1 Provisioning Server. The critical error causes the current farm operation to exit and moves the farm into an error state. When the farm is in an error state, requests in the queue cannot be processed until the error is cleared manually. After the problem causing the error is resolved, you must reset the farm error state so that the stopped operation can be restarted.

In addition to the /var/adm/messages file, various debug messages are logged in the file /var/adm/tspr.debug. The amount of information in this file is determined by the debug level set in the /etc/opt/terraspring/tspr.properties file. The default debug level is 9. When a critical error is encountered, the additional information in the /var/adm/tspr.debug file is useful in determining the cause of the error.

To diagnose a problem with the N1 Provisioning Server, follow the steps illustrated in Figure 7–1.

Figure 7–1 Diagnosing N1 Provisioning Server Problems