search

trilbymedia / grav-plugin-git-sync

Collaboratively Synchronize your Grav `user` folder hosted on GitHub, BitBucket or GitLab
Apache License 2.0
240 stars 58 forks source link

fatal: Out of memory? mmap failed: Cannot allocate memory #148

Closed samuel-fonseca closed 4 years ago

samuel-fonseca commented 4 years ago

I installed and setup git-sync just fine, but when trying to sync the content via the webhook I get this error:

fatal: Out of memory? mmap failed: Cannot allocate memory

I have git logs enabled, the logs are as follows:

[2019-09-04 15:57:16] grav.NOTICE: gitsync[command]: LC_ALL=C cd /home/public_html/user/ && git status pages 2>&1 [] []
[2019-09-04 15:57:16] grav.NOTICE: gitsync[output]: fatal: Out of memory? mmap failed: Cannot allocate memory [] []

Has anyone experienced this issue. I attempted searching but found nothing through the issues page.

w00fz commented 4 years ago

Looks like your VPS might not have enough memory, where is the site running on?

samuel-fonseca commented 4 years ago

Arvixe business shared server ...

-------- Original Message -------- On Sep 4, 2019, 5:19 PM, Djamil Legato wrote:

Looks like your VPS might not have enough memory, where is the site running on?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

w00fz commented 4 years ago

What's the specs? Might have to bump the memory. Some other things i see by googling is that it could be caused by an older version of git.

samuel-fonseca commented 4 years ago

They don't give the specifics, but the memory is plenty fast, I used git in the back end for pretty much anything. I'm not sure that they would increase it anyways 😔

I tried googling, but like I said, could not find a relavant solution to this specific issue.

-------- Original Message -------- On Sep 4, 2019, 5:23 PM, Djamil Legato wrote:

What's the specs? Might have to bump the memory. Some other things i see by googling is that it could be caused by an older version of git.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

samuel-fonseca commented 4 years ago

Some other things i see by googling is that it could be caused by an older version of git.

@w00fz The current version of git running on the server is 2.17.1

w00fz commented 4 years ago

In case this was still not resolved, seems to be related to git on your server: https://stackoverflow.com/a/6812201