Issue with maintenance window and actions

(imported topic written by SystemAdmin)

Hi All,

I am sure this is something I have overlooked but I just cannot seem to figure out what is going on.

Here is what I have done:

  1. set up a maint window for a group of servers (3 servers). This window is for 17:00-18:00 on Sunday

  2. used the Enforce Maintenance Window with Client Locking and confirmed that they are locked

  3. Set up an action to deploy a baseline to the computer group. This was set up on Friday and set to expire today

When I submitted the action, I saw that eventually it said that the targets were locked (as expected) so everything looked good. When I came in today, the target status for all servers still said locked and, according to the logs, no actions were taken on the targets. I checked out one system and I can see the lock being removed as it should have, but there was nothing done.

I am thinking that I missed something when I submitted the action, but cannot seem to figure out what I missed.

Thoughts?

Martin Carnegie

Gulf Breeze Software Partners

http://www.gulfsoft.com

(imported comment written by BenKus)

Hmmm… Seemed like you did it right…

Did you maybe have really big downloads for the action?

Ben

(imported comment written by SystemAdmin)

There were 4 of them that ranged from about 100KB to 25MB and I did not see anything come down. I had previously deployed one of them, so it should have at least been on the TEM server.

This was a rather large baseline with 142 components, but I did not even see anything about an evaluation so not sure what happened. Could you think of anything that would cause it not to be evaluated in a 1 hour period?

I did this for one server with only one fixlet and that seemed to work no problem.

Thanks

Martin Carnegie

Gulf Breeze Software Partners

http://www.gulfsoft.com

(imported comment written by SystemAdmin)

With the “Enforce Maintenance window with Client Locking” fixlet, does this have to be run from the BES Support site?

The reason I ask is that I made a custom copy of it to my site with my baselines and took an action on it. The status for the target changed to Locked (the client was already locked) and it appears that the action never occurred. I then tried using the fixlet in the BES Support site and the action was completed. Is there something in the BES Support site that gets around this locked state?

Thanks

Martin Carnegie

Gulf Breeze Software Partners

http://www.gulfsoft.com

(imported comment written by mcalvi91)

would assume so since it needs something to trigger the unlock. The bessupport site is (at least was at one time) exempt from client locking.

(imported comment written by SystemAdmin)

Hmm, that stinks :slight_smile:

I was trying to modify the action so that it would execute a custom script to send a notice to the monitoring environment when it started and when it stopped.

I thought about doing it in the baseline, but I was not sure if this was the best as there may be multiple baselines that need to be processed. Seems to me that the enforce area would have been the best.

Is there anyone doing something similar?

Thanks

Martin Carnegie

Gulf Breeze Software Partners

http://www.gulfsoft.com

(imported comment written by BenKus)

Maybe something in here will help: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=406955

Ben

(imported comment written by SystemAdmin)

Hi Ben,

I have been away for the past couple weeks, so I have not had a chance to look at your response yet. I will read up and see if this will work.

Thanks

Martin Carnegie

Gulf Breeze Software Partners

http://www.gulfsoft.com