- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
We had issues with app control and url filtering blade today and this fixed our issues per recommendation from TAC..
cd $FWDIR/appi/update/
curl_cli -O http://secureupdates.checkpoint.com/appi/v4_0_1/gw/appi_db.C.tmp
mv appi_db.C.tmp appi_db.C
fw load_sigs
As the relevant R&D group manager, I can share that:
Hello all,
The issue with the update is expected to be resolved now. However, if you are still experiencing it, here is the workaround (mostly mentioned above already).
- APPI is no longer working with the following error messages:
[ERROR]: appi_app_db_get_app_log_data: failed getting application object from hash
- Issue occurs after URLF/APPI database update
(
:pkg_file_name ("appi_urlf_db_pkg.tar")
:md5sum ("0e8f4e2b5d1172413fce76d31728e3cb")
:pkg_version (230419_5)
:appi_version ("220419_1")
:urlf_version ("230419_5")
:pkg_timestamp (1556039502)
:appi_filename ("appi_db.C.tmp")
:urlf_filename ("urlf_db.bin.tmp")
)
The workaround is needed until the package version (highlighted) shows 230419_6 / 240419_1 or higher
If after all the steps above the issue is not resolved, please open a TAC case at once.
Hi!
This started yesterday. I saw this issue customers running on R80.10
Support should give you valid appi db file and after this is recommendation to move it to current one:
1. Download the following file: appi_db.C.tmp
2. Copy it on the gw to: $FWDIR/appi/update/
3. Rename it to appi_db.C
4. Load signatures with “fw load_sids”
BR
Vato
What did it effect exactly,
we had a problem with SMTP over TLS which Check Point started to drop yesterday afternoon without any clear reason
The same here. Everything as you described.
If you restart the firewall it will block all the traffic. You need to change db file without reboot
I just talked to support
you can verify the issue with the following command:
grep -i appi_app_db_get_app_log_data /var/log/messages*
and get
"pp_db_get_app_log_data: failed getting application object from hash"
Nasty bug!!!
Does it occur only in R80.10 or also other versions?
We have only seen it on r80.10 in our customers estates at the moment.
Does a policy push then overwrite these values/files ? or are we safe to carry on as normal once the TAC workaround is in place?
thanks
Peter
So far I saw only R80.10 with automatic updates enabled on the gateway side.
There is no sk for this. support center should create it for other customers as soon as possible. It is not a lite bug it makes a big problem to the production environment
BR
Vato
Any WA you have applied is not needed anymore.
TAC is getting their updates from me.
Your package version is fine, please let me know if you suffer anything related to this case.
Hi Vato,
Can you please enable online online update and clarify if the issue has been resolved for you?
There is no need to apply any workarounds any this phase.
Thanks....
--Mor
The fix has worked for us - has anyone verified if a reboot / policy install overwrites the fix?
Hi All,
The issue has been resolved ~15 hours ago.
No need for manual overrides or turning off Automatic Updates.
Thanks...
--Mor
Hi Martin,
Can you re-enable online update and reply if the issue has been resolved for you?
Thanks...
--Mor
In our case, we tried to turn-off turn-on automatic updates but it was not getting it. Only db replacement is solving it.
Can you please share the output of:
cat $FWDIR/appi/update/Version
10x, looking great.
Any pkg version => 240419_1 (yours is 240419_3) should work without any issues.
@Mor_Himi shoulnd't be here https://status.checkpoint.com/ any sort of note ?
Good question.
Since the issue and its resolution didn't involve any of our cloud services it doesn't seem like the correct place.
I will however check internally how best to communicate such incidents going forward.
As the relevant R&D group manager, I can share that:
Hello all,
The issue with the update is expected to be resolved now. However, if you are still experiencing it, here is the workaround (mostly mentioned above already).
- APPI is no longer working with the following error messages:
[ERROR]: appi_app_db_get_app_log_data: failed getting application object from hash
- Issue occurs after URLF/APPI database update
(
:pkg_file_name ("appi_urlf_db_pkg.tar")
:md5sum ("0e8f4e2b5d1172413fce76d31728e3cb")
:pkg_version (230419_5)
:appi_version ("220419_1")
:urlf_version ("230419_5")
:pkg_timestamp (1556039502)
:appi_filename ("appi_db.C.tmp")
:urlf_filename ("urlf_db.bin.tmp")
)
The workaround is needed until the package version (highlighted) shows 230419_6 / 240419_1 or higher
If after all the steps above the issue is not resolved, please open a TAC case at once.
Should work just fine
indeed as Valeri mentioned, R77.X wasn't affected.
It sounds like a non-technical question but what is the best we can answer to customers who involved this issue and asking: How can we be sure it will not happen again?
BR
Vato
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY