R81.20 New Recommended Jumbo - Take #113

[gadt]

Hi All

R81.20 Jumbo HF Take #113 is now our Recommended Jumbo take and is available for download to all via CPUSE (as recommended) and via Jumbo documentation R81.20 

Release Highlight:

A full list of resolved issues can be found in the Jumbo documentation R81.20 

Note:

• Central Deployment allows you to perform a batch deployment of Hotfixes on your Security Gateways and clusters from SmartConsole!! For more information, see sk168597.
• With Blink images, you can upgrade your environment to the required Major version including its recommended Jumbo hotfix in one Step, using a single image file.

You can install Blink images using CPUSE – More details can be found in sk120193

Thanks,

Release Operations Group

[Daniel_]

cppcap not working in take113 😞

Be careful if you debug something and wonder why you can't see anything....

[the_rock]

I actually noticed that too...does  work in take 115 though.. I just tried pinging 8.8.8.8 from lab cluster and it worked fine, when running cppcap -i eth0 -f "host 8.8.8.8" showed me results.

Andy

[VikingsFan]

Anyone else seeing an abnormal increase for management backups?  Still looking into it but this was the first scheduled backup for our management servers and one went from typically being around 1GB to over 200GB in size and blew up our SFTP server.  A different cluster management server went from 1GB to over 50GB in size.

Will be opening a case on Monday but wasn't sure if this is expected.

[the_rock]

I tried, it was okay for me.

[VikingsFan]

I just extracted the 50GB backup file and it looks to be that the /opt/CPsuite-R81.20/fw1/log/ directory is backing up as part of my backup.  Prior backups do not have this directory.  Our main management server has 3.3TB in use for that directory so would explain the out of control backup size.  Will update after my case gets worked.

Does your backup file have the log directory?

[the_rock]

Mine does not, no.

[Lesley]

@VikingsFan https://support.checkpoint.com/results/sk/sk183835

Backup file size on the Security Management Server grows after an upgrade.

Take 115

Take 111, Take 113

PRJ-63371

[the_rock]

Maybe its just my luck, but size on my mgmt is literally the same as it was before, 1.2 GB.

Andy

[VikingsFan]

Thank you @Lesley .  Missed that one.  Will begin looking at upgrading to Take 115 in our lab and then prod.

[the_rock]

@VikingsFan I am on jumbo 115 in the lab, also had couple of customers install it, they seem very happy with it. I know its latest one, but so far, no issues.

Andy

[FXB]

Can confirm that after upgrading from R81.20 Take 105 to Take 115, the backupsize on our openserver increased from 220MB to 9.77GB. So cant really confirm that problem was fixed with take 115.

However after upgrading from R81.20 Take 115 to R82 Take 39 a few days ago, the backup size is normal again now even tho it should only have been fixed in R82 Take 41. Not complaining about it tho.

[Henrik_Noerr1]

we have a performance degradation on our log servers after upgrading to t115.

the SOLR process is eating all available CPUs.

We have a SR ongoing to investigate the issue.

Edit: It fixed itself after 2 days of maxing 48 cores.

/Henrik

[Wolfgang]

We can confirm the increase of the backup size. Tried to do a restore of SMS from this backup, The host configuration (users, network etc.) is ok but the database (rules, objects etc.) is empty after restore. It's like a fresh installed SMS.

Anyone tried a restore ?

[TJ_Aus]

I tried JHFA 113 a while back (up from 105) and started to get identity awareness errors. Had to restart pdpd every few hours on some older 3000 series firewalls. I reverted to 105 and all good.

pdp.elg.1 looked like this below:

T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37281/1
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37281/0
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37281/2
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/0
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/1
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/2
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37520/0
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37520/1
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37520/2
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/0
T_event_do_set: invalid socket/type: 37294/0, socket won't be listened to
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/2
T_event_do_set: invalid socket/type: 37294/2, socket won't be listened to
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/1
T_event_do_set: invalid socket/type: 37294/1, socket won't be listened to
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/0
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/2
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/1
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/0
T_get_event: CP_FD_SETSIZE limit (32768) reached for socket/type: 37294/2
[12328 4045404992]@<name_removed>[11 Sep 7:34:57] [TRACKER]: #169404 -> INTERNAL -> FINI ->
T_event_fdclr_epoll: failed to clear socket: 25 from epoll set: Bad file descriptor
httpMime_destroy_db: Destroying the MIME database.
[15518 4045404992]@<name_removed>[11 Sep 7:35:00] [TRACKER]: #1 -> INTERNAL -> INIT ->
[15518]@<name_removed>[11 Sep 7:35:00] [worker_0] Warning: Message ID 1 processing blocked on function for 1368 milliseconds.
[15518]@<name_removed>[11 Sep 7:35:00] [worker_0] Warning: Messages processing blocked for 1368 milliseconds.
[15518 4045404992]@<name_removed>[11 Sep 7:35:06] [TRACKER]: #2 -> INTERNAL -> RECONF ->
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory

[Steffen_Appel]

@Tes  yes there is a hotfix available for that issue https://support.checkpoint.com/results/sk/sk184028 and it is mentioned in the critial information section now