Maybe a Work Item Thread hung due to one of the target agents hanging? Running against a large number of targets like this sometimes "discovers" agents that are not functioning correctly.
Have you looked at the Jobs and Task states under Infrastructure Management to see whats up?
No, I have not looked at Jobs and Tasks. I don't even know where Infrastructure Management is located. You see, our company just purchased this product and we had professional services here long enough to get things running and now their gone. Training? Not sure if we're going. Anyway, I'll try to look for Infrastructure Management.
Other than that - is there a way to possibly split the jobs into four seperate runs? Is BladeLogic smart enough to know where it last left off then continue it's task?
I actually found the Infrastructure Management but I don't have enough access to review anything. However, one of my co-works has enough access and they are asking what is it the should be looking for within the Infrastructure Management? We were browsing around but could not find anything that would show us the job which hangs.
I do have to point out that sometimes it works and others; well, it just hangs.
1 of 1 people found this helpful
I normally look at;
Select the app server instance under "Application Servers", the right pane should show each app server instance status (if you have MAS then check each one) and look for;
"Number of jobs currently running" - If you job is really running, the count under one of the Job App server instances should reflect the count.
"Available work item threads" - Will show how many WITs are "running" (typically there is one WIT per target server.
Once you find a Job app server instance that is busy running Jobs w/ WITs, expand that instance and select;
"Job Manager Service"
This should show the name of the running jobs, to verify if your job is running. And look at the WITs listed to see what the state of each WIT is. And you may get a clue as to what target system is hanging a particular WIT. Note, I think that a Job can be listed on one Job app instance and still have WIT's running on another Job app instance!