> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/manage-content/sync-content-to-tenant-accounts/troubleshoot-errors-when-syncing-all-accounts.md).

# Troubleshoot Errors When Syncing All Accounts

Troubleshoot all-account sync errors in large Cortex XSOAR 6.15 multi-tenant environments.

When trying to sync all accounts in a large scale environment, the sync fails. The log shows that there are too many open files and the sync fails to open any additional files.

To resolve this issue, update the limit of the number of files on the Cortex XSOAR service level as follows:

1. Open the **demisto.service** file on each host. It is located at `/etc/systemd/system/demisto.service`.
2. Under **\[Service]**, update the following parameters with a number large enough to avoid the error. If these parameters do not exist, add them.

   * `LimitNOFILE`
   * `LimitNOFILESoft`

   For example:

   ```screen
   [Unit]
   Description=Demisto Server Service
   After=network.target

   [Service]
   LimitNOFILE=100000000
   LimitNOFILESoft=100000000
   WorkingDirectory=/usr/local/demisto
   Type=simple
   User=demisto
   ExecStart=/usr/local/demisto/server
   EnvironmentFile=/etc/environment
   Restart=always
   RestartPreventExitStatus=29

   [Install]
   WantedBy=multi-user.target
                   
   ```
3. Reload the daemon.

   `systemctl daemon-reload`
4. Restart the service.

   `systemctl restart demisto`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/manage-content/sync-content-to-tenant-accounts/troubleshoot-errors-when-syncing-all-accounts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.