bakito / adguardhome-sync

πŸ›‘οΈ Synchronize AdGuard Home config to replicas
Apache License 2.0
923 stars 37 forks source link

Web API server takes long to come up and show the log #351

Closed iptvcld closed 3 months ago

iptvcld commented 5 months ago

What happened?

Installed latest on unRaid on default port 8080 - when i try to bring the webUI up, it take around 45 seconds to come up

AdguardHome-Sync Version

Latest

AdguardHome Version

Latest

Configuration

Installed latest on unRaid on default port 8080 - when i try to bring the webUI up, it take around 45 seconds to come up

Current Applied Configuration

# cron expression to run in daemon mode. (default; "" = runs only once)
cron: "*/10 * * * *"

origin:
  # url of the origin instance
  url: http://10.200.1.60
  # apiPath: define an api path if other than "/control"
  insecureSkipVerify: true # disable tls check
  username: root
  password: ####

# replica instance (optional, if only one)
replica:
  # url of the replica instance
  url: http://10.200.1.61
  username: username
  password: password

# Configure the sync API server, disabled if api port is 0
api:
  # Port, default 8080
  port: 8080
  # if username and password are defined, basic auth is applied to the sync API
  username: root
  password: ####

Relevant log output

Linuxserver.io version: v0.6.11-ls104
Build-date: 2024-05-28T19:22:56+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.
2024-05-31T00:53:39.145-0400    INFO    sync    sync/sync.go:38 AdGuardHome sync        {"version": "0.6.11", "build": "2024-05-25T06:15:56Z", "os": "linux", "arch": "amd64"}
2024-05-31T00:53:39.145-0400    INFO    sync    sync/sync.go:65 Setup cronjob   {"cron": "*/10 * * * *", "next-execution": "2024-05-31T01:00:00.000-0400"}
2024-05-31T00:53:39.145-0400    INFO    sync    sync/http.go:68 Starting API server     {"port": 8080}
2024-05-31T00:53:39.145-0400    INFO    sync    sync/sync.go:75 Running sync on startup
2024-05-31T00:53:39.186-0400    INFO    sync    sync/sync.go:174        Connected to origin     {"from": "10.200.1.60", "version": "v0.107.50"}

Anything else?

No response

bakito commented 5 months ago

It might be an issue with low resources (CPU) on your container. An the application is not much that could be done here.