Nobody to help me, please !
This looks like the agent is able to communicate with the server, but the server is unable to send wakeup calls to the agent. Check that you have the "enable agent wakeup call support" option enabled in the Genarl policy, and that nothing is blocking the wakeup call port (8081 by default) between the server and the client machine. Check the local firewall settings.
it says the wakeup feature is turned off in the policy. First step I'd take is to check the policy that is applicable for one such agent if it is really turned off.
The agent - upon installation - makes firewall settings to enable traffic so I would not assume those settings were removed or disabled, etc.
In addiiton, in a concerted effort you could check the agent log in parallel, what it says (set LogLevel to 8 beforehand on the agent ) when the wakeup request is sent down.
from the attached server.log picture I saw that no corresponding "Wake up agent on DNS name.." entries appears for the "Server failed to wake up.." lines. This could mean that the corresponding entries are scrolled out but as another possibility I suppose the wake-up occurs on quantities and the server just lists those clients for which the wake-up have failed.
If this problem still persists, could you pick several clients where wake-up failed and see if the - default or the corresponding - client policy has been /could have been enforced at all on them? (i.e. the wake-up feature has been enabled on them)?
Thanks for the replies,
I did not understand how but the problem has been fixed.I did not change (or disable or remove) any of the settings, I think maybe the matter was about the traffic or the server was busy (?), I am not sure.
But now the wake up task is succesfully completed.