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

# sk180509 - Some Maestro Hyperscale Orchestrator processes might go down after you install the R81.10 Jumbo Hotfix and reboot

| Property | Value |
|----------|-------|
| Solution ID | sk180509 |
| Date Created | 2023-01-15 |
| Last Modified | 2023-03-08 |
| Technical Level | General |
| Products | Scalable Platforms |
| Versions | R81.10 (EOS) |
| OS | Gaia |

## Symptoms

- * Some processes on a Maestro Orchestrator might go down after you install a Jumbo Hotfix Accumulator and the Maestro Orchestrator reboots for the first time.

  Possible impact:
  * Connectivity issues through Security Groups.
  * If you add a new Security Group Member to a Security Group, it might not start the joining process.
* If you reboot the Maestro Orchestrator manually (for the second time), the issue does not occur again.

* This issue might occur in the R81.10 Jumbo Hotfix Accumulator Takes 79-87.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 93

If you choose not to upgrade, follow these steps:

1. To check if some processes are down, run the HealthCheck Point (HCP) tool ([sk171436](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk171436)) on **each**Orchestrator in the Expert mode:

   `hcp -r all`
   If the test "**Daemons state** " fails, it means that some daemons are down on one of the MHOs and should be manually brought up. (See below commands)  

2. An additional way to check whether this issue occurs is to run the following command on each one of the MHOs:  
   `ps auxww | grep -E "pmd|ssm_lsp|maestro_daemon|p_ch|fsync" | grep -v grep`
3. In case maestro_daemon, ssm_pmd, ssm_lsp, p_ch or fsyncd are down, then execute the following commands on the relevant MHO in order to resolve this issue:  
   Note: Even if one of the daemons is up, running the below commands will not have any negative impact.

   1. `tellpm process:ssm_pmd t`

   2. `tellpm process:ssm_lsp t`

   3. `tellpm process:maestro_events_runner t`
   4. `tellpm process:p_ch t`

   5. `tellpm process:fsyncd t`

   <br />

4. After running the above commands, verify that all of the daemons are up:

   `ps auxww | grep -E "pmd|ssm_lsp|maestro_daemon|p_ch|fsync" | grep -v grep`
   `hcp -r all`

**Note:**You can resolve this issue by rebooting the Maestro Orchestrator, but the procedure above is sufficient and does not cause a traffic impact.

---

# 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