Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to unlock SHM lock #2350

Open
hgschwibbe opened this issue Mar 7, 2025 · 1 comment · Fixed by #2351
Open

Failed to unlock SHM lock #2350

hgschwibbe opened this issue Mar 7, 2025 · 1 comment · Fixed by #2351

Comments

@hgschwibbe
Copy link

hgschwibbe commented Mar 7, 2025

Versions

Core version is v6.0.5 (Latest: v6.0.5)
Web version is v6.0.2 (Latest: v6.0.2)
FTL version is v6.0.4 (Latest: v6.0.4)

Platform

  • OS and version: Debian 12.9.0
  • Platform: Hyper-V VM on Windows Server 2019

Actual behavior / bug

The following error appears in /var/log/pihole/FTL.log:

2025-03-06 20:58:10.562 ERROR Failed to unlock SHM lock: Operation not permitted in api_history_clients() (/app/src/api/history.c:105)
2025-03-06 20:58:10.564 ERROR Failed to unlock outer SHM lock: Operation not permitted

Image

Steps to reproduce

The error appears automatically in the log.

The Docker solution described here did not work because I installed via basic-install.sh:
pi-hole/docker-pi-hole#914

I also tried to add some capabilities, but it did not work:
Image

Debug Token

pihole_debug.log

Image

@DL6ER DL6ER transferred this issue from pi-hole/pi-hole Mar 7, 2025
@DL6ER
Copy link
Member

DL6ER commented Mar 7, 2025

Thank you for the report. Will be fixed by #2351

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants