- Products
- Learn
- Local User Groups
- Partners
- More
What's New in Check Point SASE
Wednesday, 9 September @ 5pm CET / 11am EDT
The State of Ransomware Q2 2026:
This Quarter's Trends, and Their Impact on Your Defenses
AI Security Masters
Implementing the AI Security Trifecta
CheckMates Go:
Half is Not Enough
Hi friends,
I am facing some issues with logs and monitor. logs are not showing in logs and monitor tab. Please find the attachment. Please share a solution if anyone has experience in the same issue.
R80.40
Regards,
RB
Hi friends,
I am facing some issues with logs and monitor. logs are not showing in logs and monitor tab. Please find the attachment. Please share a solution if anyone has experience in the same issue.
R80.40
Regards,
RB
I found in the past that what works is one of 2 below things (not always recommended, but they do work)
1- create a dummy duplicate cp host ( NOT regular host, but the one where it lets you choose it as logging server) and then once you save that, go to logs under firewall and add that new object as logging server (just give it same IP as actual mgmt object). Install database, push policy. If logging works, then leave it like that for 24 hours, then delete dummy object and revert back to old config.
2- edit $FWDIR/conf/masters file on affected gateway and change name in all 3 fileds to actual mgmt IP address reflected in dashboard object. Also, apply below sk:
Alternatively, please follow what @Tal_Paz-Fridman mentioned, those are all valid points.
Please update us on results.
Cheers,
Andy
I found in the past that what works is one of 2 below things (not always recommended, but they do work)
1- create a dummy duplicate cp host ( NOT regular host, but the one where it lets you choose it as logging server) and then once you save that, go to logs under firewall and add that new object as logging server (just give it same IP as actual mgmt object). Install database, push policy. If logging works, then leave it like that for 24 hours, then delete dummy object and revert back to old config.
2- edit $FWDIR/conf/masters file on affected gateway and change name in all 3 fileds to actual mgmt IP address reflected in dashboard object. Also, apply below sk:
Alternatively, please follow what @Tal_Paz-Fridman mentioned, those are all valid points.
Please update us on results.
Cheers,
Andy
Just solved a similar problem. The GW was transmitting logs to the management console but they were not displaying. We added the management console to the GW hosts file and the problem resolved. Perhaps the management console needs to be informed when it should review the log file - just a WAG.
Just solved a similar problem. The GW was transmitting logs to the management console but they were not displaying. We added the management console to the GW hosts file and the problem resolved. Perhaps the management console needs to be informed when it should review the log file - just a WAG.
I've seen this when the management server had 0 bytes free on the /var/log partition. Check your local disk space.
Check if the gateways are sending logs:
netstat -nap |grep :257
cpstat mg -f log_server
If your management is behind NAT, do as @the_rock and @Tal_Paz-Fridman suggested.
I've seen this when the management server had 0 bytes free on the /var/log partition. Check your local disk space.
Check if the gateways are sending logs:
netstat -nap |grep :257
cpstat mg -f log_server
If your management is behind NAT, do as @the_rock and @Tal_Paz-Fridman suggested.