SHM Errors in FTL.log for V6 Development

General Beta 6.0
1

The issue I am facing:
In FTL.log I see these error lines since last update from this weekend:

2025-01-13 08:31:15.167 CET [134518/T134546] INFO: Received 8/8 valid NTP replies from ntp.time.nl
2025-01-13 08:31:15.167 CET [134518/T134546] INFO: Time offset: 2.530962e+00 ms (excluded 0 outliers)
2025-01-13 08:31:15.167 CET [134518/T134546] INFO: Round-trip delay: 7.506073e+00 ms (excluded 0 outliers)
**2025-01-13 09:24:27.377 CET [134518/T134549] ERROR: Failed to unlock SHM lock: Operation not permitted in resolveClients() (/app/src/resolve.c:956)**
**2025-01-13 09:24:27.377 CET [134518/T134549] ERROR: Failed to unlock outer SHM lock: Operation not permitted**
2025-01-13 09:31:16.171 CET [134518/T134546] INFO: Received 8/8 valid NTP replies from ntp.time.nl
2025-01-13 09:31:16.171 CET [134518/T134546] INFO: Time offset: 2.807106e+00 ms (excluded 1 outliers)
2025-01-13 09:31:16.171 CET [134518/T134546] INFO: Round-trip delay: 7.566520e+00 ms (excluded 1 outliers)
2025-01-13 10:31:17.105 CET [134518/T134546] INFO: Received 8/8 valid NTP replies from ntp.time.nl
2025-01-13 10:31:17.106 CET [134518/T134546] INFO: Time offset: 2.430814e+00 ms (excluded 1 outliers)

Details about my system:
Ubuntu 24.04.1 LTS (GNU/Linux 6.1.0-odroid-arm64 aarch64)
Monday, 13 January 2025, 04:08:09 PM
Up time: 12 days, 20:03:37
Free memory: 2113748 / 3757004 kB
Hardware Odroid-c4 SBC

What I have changed since installing Pi-hole:
Updated every week. No other changes.

Your debug token is: https://tricorder.pi-hole.net/3jqPv6bK/

During executing pihole -d, I got these error lines in ftl.log:

2025-01-13 16:16:59.694 ERROR Failed to unlock SHM lock: Operation not permitted in resolveClients() (/app/src/resolve.c:956)

2025-01-13 16:16:59.694 ERROR Failed to unlock outer SHM lock: Operation not permitted

2025-01-13 16:16:59.695 ERROR Failed to unlock SHM lock: Operation not permitted in resolveClients() (/app/src/resolve.c:956)

2025-01-13 16:16:59.695 ERROR Failed to unlock outer SHM lock: Operation not permitted

Version information:

CORE_VERSION=v5.18.4-600-gefaa0f4
CORE_BRANCH=development
CORE_HASH=efaa0f42
GITHUB_CORE_VERSION=null
GITHUB_CORE_HASH=efaa0f42
WEB_VERSION=v5.21-1058-g603f35d5
WEB_BRANCH=development
WEB_HASH=603f35d5
GITHUB_WEB_VERSION=null
GITHUB_WEB_HASH=603f35d5
FTL_VERSION=vDev-bed065c
FTL_BRANCH=development
FTL_HASH=bed065cc
GITHUB_FTL_VERSION=null
GITHUB_FTL_HASH=bed065cc
2

I am seeing the same errors in FTL.log

https://tricorder.pi-hole.net/J6e1R7z6/

3

Thanks for bringing this up, it will be fixed by

https://github.com/pi-hole/FTL/pull/2163

Further background if you are interested:

This is a (harmless) side-effect of the combination of two PRs:

https://github.com/pi-hole/FTL/pull/2130

and the later merged

https://github.com/pi-hole/FTL/pull/2125

Each PR on its own didn't show the issue, only the combination revealed it. It happens whenever the internal name resolution of an IPv6-connected device within your local network was postponed to increase the likeliness that we are able to infer its name from the network table if no name is provided by the device itself (commonly happens especially with mobile devices spoofing their MAC addresses for "privacy" reasons).

The FTL code handling locks is self-defensive and knows that this is an error to unlock a lock that has already been unlocked before so no harm is caused and your Pi-holes operate as usual.

1 Like
4

Thanks! Working great!

5

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.