You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
==> 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.
To Reproduce
On you user profile in uptime-kuma select "Settings"
Ensure that you have the option: "Enable NSCD (Name Service Cache Daemon) for caching all DNS requests" enabled
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.
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]
The text was updated successfully, but these errors were encountered:
Closing as SCALE isnt a supported platform any longer. Feel free to open a new Issue if the issue persists on one of the currently supported platforms.
chart Name
uptime-kuma
Operating System
TrueNAS SCALE 24.04.0
Deployment Method
TrueNAS SCALE charts
Chart Version
10.8.16
Kubernetes Events
chartlication Logs
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.
To Reproduce
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
[Chart-Name]
The text was updated successfully, but these errors were encountered: