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

[uptime-kuma] nscd for DNS caching is not starting #21434

Open
2 tasks done
georg-lam opened this issue Apr 27, 2024 · 0 comments
Open
2 tasks done

[uptime-kuma] nscd for DNS caching is not starting #21434

georg-lam opened this issue Apr 27, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@georg-lam
Copy link

chart Name

uptime-kuma

Operating System

TrueNAS SCALE 24.04.0

Deployment Method

TrueNAS SCALE charts

Chart Version

10.8.16

Kubernetes Events

No events are available.

chartlication Logs

==> Performing startup jobs and maintenance tasks
==> Starting application with user 568 group 568
Welcome to Uptime Kuma
Your Node.js version: 18.20.2
2024-04-27T11:38:42+02:00 [SERVER] INFO: Welcome to Uptime Kuma
2024-04-27T11:38:42+02:00 [SERVER] INFO: Node Env: production
2024-04-27T11:38:42+02:00 [SERVER] INFO: Inside Container: true
2024-04-27T11:38:42+02:00 [SERVER] INFO: Importing Node libraries
2024-04-27T11:38:42+02:00 [SERVER] INFO: Importing 3rd-party libraries
2024-04-27T11:38:45+02:00 [SERVER] INFO: Creating express and socket.io instance
2024-04-27T11:38:45+02:00 [SERVER] INFO: Server Type: HTTP
2024-04-27T11:38:45+02:00 [SERVER] INFO: Importing this project modules
2024-04-27T11:38:45+02:00 [NOTIFICATION] INFO: Prepare Notification Providers
2024-04-27T11:38:45+02:00 [SERVER] INFO: Version: 1.23.13
2024-04-27T11:38:45+02:00 [DB] INFO: Data Dir: ./data/
2024-04-27T11:38:45+02:00 [SERVER] INFO: Connecting to the Database
2024-04-27T11:38:45+02:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2024-04-27T11:38:45+02:00 [DB] INFO: SQLite Version: 3.41.1
2024-04-27T11:38:45+02:00 [SERVER] INFO: Connected
2024-04-27T11:38:45+02:00 [DB] INFO: Your database version: 10
2024-04-27T11:38:45+02:00 [DB] INFO: Latest database version: 10
2024-04-27T11:38:45+02:00 [DB] INFO: Database patch not needed
2024-04-27T11:38:45+02:00 [DB] INFO: Database Patch 2.0 Process
2024-04-27T11:38:45+02:00 [SERVER] INFO: Load JWT secret from database.
2024-04-27T11:38:45+02:00 [MAINTENANCE] INFO: Maintenance id: 3 is under maintenance now
2024-04-27T11:38:45+02:00 [SERVER] INFO: Adding route
2024-04-27T11:38:45+02:00 [SERVER] INFO: Adding socket handler
2024-04-27T11:38:45+02:00 [SERVER] INFO: Init the server
2024-04-27T11:38:45+02:00 [SERVER] INFO: Listening on 3001
2024-04-27T11:38:45+02:00 [SERVICES] INFO: Starting nscd
2024-04-27T11:38:45+02:00 [SERVICES] INFO: Failed to start nscd

Chart Configuration

nothing special. I enabled ingress/traefik with certificate. This is working. no problem here.

Describe the bug

In the GUI of uptime kuma you can enable nscd (a service to cache DNS requests). I noticed that requests are not cached because I see too many requests on my nameserver (AdGuard Home).

In the pod I see that there is a problem with nscd. First the log shows that nscd did not start. When I start it manually it also fails due to a permission problem. See screenshots attached.

Screenshot 2024-04-27 120904
Screenshot 2024-04-27 120953

To Reproduce

  1. On you user profile in uptime-kuma select "Settings"
  2. Ensure that you have the option: "Enable NSCD (Name Service Cache Daemon) for caching all DNS requests" enabled
  3. Log into the pod and try to rund nscd -g to get some statistics from the daemon. -> this will fail as the daemon is not starting.
  4. When you start the daemon manually with "nscd --debug" you see that it cannot start due to a permission problem:
    it cannot create the /var/cache/nscd/hosts as it is a read-only file system.
    (This is probably the root cause).

Expected Behavior

When you enable NSCD in the GUI then you expect that this daemon starts and caches some of the DNS requests.

Screenshots

n/a

Additional Context

n/a

I've read and agree with the following

  • I've checked all open and closed issues and my issue is not there.
  • I've prefixed my issue title with [Chart-Name]
@georg-lam georg-lam added the bug Something isn't working label Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant