-
Notifications
You must be signed in to change notification settings - Fork 36
Description
What happened?
I have re-organized my piholes and added some more. It worked for a little bit but then started failing again. I have tried recreating nebula-sync but it is just unable to invalidate sessions so they stack up until full.
2025-12-24T11:17:25-06:00 INF Invalidating sessions... 2025-12-24T11:17:27-06:00 WRN Failed to invalidate session for target: http://172.16.8.250 2025-12-24T11:17:29-06:00 WRN Failed to invalidate session for target: http://pihole1-1.pihole1-headless.pihole.svc.cluster.local 2025-12-24T11:17:31-06:00 WRN Failed to invalidate session for target: http://pihole2-0.pihole2-headless.pihole.svc.cluster.local 2025-12-24T11:17:33-06:00 WRN Failed to invalidate session for target: http://pihole2-1.pihole2-headless.pihole.svc.cluster.local 2025-12-24T11:17:33-06:00 FTL Sync failed error="authenticate: http://172.16.8.250/api/auth: unexpected status code: 429"
Expected Behaviour
It should successfully invalidate or somehow wipe out existing sessions so they do not fill up.
Nebula-sync Version
v0.11.1
Runtime
docker
Operating System
pi os bullseye
CPU Architecture
arm64
Configuration
apiVersion: v1
kind: ConfigMap
metadata:
name: nebula-sync-config
namespace: pihole
data:
PRIMARY: 'http://pihole1-0.pihole1-headless.pihole.svc.cluster.local|[REDACTED]'
REPLICAS: 'http://172.16.8.250|[REDACTED],http://pihole1-1.pihole1-headless.pihole.svc.cluster.local|[REDACTED],http://pihole2-0.pihole2-headless.pihole.svc.cluster.local|[REDACTED],http://pihole2-1.pihole2-headless.pihole.svc.cluster.local|[REDACTED]'
FULL_SYNC: 'true'
RUN_GRAVITY: 'false'
CRON: '*/10 * * * *'
CLIENT_SKIP_TLS_VERIFICATION: 'true'
TZ: 'America/Chicago'Relevant log output
2025-12-24T11:24:36-06:00 INF Starting nebula-sync v0.11.1
2025-12-24T11:24:36-06:00 INF Running sync mode=full replicas=4
2025-12-24T11:24:36-06:00 INF Authenticating clients...
2025-12-24T11:24:45-06:00 INF Invalidating sessions...
2025-12-24T11:24:47-06:00 WRN Failed to invalidate session for target: http://172.16.8.250
2025-12-24T11:24:49-06:00 WRN Failed to invalidate session for target: http://pihole1-1.pihole1-headless.pihole.svc.cluster.local
2025-12-24T11:24:51-06:00 WRN Failed to invalidate session for target: http://pihole2-0.pihole2-headless.pihole.svc.cluster.local
2025-12-24T11:24:53-06:00 WRN Failed to invalidate session for target: http://pihole2-1.pihole2-headless.pihole.svc.cluster.local
2025-12-24T11:24:53-06:00 FTL Sync failed error="authenticate: http://172.16.8.250/api/auth: unexpected status code: 429"Pi-hole Version
Docker Tag 2025.11.1Core v6.3FTL v6.4.1Web interface v6.4