xigmanas: AdGuardHome# ls
AdGuardHome AdGuardHome.yaml data README.md
AdGuardHome.sig CHANGELOG.md LICENSE.txt
xigmanas: AdGuardHome# ./AdGuardHome
2024/11/03 13:16:48.668458 [info] AdGuard Home, version v0.107.53
2024/11/03 13:16:48.669733 [info] tls: using default ciphers
2024/11/03 13:16:48.672171 [info] safesearch default: disabled
2024/11/03 13:16:49.282924 [info] Initializing auth module: /mnt/pool/downloads/opt/AdGuardHome/data/sessions.db
^C2024/11/03 13:16:51.625911 [info] Received signal "interrupt"
2024/11/03 13:16:51.625926 [info] stopping AdGuard Home
2024/11/03 13:16:51.625968 [info] stopped
^C2024/11/03 13:16:54.688728 [info] Received signal "interrupt"
2024/11/03 13:16:54.688749 [info] stopping AdGuard Home
panic: close of closed channel
goroutine 33 [running]:
github.com/AdguardTeam/AdGuardHome/internal/aghnet.(*HostsContainer).Close(0x86c31e000)
github.com/AdguardTeam/AdGuardHome/internal/aghnet/hostscontainer.go:108 +0x128
github.com/AdguardTeam/AdGuardHome/internal/home.cleanup({0x1a5c010?, 0x26586e0?})
github.com/AdguardTeam/AdGuardHome/internal/home/home.go:862 +0x1bc
github.com/AdguardTeam/AdGuardHome/internal/home.Main.func1()
github.com/AdguardTeam/AdGuardHome/internal/home/home.go:126 +0x112
created by github.com/AdguardTeam/AdGuardHome/internal/home.Main in goroutine 1
github.com/AdguardTeam/AdGuardHome/internal/home/home.go:117 +0x298
xigmanas: AdGuardHome#
6. Run *AdguardHome* as service.
```sh
xigmanas: AdGuardHome# ./AdGuardHome -s start
2024/11/03 13:22:57 [info] AdGuard Home, version v0.107.53
2024/11/03 13:22:57 [info] service: control action: start
2024/11/03 13:22:57 [fatal] service: executing action "start": Failed to start AdGuard Home service: exit status 1
Expected result
no panic
Actual result
panic
Additional information and/or screenshots
Previously, running it as a service worked fine, but recently, after a power outage, I tried to manually restart AdguardHome and encountered these issues. Of course, it could be due to my lack of familiarity with FreeBSD, but the panic is undoubtedly a BUG.
Prerequisites
[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to report a bug and not ask a question or ask for help
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
FreeBSD, AMD64 (aka x86_64)
Installation
GitHub releases or script from README
Setup
Other (please mention in the description)
AdGuard Home version
AdGuard Home, version v0.107.53
Action
Crtl+C
, get a stopped info, but freeze.Ctrl+C
again, get a panic.xigmanas: AdGuardHome# ./AdGuardHome 2024/11/03 13:16:48.668458 [info] AdGuard Home, version v0.107.53 2024/11/03 13:16:48.669733 [info] tls: using default ciphers 2024/11/03 13:16:48.672171 [info] safesearch default: disabled 2024/11/03 13:16:49.282924 [info] Initializing auth module: /mnt/pool/downloads/opt/AdGuardHome/data/sessions.db ^C2024/11/03 13:16:51.625911 [info] Received signal "interrupt" 2024/11/03 13:16:51.625926 [info] stopping AdGuard Home 2024/11/03 13:16:51.625968 [info] stopped ^C2024/11/03 13:16:54.688728 [info] Received signal "interrupt" 2024/11/03 13:16:54.688749 [info] stopping AdGuard Home panic: close of closed channel
goroutine 33 [running]: github.com/AdguardTeam/AdGuardHome/internal/aghnet.(*HostsContainer).Close(0x86c31e000) github.com/AdguardTeam/AdGuardHome/internal/aghnet/hostscontainer.go:108 +0x128 github.com/AdguardTeam/AdGuardHome/internal/home.cleanup({0x1a5c010?, 0x26586e0?}) github.com/AdguardTeam/AdGuardHome/internal/home/home.go:862 +0x1bc github.com/AdguardTeam/AdGuardHome/internal/home.Main.func1() github.com/AdguardTeam/AdGuardHome/internal/home/home.go:126 +0x112 created by github.com/AdguardTeam/AdGuardHome/internal/home.Main in goroutine 1 github.com/AdguardTeam/AdGuardHome/internal/home/home.go:117 +0x298 xigmanas: AdGuardHome#
Expected result
no panic
Actual result
panic
Additional information and/or screenshots
Previously, running it as a service worked fine, but recently, after a power outage, I tried to manually restart AdguardHome and encountered these issues. Of course, it could be due to my lack of familiarity with FreeBSD, but the panic is undoubtedly a BUG.