- CheckMates
- :
- Products
- :
- General Topics
- :
- After update to R81.20 – logs are lost
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After update to R81.20 – logs are lost
After update MGMT from R81.10 to R81.20 Jumbo Hotfix Take 79 I lost all my log. So I follow https://support.checkpoint.com/results/sk/sk111766 but logs show only for few days. (I want to index for 180 days)
Should I try something else or should I repeat procedure?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you see them if you open old school smartview tracker?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Depending on how many logs you have, it can take some time to fully index the old logs.
If you're concerned it isn't working, I'd check with TAC: https://help.checkpoint.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dealing with a large amount of logs, how can I check if it is still indexing?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Check there on your management server: $INDEXERDIR/log/log_indexer.elg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Log Indexing is enbale. I can see log if I go to File - Open Log File. Thanks for help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
try to force re-index https://support.checkpoint.com/results/sk/sk111766 or re-index single log files by fw logsrepair command
