adguardhome-sync: 0.6.0: Error syncing DHCP server config
What happened?
After updating from version 0.5.4 to 0.6.0 I see this error.
Rolling back doesn’t show this error.
AdguardHome-Sync Version
0.6.0
AdguardHome Version
v0.107.43
Configuration
# cron expression to run in daemon mode. (default; "" = runs only once)
cron: "*/10 * * * *"
# runs the synchronisation on startup
runOnStart: true
origin:
# url of the origin instance
url: http://redacted:8085
# apiPath: define an api path if other than "/control"
insecureSkipVerify: true # disable tls check
username: redacted
password: redacted
# replica instance (optional, if only one)
replica:
# url of the replica instance
url: http://redacted:8085
username: redacted
password: redacted
# 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: username
# password: password
# Configure sync features; by default all features are enabled.
# features:
# generalSettings: true
# queryLogConfig: true
# statsConfig: true
# clientSettings: true
# services: true
# filters: true
# dhcp:
# serverConfig: true
# staticLeases: true
# dns:
# serverConfig: true
# accessLists: true
# rewrites: true
Relevant log output
2024-01-12T18:36:16.790+0100 INFO root cmd/root.go:119 Using config file:/config/adguardhome-sync.yaml
2024-01-12T18:36:16.806+0100 INFO sync sync/sync.go:38 AdGuardHome sync {"version": "v0.6.0", "build": "2024-01-10T18:53:37Z", "os": "linux", "arch": "arm64"}
2024-01-12T18:36:16.808+0100 INFO sync sync/sync.go:65 Setup cronjob {"cron": "*/10 * * * *", "next-execution": "2024-01-12T18:40:00.000+0100"}
2024-01-12T18:36:16.809+0100 INFO sync sync/sync.go:75 Running sync on startup
2024-01-12T18:36:16.810+0100 INFO sync sync/http.go:57 Starting API server {"port": 8080}
2024-01-12T18:36:16.827+0100 INFO sync sync/sync.go:172 Connected to origin {"from": "redacted:8085", "version": "v0.107.43"}
2024-01-12T18:36:16.920+0100 INFO sync sync/sync.go:271 Start sync {"from": "redacted:8085", "to": ""}
2024-01-12T18:36:17.396+0100 INFO sync sync/sync.go:279 Connected to replica {"from": "redacted:8085", "to": "", "version": "v0.107.43"}
2024-01-12T18:36:19.807+0100 INFO client client/client.go:337 Set stats config {"host": "", "interval": 7}
2024-01-12T18:36:20.262+0100 INFO client client/client.go:269 Toggle filtering {"host": "", "enabled": true, "interval": 24}
2024-01-12T18:36:21.348+0100 INFO client client/client.go:396 Set dhcp server config {"host": ""}
2024-01-12T18:36:21.505+0100 ERROR sync sync/sync.go:300 Error syncing DHCP server config {"from": "redacted:8085", "to": "", "error": "400 Bad Request(bad dhcpv4 configuration: dhcpv4: invalid IP is not an IPv4 address\n)"}
github.com/bakito/adguardhome-sync/pkg/sync.(*worker).syncTo
/go/src/app/pkg/sync/sync.go:300
github.com/bakito/adguardhome-sync/pkg/sync.(*worker).sync
/go/src/app/pkg/sync/sync.go:259
github.com/bakito/adguardhome-sync/pkg/sync.Sync.func3
/go/src/app/pkg/sync/sync.go:76
Anything else?
In the log, some to and host seem to be empty.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (16 by maintainers)
Commits related to this issue
- correct config issues #271 #272 — committed to bakito/adguardhome-sync by bakito 3 years ago
- Fix config issues with new env library (#273) * correct config issues #271 #272 * rename type tags * replace env lib * move to config module * read flags * show e2e logs on error * ... — committed to bakito/adguardhome-sync by bakito 3 years ago
- #272 do not sync dhcp if empty IP — committed to bakito/adguardhome-sync by bakito 3 years ago
- extend dhcp checks #272 — committed to bakito/adguardhome-sync by bakito 3 years ago
- add tests #272 — committed to bakito/adguardhome-sync by bakito 3 years ago
The main looks good, with no errors. Thanks!