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

Error when upgrading from 0.5.4 to 0.6.2 #281

Closed
tapufd opened this issue Jan 17, 2024 · 6 comments
Closed

Error when upgrading from 0.5.4 to 0.6.2 #281

tapufd opened this issue Jan 17, 2024 · 6 comments

Comments

@tapufd
Copy link

tapufd commented Jan 17, 2024

What happened?

Using in docker a config-file -> CONFIGFILE=/config/adguardhome-sync.yaml
All works in v0.5.4, but when upgrading my docker image to v0.6.2, adguardhome-sync doesn't start.
See attached log-file...
_adguardhome-sync_logs.txt

AdguardHome-Sync Version

current = 0.5.4
target = 0.6.2

AdguardHome Version

v0.107.43

Configuration

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

# runs the synchronisation on startup
runOnStart: false

origin:
  # url of the origin instance
  url: https://192.168.1.2:3443
  # apiPath: define an api path if other than "/control"
  insecureSkipVerify: true # disable tls check
  username: xxx
  password: 'xxx'

# replica instance (optional, if only one)
replica:
  # url of the replica instance
  url: https://192.168.1.3:3443
  # apiPath: define an api path if other than "/control"
  insecureSkipVerify: true # disable tls check
  username: xxx
  password: 'xxx'
  interfaceName: eth0
  dhcpServerEnabled: false

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

# 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

See attached log...

Anything else?

No response

@bakito
Copy link
Owner

bakito commented Jan 17, 2024

Hi @tapufd

Can you please switch to array replicas config for now?

# replicas instances
replicas:
  - url: http://192.168.1.3
    username: username
    password: password

@bakito
Copy link
Owner

bakito commented Jan 17, 2024

Update, the issue seems to be with dhcpServerEnabled: false it also happens wit array config.

@tapufd
Copy link
Author

tapufd commented Jan 17, 2024

Seems I already was using the "array replicas" notation.

bakito added a commit that referenced this issue Jan 17, 2024
* switch to go.uber.org/mock

* #281 special handling for dhcpServerEnabled
@bakito
Copy link
Owner

bakito commented Jan 17, 2024

@tapufd can you try the newest main image and check if the issue is solved?
https://github.com/bakito/adguardhome-sync/pkgs/container/adguardhome-sync/168115720?tag=main

@tapufd
Copy link
Author

tapufd commented Jan 18, 2024

Hi, tested the latest main image/pkg ghcr.io/bakito/adguardhome-sync:main and that one works.
Did a sync, and all seems to be working.
Thx!

@bakito
Copy link
Owner

bakito commented Jan 18, 2024

@bakito bakito closed this as completed Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants