Handling Stalled Requests

A request can sometimes fail to be processed by its intended server and might stay in the queue unattended. This section explains how to diagnose and solve this problem.

Check for Blocked Requests

If starting the segment manager does not process all requests on the queue, some requests might be blocked. Blocked requests require manual intervention prior to their processing. When you have reviewed the blocked requests, you can unblock them to process them or delete them. You can run the request -u request-ID command to unblock or the request -d request-ID command to delete blocked requests.

After the blocked requests are cleared, the requests in the queue are processed in the order in which they were received.

Verify That the Farm Queue Handler Is Active

Sometimes the request is not blocked but just queued, and the farm manager is still not processing the request. In this case, ping the farm. Issuing the ping command to the farm activates the farm manager queue handler to process requests. This command especially applies to requests for farms that are in an error state. Run the following command to ping the farm to activate the request queue handler:

farm -p farm-ID 

If the farm was in an error state (that is, a previous operation ended in error), reset the error to move the queue:

farm -pf farm-ID 

Managing Failed Power and Switch Operation Requests

You can look for failed power or switch operation requests by checking the tspr.debug log for ExpectTimedOut messages. Power operation requests include powerUp, ispowerUp, and powerDown operations. Switch operation requests include addPort, removeVlan, and removeAll operations.

A failure can occur if the N1 Provisioning Server is unable to access a device or the N1 Provisioning Server receives unexpected output from a device. If a failure occurs, check the following items:

1. Verify that the IP address for the device is set correctly and that communication from the N1 Provisioning Server to the device exists.

2. Run the device -lv device-ID command from the N1 Provisioning Server to verify that all login names and passwords for this device are correct.

3. Ensure that the firmware is the supported version and that any changes made to the default settings are acceptable.

If you need to debug further to resolve the issue, enable the expect log in the following properties:

• com.terraspring.drivers.util.expect.Expect.print=true

• com.terraspring.drivers.util.expect.Expect.output=log-name-path

Run the tail -f log-name-path command and reissue your request to view the operation.