ayufan / pve-backup-server-dockerfiles

Unofficial, and unmaintained build of proxmox-backup-server
322 stars 57 forks source link

read_meminfo failed - unable to read ...pages_sharing" #8

Closed caraar12345 closed 2 years ago

caraar12345 commented 2 years ago

Hey there! I've been using PBS through Docker for a while now with no issues, but today I can't get it to start.

It's repeatedly spitting out the below to the logs but not booting up.

read_meminfo failed - unable to read "/sys/kernel/mm/ksm/pages_sharing" - No such file or directory (os error 2)

Any idea as to what may be causing this?

I'm running the latest debug version (although it was showing up on :latest too) on a Pi 4 with Debian Buster.

ayufan commented 2 years ago

Interesting. Can you try one of the older versions? And don't use one with .debug :)

I'm sure that v2.0.7 works: https://hub.docker.com/r/ayufan/proxmox-backup-server/tags?page=1&ordering=last_updated

sysrq-reisub commented 2 years ago

It starts for me, that error appears only into PBS when I try to view some graphs

dorianim commented 2 years ago

I have the same issue: image

Running on a raspberry pi 3b+ on 64bit raspberrypi os.

dorianim commented 2 years ago

Is it possible, that this is related to RaspberrypiOS not supporting KMS?

dorianim commented 2 years ago

This may be helpful: https://github.com/wofferl/proxmox-backup-arm64/pull/5

ayufan commented 2 years ago

Since this is docker container. Just bind-mount empty file, this should silence this warning very well.

volumes:
  - /dev/null:/sys/kernel/mm/ksm/pages_sharing:ro
dorianim commented 2 years ago

Unfortunately, the docker container does not start with that setting added: image

dorianim commented 2 years ago

The error also appears on the dashboard: image

dorianim commented 2 years ago

Would it be possible to apply the patch from https://github.com/wofferl/proxmox-backup-arm64/pull/5 ? That would solve the problem in a clean way in my opinion :)

ayufan commented 2 years ago

Will do in next round :)

On Wed, 9 Feb 2022 at 21:51, Dorian Zedler @.***> wrote:

Would it be possible to apply the patch from wofferl/proxmox-backup-arm64#5 https://github.com/wofferl/proxmox-backup-arm64/pull/5 ? That would solve the problem in a clean way in my opinion :)

— Reply to this email directly, view it on GitHub https://github.com/ayufan/pve-backup-server-dockerfiles/issues/8#issuecomment-1034180326, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASOSQKEEM7YKFR5UOE6AK3U2LHVDANCNFSM5FL24QOA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

ayufan commented 2 years ago

@dorianim

For time being this should do the trick:

    volumes:
      ...
      - /tmp/pbs-mm:/sys/kernel/mm
    command:
      /bin/bash -c 'mkdir -p /sys/kernel/mm/ksm; echo 0 > /sys/kernel/mm/ksm/pages_sharing; exec runsvdir /runit'
dorianim commented 2 years ago

Yes, that worked, thank you!

Also, thanks a lot for wrapping this up! It is the perfect solution and exactly what I was looking for for a long time :+1:

ayufan commented 2 years ago

@dorianim @caraar12345 You might check v2.1.5 with a fix: https://hub.docker.com/r/ayufan/proxmox-backup-server.

dorianim commented 2 years ago

Works for me! :smile: