topic Re: Getting system alert-high for Wildfire update failure, failed to extract file in Panorama Discussions

Getting system alert-high for Wildfire update failure, failed to extract file

Wayne_Ajimine — Thu, 07 Apr 2022 01:02:04 GMT

This is occurring on our Panorama. Content of email alert is:

Type: SYSTEM
Subtype: general
Time: Apr 07 2022 00:12:55 GMT
Severity: high
Details: "Failed to extract file panupv3-all-wildfire-652605-655839.tgz with sha256: 647eedc7698709983f5e9d99dc0428cac00b16aef603a703b4e8572f041411eb"

Not sure how to proceed to resolve.

Re: Getting system alert-high for Wildfire update failure, failed to extract file

Henry-el-Hajj — Thu, 28 Jul 2022 08:39:49 GMT

has this issue been solved?

Re: Getting system alert-high for Wildfire update failure, failed to extract file

Lee_S — Mon, 29 Aug 2022 18:15:29 GMT

We are seeing this daily on PA-5220(no Panorama), v10.0.11(will soon get to 10.1 next maintenance day) for these files:

SYSTEM ALERT : high : Failed to extract file panupv2-all-contents-8610-7534.tgz
SYSTEM ALERT : high : Failed to extract file panupv2-all-contents-8611-7538.tgz
SYSTEM ALERT : high : Failed to extract file panup-all-antivirus-4186-4699.tgz
SYSTEM ALERT : high : Failed to extract file panup-all-antivirus-4190-4703.tgz

When We check, the file actually installed.

Re: Getting system alert-high for Wildfire update failure, failed to extract file

CyberEye — Wed, 12 Jul 2023 09:43:34 GMT

Same occurring in our firewall which is acting as passive.Any one has an idea about the root cause. Using PAN-OS 10.1.8-h2

Failed to extract file panupv3-all-wildfire-784991-788674.tgz with sha256: e8f76e669aafcec6de3193574e953a9dd28504635a651526e6c8475cb228e4bf

Failed to extract file panupv3-all-wildfire-784933-788610.tgz with sha256: 9986ceb7ab6e4b84e944d83125a9de47eba46626aba51b5d3d51c7b50f578d7a

Failed to extract file panupv3-all-wildfire-784833-788501.tgz with sha256: 1e8ab5e4a130603be6bb3eee23d6f66c29a993c98db5a651462f5b4927accb15

Failed to extract file panupv3-all-wildfire-784342-787928.tgz with sha256: 98b87ace25725198ddfa447368daddf520a27bcb7de27cca70da843a701d1e5b

Failed to extract file panupv3-all-wildfire-784142-787727.tgz with sha256: 0298adf315d2e1f28a96acd86f5ae6d43457f56fc25150b8858413e767507f4d

Failed to extract file panupv3-all-wildfire-784004-787589.tgz with sha256: 5bba76e6dedda6c21b245dba76d85ecbd6c8d9e7e3dba4e5e787db595510be6f

Failed to extract file panupv3-all-wildfire-783747-787331.tgz with sha256: 6879548b453fec5df9fe1a09e4409578bc9aeddab5e850091c390312d026017c

Failed to extract file panupv3-all-wildfire-783699-787283.tgz with sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Re: Getting system alert-high for Wildfire update failure, failed to extract file

mikko.hayrinen — Tue, 30 Jan 2024 05:30:28 GMT

me too, 10.2.6. randomly getting same error, but still updates are installed.

Re: Getting system alert-high for Wildfire update failure, failed to extract file

TerenceOyape — Wed, 27 Mar 2024 15:53:34 GMT

We just recently updated to 10.2.7-h3. Just started seeing a similar error appear for the wildfire and antivirus dynamic updates 2 days ago. The subsequent scheduled updates succeed though.

Re: Getting system alert-high for Wildfire update failure, failed to extract file

MichaelTiernan — Tue, 23 Jul 2024 13:01:16 GMT

Did you ever get the reason why this is happening? Was there a fix. We are getting this type of error now 7/22/2024.

Re: Getting system alert-high for Wildfire update failure, failed to extract file

CyberEye — Tue, 23 Jul 2024 20:44:15 GMT

@Henry-el-Hajj Try to disable sync to peer on one of the firewalls. I made this and the logs getting stopped.

Mark this as the solution if the issue has been resolved.

Re: Getting system alert-high for Wildfire update failure, failed to extract file

Veloman — Wed, 31 Jul 2024 07:37:49 GMT

I'm also getting this on our PA-5250 HA pair on v10.2.8-h4.
module: general
severity: high
opaque: Failed to extract file panupv3-all-wildfire-

Will try the "disable sync to peer" on FW1. But I assume you only have to switch it off and then back on again.

Has a reason for this occuring been given yet?