> Source: [sk165352](https://support.checkpoint.com/results/sk/sk165352)

# sk165352 - SmartEvent does not shows logs, and the 'log_indexer' process stops working

| Property | Value |
|----------|-------|
| Solution ID | sk165352 |
| Date Created | 2020-03-03 |
| Last Modified | 2025-01-22 |
| Technical Level | Advanced |
| Products | Security Management Server |
| Versions | R82.10, R82, R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * SmartEvent / SmartLog does not show logs.

* The "log_indexer" process stops working. There are core dump files for he "log_indexer" process in the */var/log/dump/usermode/* directory.

  <br />

## Cause

There is an inconsistency between the number of lines in the header and the **actual** number of lines in *$INDEXERDIR/data/FetchedFiles*.

Example from an incorrect 'FetchedFiles' file:

The **header** contains the value **26**, but the actual number of lines is **24** + 1 = **25**.
> **22 serialization::archive 10 0 0 0 0 26 1 0 1 3 1 0**  
> 0 9 127.0.0.1 21 2016-10-22_235900.log 1477157778 1 788391 0 0 0 0 3  
> 1 9 127.0.0.1 24 2016-10-23_000000.adtlog 1477156209 1 31 0 0 3  
> 2 9 127.0.0.1 21 2016-10-22_133618.log 1477156209 1 46 0 0 3  
> ... ... ... *truncated for brevity* ... ... ...  
> 23 13 10.254.222.76 21 2015-10-03_163039.log 1443882639 0 0 0 0 3  
> **24** 13 10.254.222.76 21 2015-08-19_043039.log 1439951439 0 0 0 0 3

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content