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

# sk133632 - FWD does not come back up after manually killing the process

| Property | Value |
|----------|-------|
| Solution ID | sk133632 |
| Date Created | 2018-08-11 |
| Last Modified | 2018-09-02 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * FWD does not start after manually killing the process.

* The *fwd.elg* file shows following error after manually starting FWD:  

  `
  fw device (/dev/fw0) is already locked by another process`

* The output of `'#lsof /dev/fw0'` shows multiple PID's for *curl_cli* processes.

* The output of `'#ps aux | grep curl_cli'` shows the same PID's from `'#lsof /dev/fw0'` command.

## Cause

There is another process that has locked */dev/fw0* and will not allow FWD to start.

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