Not sure what is producing this error message: "timeout while executing a shell script" when polling system.uname and system.hostname on a heavily-loaded server. All other agent parameters respond fine with no loss of data. Cannot filter on this message in the trigger expression using, for example:

>0 &

=0

What is issuing this message - agent or server? It would seem that agent is. Are these the only agent builtin parameters that read via shell script and if so, why? I would rather not increase agent timeout unless it's the only way out.