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

# sk183983 - QoS service starts automatically after disabling the QoS blade in SmartConsole

| Property | Value |
|----------|-------|
| Solution ID | sk183983 |
| Date Created | 2025-09-22 |
| Last Modified | 2025-10-08 |
| Technical Level | Advanced |
| Products | Security Gateway, Scalable Platforms |
| Versions | R82, R81.20, R81.10 (EOS), R82, R81.20, R81.10 (EOS) |
| OS | Gaia |
| Platform | Maestro Orchestrator |

## Symptoms

- * The Quality of Service (QoS) blade is disabled in SmartConsole, but the QoS service (Floodgate-1/fgd50) starts automatically on Security Group Members (SGMs) after policy installation. There are no rules in the QoS policy, and no QoS policy on the Security Management Server (Postgres database). Inbound and outbound QoS checkboxes are unchecked on all Security Gateway ports.

* Although all QoS settings are disabled, logs show repeated cycles of starting, stopping, installing, and uninstalling of the QoS service.

* Manual attempts to stop QoS (using the `etmstop` command) are only temporarily effective. The service restarts automatically.

* The folders *$FWDIR/state/local/FG1* and *$FWDIR/state/__tmp/FG1* are present on SGMs and the Single Management Object (SMO), even after disabling QoS.

## Cause

There is a problem with temporary folders on the Security Gateway Module (SGM).

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