BES Relay update failing

Usage and Config Platform
1

(imported topic written by SystemAdmin)

I’m running the fixlet "Updated BES Relay Now Available! (Version 7.2.5.22) and I’m getting a status of “Download Failed” for all relays. The BES root server was successfully updated to this latest version. These relays are all running v7.2.4.60. Any ideas on where to begin troubleshooting?

2

(imported comment written by SystemAdmin)

Same issue here. I did notice that three different versions of the BES Relay are downloaded on the server - “Trend”, “IBM” and standard “BigFix”. The relays report the downloads are availible and then fail.

Client Log From Relay (Download was retried 8 times - I removed the duplicate attempts here):

At 13:03:22 -0400 -

DownloadsAvailable: checking for ‘http://127.0.0.1:52311/bfmirror/downloads/3436/0’

DownloadsAvailable: true (action id 3436)

At 13:03:56 -0400 -

DownloadsAvailable: checking for ‘http://127.0.0.1:52311/bfmirror/downloads/3436/0’

DownloadsAvailable: true (action id 3436)

ActionLogMessage: (action 3436 ) Non-Distributed - DownloadsAvailable

ActionLogMessage: (action 3436 ) Submitting download request

ActionLogMessage: (action 3436 ) Download url: ‘http://software.bigfix.com/download/bes/72/Trend-BESRelayUpgrade-7.2.5.22.exe’ (skip non relevant)

ActionLogMessage: (action 3436 ) Download url: ‘http://software.bigfix.com/download/bes/72/IBM-BESRelayUpgrade-7.2.5.22.exe’ (skip non relevant)

ActionLogMessage: (action 3436 ) Download url: ‘http://software.bigfix.com/download/bes/72/BESRelayUpgrade-7.2.5.22.exe’

At 13:03:59 -0400 -

DownloadsAvailable: checking for ‘http://127.0.0.1:52311/bfmirror/downloads/3436/0’

DownloadsAvailable: true (action id 3436)

ActionLogMessage: (action 3436 ) Non-Distributed - DownloadsAvailable

ActionLogMessage: (action 3436 ) JobFailed - cancel and fail action

ActionLogMessage: (action 3436 ) DownloadJobFailed

At 13:04:00 -0400 -

ActionLogMessage: (action 3436 ) ending action

3

(imported comment written by jessewk)

An updated version of the task has been published to resolve this issue. You can trigger a site gather in the Manage Sites dialog to make sure you have the latest version or your server should update itself within an hour.

4

(imported comment written by EspenD91)

I had the same issue. Relay download failed, but other content downloaded fine to the same relays. All files cached on the BES-server. Didnt’t bother to research it further. Used the Software deployment wizard (with BESRelayUpgrade-7.2.5.22.exe -s) and copied relevant parts from the action script. That worked.

Espen

Norway

5

(imported comment written by SystemAdmin)

jessewk

Thanks! We performed the gather and redeployed successfully. The only question we have is how do we know when the fixlet has been updated? There is no version # or change log. After issuing the gather, we had no idea if it worked or if we had the newer fixlet. We just redployed and hoped.

Thanks,

John

6

(imported comment written by ggerling91)

I called support about this issue this morning and some other issues last week. I was told that the fixlet would be updated but I didn’t know when or how I would be able to tell that it did indeed get updated. I have been waiting for some kind of email or call to let me know the status. It would be very helpful if we could get verison numbers or timestamps on fixlets. It would make troubleshooting much easier.

7

(imported comment written by Aram_Eblighatian)

Hi All,

I agree that an easier way to let console operators know of new content/Fixlets would be a good thing, and I believe we are considering various options for future product there, but in the meantime, there is at least one way that can give you an idea as to whether or not the Content for a given Fixlet Site has been updated. In the Console, if you go to the ‘Tools’ menu then select ‘Manage Sites’, the various Fixlet Sites that your BigFix Server subscribes to will be listed. If you select the Site in question (in this case the Fixlet resided in the BES Support site), and click the ‘Properties’ button, a window will come up that includes the version number of the Site itself. So, in a case like this, you could check the version of your Site once speaking to support, and be confident that if the Site version increments by one, that it’s been updated by BigFix, and that your server has in fact gathered the updated version. Note that through this same dialog box (the ‘Manage Sites’ window), you can click the ‘Gather All Sites’ button as Jesse describes above, and compare the Site versions to ensure you have the most up to date content.

One other quick note: if you had the Relay upgrade Fixlet document open, you would have received a small pop-up message that it had been updated when your BigFix Server gathered the latest version.

Thanks!

-Aram

8

(imported comment written by ggerling91)

Thanks Aram

I often have many fixlet/task documents open at the same time when I receive the pop up message that a new verison has been propagated. It would be nice to know in the pop up which site received the update.

Greg

9

(imported comment written by SystemAdmin)

Ahh this is good to know. While we eagerly await the upgrades to the console to let us know of updated content, could something be done in Web Reports to kick off an email if the Fixlet Site version number has changed? Sort of a poor man’s alerting system for BigFix?