sk182033 - Login to SmartConsole fails when the Compliance blade runs scheduled scans
Login to SmartConsole fails when the Compliance blade runs scheduled scans
Symptoms
- Login to SmartConsole fails when the Compliance blade runs scheduled scans. The Compliance blade scheduled scans run at different times.
Solution
This problem was fixed. The fix is included in:
- Check Point R82
- Jumbo Hotfix Accumulator for R81.20 starting from Take 70
- Jumbo Hotfix Accumulator for R81.10 starting from Take 152
If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.
For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.
Hotfix installation instructions:
Refer to sk168597 - How to install a Hotfix.
On versions R81.20 and earlier, after you install the Hotfix:
Backup and edit
grc.conf. Run:[Expert@HostName]# cp -pv $MDS_FWDIR/conf/grc.conf{,_BKP}[Expert@HostName]# vi $MDS_FWDIR/conf/grc.confRemove this line:
interpreterSchedPeriod=86400Add these values at the bottom of
grc.conf:interpreterSchedPeriodDay=7interpreterSchedPeriodHour=23interpreterSchedPeriodMin=59interpreterSchedPeriodSec=59By default, this schedules the Compliance blade to run every day at 23:59:59.
interpreterSchedPeriodDayis the day of the week. 0=Sunday, 1=Monday, 2=Tuesday, 3=Wednesday, 4=Thursday, 5=Friday, 6=Saturday, 7 = every day.interpreterSchedPeriodHouris the hour of the day which can be between 0-23.interpreterSchedPeriodMinandinterpreterSchedPeriodSeccan be between 0-59.Save the changes in the
Vieditor and restart thefwmprocess to apply the changes.
On version R82 For R82 the necessary configuration is already included in $MDS_FWDIR/conf/grc.conf.
NOTE
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.