Failed to find the task handler
Created: 13 Feb 2012 | 6 comments
We are using DS 7.1. SP1a MR1a and we are attempting to imgage an RHEL 5.4 machine.We are able to power on and off the system via a task, however when we create the job as following:
reboot to automation
create image
reboot to production
the reboot to automation immediately fails with an error which states "failed to find the task handler" Error 2111635346
We are scratching our heads on this one.
Thanks in advance
Discussion Filed Under:
Comments
No task handlers for Linux?
I don't do a lot with Linux, but it appears there are no task handlers for Linux, since you have the same error and behavior description as this thread regarding a Mac not having DS task handlers:
http://www.symantec.com/connect/forums/basics-mac-management-smp-71
The recommendation there was to script the reboot. I'd recommend the same here, to script the reboot, after which the Linux client should pick up the image task properly and then reboot to production, since both of those should be handled properly while in automation.
Does this approach work?
Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
Well I would certainly
Well I would certainly entertain writing scripts to get something out of the ordinary working. We spent roughly 70k for the full up solution and rebooting to automation is a supported task so it should work as advertised. I do appreciate the quick reply.
If I have to start writing scripts for something DS 7.1 is supposed to support then future government purchases are highly unlikely.
Derek, This could be a silly
Derek,
This could be a silly question of mine but is the Linux client has Linux DS Plug-in and Linux Automation Plug-in installed. Because in Linux production environment -
1. Linux Automation agent is needed (DS Automation Plug-in) : /boot/altiris folder
2. Deployment task handlers needed (DS Plug-in) : Check aex-helper list | grep Deploy
3. Reboot task handler call tool to switch from automation to production (autoutil)
Thanks.
not sure what to look for in
not sure what to look for in the /boot/altiris folder
I did a grep and found no Deploy. Interesting that it shows installed by the DS server.
I will try a manual install if I can find out how. Very much thanks. I think we are moving somewhere.
Speak up by submitting a case to support
I would speak up by submitting a case to support. Obviously, the majority of nodes are Windows, so the majority of functionality will go there. A bug affecting 98% of people will be fixed before a bug affecting .5% of people. That being said, submitting a case to Symantec is a good step to take. First, they will have a Linux pro (which I am not -- maybe someone else here can speak up) who can determine whether things are working properly or not. They are likely to have good workarounds for you if the product doesn't support it. And best of all, you can have a case on file so that when they look for where to invest effort, Linux will be more likely to get the attention.
Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
Ends up that there is known
Ends up that there is known bug in 7.1. sp1a MR1a. Their is 2 files the deployment client must have renamed:
Rename libcrypto.so.1.0.0 to libcrypto.so.0.9.8
Rename libssl.so.1.0.0 to libssl.so.0.9.8
Restart the client, and all is well, I can now image RHEL 5.6
Would you like to reply?
Login or Register to post your comment.