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

# sk119841 - fw_full process consumes 100% CPU

| Property | Value |
|----------|-------|
| Solution ID | sk119841 |
| Date Created | 2017-08-13 |
| Last Modified | 2020-07-07 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server |
| Versions | R82.10, R82, R81.20, R82.10, R82, R81.20 |

## Symptoms

- * fw_full process is using 99-100% CPU indefinitely, with multiple FW_FULL instances (3 max).
* When debugging the issue `fwd.elg` gets filled with the following messages (run ` tail -10 fwd.elg` to view:

  ```
  fwasync_create_socket_bindopt: socket() failed: Too many open files
  ```

* A reboot resolves the issue for 2-3 hours and then the issue is back.

## Cause

The fw_full process seems to be on 100% due to a socket overflow - it cannot handle cpd requests. cpd overloaded fw_full process due to a failure in initializing the thresholds mechanism, which is configured by thresholds.conf file.

## 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