Processing action site

Usage and Config Platform
1

(imported topic written by SystemAdmin)

When a non-master operator takes actions in our environment we have noticied a long delay for the client to report a status. I’ve looked at the client log file and the client seems to gather right away, but is getting hung at processing action site. I created a new non-masteroperator account to verify this was not a problem with a particular account and I am seeing the same behavior. When taking actions with my masteradmin account clients are processing and posting results right away.

Has anyone seen this behavor? we have a total of 32 operators with 2 master operators.

See log file below (this was a custom action with no action script):

At 12:34:21 -0600 - opsite165 (http://Server.domain.name:52311/cgi-bin/bfgather.exe/opsite165)

Download ‘http://Relay.domain.name:52311/bfmirror/bfsites/manydirlists_72/__diffsite_450354a51a10fb0f5c47422e4569de568f6ca649_to_6d4e7c8c1e8c18fbbc7f41d4364536e7024ccfdc’ as ‘__TempUpdateFilename’

At 12:34:21 -0600 -

Gather merging new file C:\Program Files\BigFix Enterprise\BES Client__BESData\opsite165\Action 64918.fxf

At 12:34:21 -0600 - opsite165 (http://Server.domain.name:52311/cgi-bin/bfgather.exe/opsite165)

Successful Synchronization with FixSite (version 110230) - ‘http://Relay.domain.name:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://Server.domain.name:52311/cgi-bin/bfgather.exe/opsite165&Time=10Nov12:34:21&rand=1e218e52&ManyVersionSha1=450354a51a10fb0f5c47422e4569de568f6ca649’

At 12:34:22 -0600 -

Processing action site.

At 12:53:42 -0600 - opsite156 (http://Server.domain.name:52311/cgi-bin/bfgather.exe/opsite156)

BackgroundAdviceEvaluation NonTargetedFile optimization of C:\Program Files\BigFix Enterprise\BES Client__BESData\opsite156\Action 64917.fxf

At 12:53:44 -0600 - opsite165 (http://Server.domain.name:52311/cgi-bin/bfgather.exe/opsite165)

Relevant - Custom Action (fixlet:64918)

At 12:53:45 -0600 -

ActionLogMessage: (action 64918 ) Action signature verified

ActionLogMessage: (action 64918 ) starting action

At 12:53:46 -0600 -

ActionLogMessage: (action 64918 ) ending action

At 12:53:46 -0600 - opsite165 (http://Server.domain.name:52311/cgi-bin/bfgather.exe/opsite165)

Not Relevant - Custom Action (fixlet:64918)

2

(imported comment written by cstoneba)

maybe try forcing the propagation of all users?

besadmin.exe /propagatealloperatorsites

3

(imported comment written by SystemAdmin)

That did not seem to help.

I deployed an action with this account almost an hour ago, but still not seeing an updated status and the log does not show that the action has run.

4

(imported comment written by SystemAdmin)

This issue was related to having too many open actions in the master operator site.

5

(imported comment written by cstoneba)

how many was too many? I imaging it’s not the number of actions, but the number of components of each action. For example, multiple baselines actions would contain more actions then just single actions being deployed.

6

(imported comment written by SystemAdmin)

Yes, there were a lot of baselines with several components. I think we were probably pushing around 1,000 tasks between individual actions and baseline components. I’ve since made some baselines smaller and opened the actions using a non master operator account.

7

(imported comment written by Shawn_Jefferson)

Hi,

I’m having the exact same issue with my system. Non-master operator actions take a long time for the clients to report, evaluate and run, but master operator actions are run almost immediately. It’s also a bit sporadic when non-master operator actions will be slow.

We have a few open actions, but not that many. This behaviour started some time ago, but I can’t pinpoint the exact time that it started to appear.

Is there an official bugfix or other explanation/fix for this problem?

Thanks,

Shawn