Server, cannot allocate memory

Hi,

kopia server does not start:

# kopia server start [...]
[...]
ERROR failed to open repository: unable to create shared content manager: error loading indexes: unable to open pack index "xn282_ffff6200eb60036f448251e4d0b3d5dc-sbbbf215900ef78b7128-c1": mmap error: cannot allocate memory ERROR unable to initialize repository: unable to initialize repository: error opening repository: unable to open repository: unable to create shared content manager: error loading indexes: unable to open pack index "xn282_ffff6200eb60036f448251e4d0b3d5dc-sbbbf215900ef78b7128-c1": mmap error: cannot allocate memory

Deleting the file does not change anything. I tried several times without any luck.

I’ve tried with a different location of cacheDirectory, it started working for a while but failed and I got the same errors once again.
Kopia is now useless :frowning:

1 Like

I have a similar issue, if you resolved it can you update on this topic please?

How did you connect to your repository? (sftp, filesystem, s3 etc…) also where is your repository is located? (s3, gdrive etc)

My topic here is hidden, for some reason it think’s I am spamming, but on slack there it is:

Thanks!

Does it work with a new repo local on your disk? If it does, can you do any other read-only commands with the corrupt repo, like restoring?

Looks like the hint from @jkowalski on Slack is a solution to my problem:

also check sysctl vm.max_map_count on my system it shows 262144

1 Like

Mine too! :blush: :hearts: Thanks!