# Error syncing v3 source with CloudQuery EOF issue

**URL:** <https://community.cloudquery.io/t/error-syncing-v3-source-with-cloudquery-eof-issue/445>\
**Category:** CloudQuery Plugins\
**Created:** [January 18, 2024, 2:06pm UTC](https://community.cloudquery.io/t/error-syncing-v3-source-with-cloudquery-eof-issue/445 "2024-01-18T14:06:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![devoted-oryx](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@devoted-oryx](https://community.cloudquery.io/u/devoted-oryx)\
**Post date:** [January 18, 2024, 2:06pm UTC](https://community.cloudquery.io/t/error-syncing-v3-source-with-cloudquery-eof-issue/445/1 "2024-01-18T14:06:35Z")

</div>

Hi CQ team,

I’m receiving the following error:

```auto
Error: failed to sync v3 source
2024-01-18T13:53:27Z ERR exiting with error error="failed to sync v3 source Account1: write client returned error (insert): error reading from server: EOF" module=cli

```

Here is my config:

```auto
path: cloudquery/aws
version: "v23.5.0"
tables:
  - aws_securityhub_findings
destinations: ["postgresql"]

```

Can anyone help me troubleshoot this issue?

---

<div class="post-metadata">

**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\
**Post date:** [January 18, 2024, 2:37pm UTC](https://community.cloudquery.io/t/error-syncing-v3-source-with-cloudquery-eof-issue/445/2 "2024-01-18T14:37:46Z")

</div>

Does this same error happen every time you run a sync? What happens if you sync another table, say, `aws_lambda_runtimes`?

---

<div class="post-metadata">

**Author:** ![devoted-oryx](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@devoted-oryx](https://community.cloudquery.io/u/devoted-oryx)\
**Post date:** [January 18, 2024, 2:59pm UTC](https://community.cloudquery.io/t/error-syncing-v3-source-with-cloudquery-eof-issue/445/3 "2024-01-18T14:59:04Z")

</div>

Hi cq-ben,

It seems it’s related to the memory limit.

---

<div class="post-metadata">

**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\
**Post date:** [January 18, 2024, 3:00pm UTC](https://community.cloudquery.io/t/error-syncing-v3-source-with-cloudquery-eof-issue/445/4 "2024-01-18T15:00:05Z")

</div>

Interesting! How do you determine that? How many accounts + regions are you syncing?

---

<div class="post-metadata">

**Author:** ![devoted-oryx](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@devoted-oryx](https://community.cloudquery.io/u/devoted-oryx)\
**Post date:** [January 18, 2024, 3:01pm UTC](https://community.cloudquery.io/t/error-syncing-v3-source-with-cloudquery-eof-issue/445/5 "2024-01-18T15:01:07Z")

</div>

So basically, I have a central security hub that aggregates findings from all accounts. The accounts count is around 50. I increased the pod memory limit from 1GB to 2GB and now it’s syncing properly (at least it looks like that).