HP Insight Orchestration 6.0 User Guide

Task for logical server <logical_server_id> has failed. Job <job_id> has exceeded
its timeout value of <nnn> minutes. Marking the job as failed.
Failure message
Possible cause
• Server blade firmware.
• Errors in storage presentation, multipath or zoning configuration, or failed components.
• Timeout value for create logical server request is too short
Additional possible causes if using the Insight Control deployment server.
• Insight Control server deployment has been reconfigured in a way that has modified the default PXE boot
sequence so that it no longer works with Insight Orchestration
• Issue with server deployment ProLiant Support Pack (PSP).
Review the job status on the deployment server and investigate any issues discovered there.Action
• If using the Insight Control deployment server, review the job status by:
Locate the Provisioning logical server message which identifies the server blade in use.1.
2. Use Remote desktop and log into the server deployment server.
3. Locate the server blade in the Computers pane of the server deployment console. Review the job status
in the details pane.
4. If the “in progress” icon is shown against the last task right-click and select Properties to display the
Job Schedule information.
5. If the current status is shown as Executing file: "hpsum.exe" verify that server deployment has
the latest ProLiant Support Pack in the appropriate ..\Altiris\eXpress\Deployment
Server\lib\software\ folder. Also check for any customer advisories pertaining to the drivers in
the ProLiant Support Pack. In particular see “ADVISORY: HP ProLiant iLO 2 Management Controller
Driver version 1.9.0.0 May Prevent Windows Server 2003 or Windows Server 2008 from Completing
a Shutdown or Restart Request” .
• If using Ignite-UX as the deployment server, review the status of the client by executing this command on the
Ignite/UX server:
/opt/ignite/bin/ignite client list –m xml –l status <client>
Check the Ignite-UX client’s install log in the file:
/var/opt/ignite/clients/<client>/install.log
• For HP Server Automation, review the job status:
1. Log into the HP Server Automation Client.
2. Check for “Run OS Sequence” jobs in the Jobs & Sessions section.
3. Click on the job and examine the details.
• These issues, can also indicate a possible firmware issue with the server. See “Correcting a checksum error”.
• Contact your storage administrator to ensure that your storage presentation, zoning, operating system
distribution, and drivers all support multipath SAN environments
• To set the timeout value, see “Modifying the logical server timeout value”.
• Whatever the cause, always check whether or not there are any “clean-me” logical servers. If so, perform
a manual cleanup process. See “Manual clean-up process”.
Failure message
• Could not find server with serial number <serial_number>.
• Task for logical server <logical_server_id> has failed. Logical server job
<job_id> completed with a failure status. Failure: Exception creating connection
to: 15.2.50.138; nested exception is: java.net.NoRouteToHostException: No route
to host: connect.
• Task for logical server <logical_server_id> has failed. Logical server job
<job_id> completed with a failure status. Failure: no such object in table.
A server blade that was allocated has suffered hardware or firmware problems during provisioning process,
for example insufficient power alert or power outage.
Possible cause
Action 1. Use Onboard Administrator to verify the status of the server blade.
2. Verify that the server blade has the latest firmware installed.
3. Perform a manual cleanup process for any affected logical servers. See “Manual clean-up process”.
The Manual Storage Provisioning email states that I should add more data LUNs than are required.Issue
You receive this email when adding a new server to an existing service and one or more of the following applies:Possible cause
• You added a server to a deployed server group using the Add a Server feature.
• The servers in the selected group are connected to a shared data disk.
• A manual storage provisioning action is required for the data disk.
64 Troubleshooting