Do you have the full agent log showing the job run ?
Are you speaking of the log.txt file which I obtained this excert from? If so, yes, I can attach that file.
the line entry you showed below should be in the rscd.log on the target right? I want to see the whole sequence around that WARN
Okay, so I guess 7164 really means nothing because I wanted to send you some information from a few servers but every server where this job is just in "simulate" stage has a different number. Anyway, the issue is this. We created a depot/deploy job which copies three files to every server and we have an external command which kicks off the .vbs (oneof the three files copied to the servers). We deployed the job on 97 servers and only 36 servers are doing what we expected; the remaining servers are only in simulate stage.
The rscd.log has ip addresses to servers and an account so maybe I should just open up a case.?.?.
I submitted ISS03887017 if you wish to see the log file.
Kindly try this command:
set appserver RemoteServerTimeout #
# -> any time interval in minutes(default is 10 min so set it to a higher value)
I hope you will not get this error again.
Well, thanks for the suggestion but I don't think that's the issue because I can run any other job on the servers which are not doing what we expect with the file deploy job, and they run immediately. Also, I can't do this to 2,600 servers, it will take forever.
What you have did to fix the error ?. I am also getting the same error in patching job.
17/01/12 13:28:42.841 WARN rscd - SERVER01 7164 SYSTEM (???): ???: Main: Wait Timeout. Starting AgentHouseKeeping.
Yes, believe it or not, for my issue, I started over and went down a different path. Instead of a BLPackage, I created a File-Deploy job and everything worked just fine. I think what was happening, and I could be wrong and probably am, was the blpackage deploy was looking for some "termination" or "job end" and since we were running this against 2,600 servers, we may have confused the BladeLogic app server and setting a limit to run against 300 servers in parallel.
However, again, my disclaimer is that this might not be the cause.... It just worked for me.