Strange Failure Report

Usage and Config Platform
1

(imported topic written by Steve91)

Hi Chaps,

A fixlet I take keeps reporting back as a failure although all stages of it have a status of completed and it successfully executes on the server.

Please see below:

The action has been run 1 time, and will not be run again.

The action failed.

Completed: download http://xxxxxxxx/Uploads/9770b96b0340d9c671cd69eca7f52497fb4e8acd/big13CE.tmp

Completed: continue if { (size of it = 152 and sha1 of it = “9770b96b0340d9c671cd69eca7f52497fb4e8acd”) of file “big13CE.tmp” of folder “__Download”}

Completed: extract big13CE.tmp

Completed: download http://xxxxxxxx/Uploads/64fe2cc0fd93885b142d163a83cc244fcbb5ecfc/big13CF.tmp

Completed: continue if { (size of it = 32059 and sha1 of it = “64fe2cc0fd93885b142d163a83cc244fcbb5ecfc”) of file “big13CF.tmp” of folder “__Download”}

Completed: extract big13CF.tmp

Completed: download http://xxxxxxxx/Uploads/79ad298c7fca5350cfceb5a7dd8e8db9c316f10f/big13D0.tmp

Completed: continue if { (size of it = 152 and sha1 of it = “79ad298c7fca5350cfceb5a7dd8e8db9c316f10f”) of file “big13D0.tmp” of folder “__Download”}

Completed: extract big13D0.tmp

Completed: download http://xxxxxxxx/Uploads/1fa385bb8640b6ca2f74f7fc1ee1ff0a63953686/big13D1.tmp

Completed: continue if { (size of it = 5722 and sha1 of it = “1fa385bb8640b6ca2f74f7fc1ee1ff0a63953686”) of file “big13D1.tmp” of folder “__Download”}

Completed: extract big13D1.tmp

Completed: wait “__Download\dump.bat”

The log on the server also reports a success:

Command succeeded wait “__Download\dump.bat”

At 11:21:07 +0100 - opsite108 (http://xxxxxxxx/cgi-bin/bfgather.exe/opsite108)

Fixed - Copy Eventlog Backup Script To Non ENT Servers

We’re using BigFix 5.1.9.12

Any suggestions as to why this may be occuring?

Many thanks

Steve

2

(imported comment written by jessewk)

Steve,

The relevance for your Fixlet is true both before and after the action is run, so the client considers it a failure even though all lines completed.

You have a few options:

  1. You can create a Task instead of a Fixlet

  2. When deploying your action, chose ‘Run this action on all relevant computers, and consider the action sucessful once all lines of the action have been executed’ on the ‘Relevance’ tab. In 6.0 this setting is on the ‘Success Criteria’ tab. This setting is the difference between a Task and a Fixlet.

  3. Modify the relevance so that it is true before the action is run and false after the action completes.

-Jesse