Quantcast
Channel: Alltop RSS feed for enterprise.alltop.com
Viewing all articles
Browse latest Browse all 58520

Wake on lan task - Waiting for the agent to get the task

$
0
0
I need a solution

Hello,

I'm troubleshooting the wake-on-lan options with Altiris NS 7.1.

 

The strange this is that when I do a clean manual shutdown the wake-on-lan feature seems to be working most of the time. (not always... :s)

However, sometimes the jobs gets stuck with status "Waiting for the agent to get the task"

This happens when I hibernate/standby the machine, or even sometimes when I use the Shut down task of Altiris itself...

Information I found in logs

 

"24/10/2012 10:58:39","Starting Task Instance Re-Quick run on FHN4266Q2 (e34d1402-5d8c-4cb1-b421-5b1027832fcb) from Task Power Control - Wake up (ff55394a-b404-4bcc-8207-5fccd8140fc6)","Altiris.TaskManagement.ClientTask.*","AtrsHost","142"
24/10/2012 10:58:39 Task instance Re-Quick run on FHN4266Q2 (24/10/2012 10:58:39) is being put to sleep until 24/10/2012 11:03:39. Instance GUID: e34d1402-5d8c-4cb1-b421-5b1027832fcb Altiris.TaskManagement.ServerTasks.ServerTaskExecutionInstance.Sleep AtrsHost 121
24/10/2012 11:03:45 Resuming task instance Power Control - Wake up (24/10/2012 10:58:39)(e34d1402-5d8c-4cb1-b421-5b1027832fcb) Altiris.TaskManagement.ClientTask.* AtrsHost 1541
"24/10/2012 11:03:45","BaseClientTask.CheckIsTaskComplete(): Task ""Power Control - Wake up"" (24/10/2012 10:58:39) - 0 / 1 child instances done.  Timeout at 24/10/2012 11:20:39.  Will complete at 24/10/2012 11:13:39 if 95% of child instances are complete.","Altiris.TaskManagement.ClientTask.BaseClientTask.CheckIsTaskComplete","AtrsHost","1541"
"24/10/2012 11:03:45","Task instance Re-Quick run on FHN4266Q2 (24/10/2012 10:58:39) is being put to sleep until 24/10/2012 11:08:45. Instance GUID: e34d1402-5d8c-4cb1-b421-5b1027832fcb","Altiris.TaskManagement.ServerTasks.ServerTaskExecutionInstance.Sleep","AtrsHost","121"
 
and this repeats untill it eventually times out.
 
Or If manually start the machine and check the TASK history I see that as soons as it contacts the TASK server it puts it on succesfull.
So it seems that sometimes it wants to contact the client first before doing a wakeup...
 
Does anyone have an idea why this happens?
 
 
Tom
 

 


Viewing all articles
Browse latest Browse all 58520

Trending Articles