1 of 1 people found this helpful
please try to increase 'Layer 2 Job Timeout' and 'Layer 3 Job Timeout' values on UDT Advanced Settings page instead of extending polling interval. I guess there are some jobs that always timeouts (the reason may be slow device?) and thus never finished, so this notification considers them still as 'new'. Can you please go to UDT Job Status page and check if there are any jobs with LastRun value of '1899-12-30 01:00:00' to confirm this?
UDT automatically uses the polling engine node is assigned to. So for example if you have some nodes in NPM on your additional poller and put those nodes into UDT, UDT will also use this additional poller.
I changed the time out to 20 minutes....didn't get the message again...I'll wait a couple of days to see if it's ok
I don't have jobs with this last run value so I suppose all jobs have run at least one time
thanks for both your answers !
I actually managed to get a query to find out on which Polling engine the failures are happening. And i just gave a reboot on the server and it resolved the issue.
This is the query which i had got from community:
select b.nodeid,b.engineid,c.ServerName,COUNT(*) numberOfFailures
from udt_job a,nodes b,Engines c
and b.engineid = c.engineid
and a.JobLastResult = 0
group by b.nodeid,b.engineid,c.ServerName