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

Add logging to /var/log/AdGuardHome.err on FreeBSD and OpenBSD #4213

Closed
ainar-g opened this issue Jan 26, 2022 · 6 comments
Closed

Add logging to /var/log/AdGuardHome.err on FreeBSD and OpenBSD #4213

ainar-g opened this issue Jan 26, 2022 · 6 comments

Comments

@ainar-g
Copy link
Contributor

ainar-g commented Jan 26, 2022

Just like on macOS and Linux, let's write stderr and stdout to /var/log/AdGuardHome.err and AdGuardHome.out correspondingly.

@ainar-g ainar-g added this to the v0.108.0 milestone Jan 26, 2022
@ainar-g ainar-g self-assigned this Jan 26, 2022
@cookiemonsteruk
Copy link

I don't doubt that there are issues with higher priority but all *bsd users are unable to diagnose problems with Adguard and often have no choice but to give up or use an alternative in search of the lofty goals Adguard has. That is a good chunk of proficient users with *bsd-based firewalls.
I would very much like to see some logging to be made available.

@ainar-g
Copy link
Contributor Author

ainar-g commented Feb 11, 2022

@cookiemonsteruk, we'll bump the priority, thanks. You can already make it write logs by filling in the log_file parameter in AdGuardHome.yaml, but the default behaviour obviously has to be changed.

@cookiemonsteruk
Copy link

Well that is wonderful, thank you @ainar-g
I also didn't know of this logging possibility I'll set it up now. Is it a value pair i.e.
log_file /var/log/adguard.log

@cookiemonsteruk
Copy link

And are there logging level directives available like INFO, ERROR, DEBUG, etc?

@ainar-g
Copy link
Contributor Author

ainar-g commented Feb 11, 2022

@cookiemonsteruk, the default level is info and debug is enabled through the verbose parameter. Please see our documentation. Also, it's better to keep the Q&A in the Discussions. Thanks.

@cookiemonsteruk
Copy link

Understood, thank you.

@ainar-g ainar-g modified the milestones: v0.108.0, v0.107.7 Jun 2, 2022
adguard pushed a commit that referenced this issue Jun 2, 2022
Merge in DNS/adguard-home from 4213-bsd-syslog to master

Updates #4046.
Closes #4213.

Squashed commit of the following:

commit 1e57c75
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 16:20:32 2022 +0300

    home: imp error msg

commit 63059d0
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 15:36:37 2022 +0300

    all: imp log of changes

commit 682c3c9
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 15:29:29 2022 +0300

    home: imp code

commit 86c311a
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 15:03:02 2022 +0300

    home: add bsd syslog
heyxkhoa pushed a commit to heyxkhoa/AdGuardHome that referenced this issue Mar 20, 2023
Merge in DNS/adguard-home from 4213-bsd-syslog to master

Updates AdguardTeam#4046.
Closes AdguardTeam#4213.

Squashed commit of the following:

commit 1e57c75
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 16:20:32 2022 +0300

    home: imp error msg

commit 63059d0
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 15:36:37 2022 +0300

    all: imp log of changes

commit 682c3c9
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 15:29:29 2022 +0300

    home: imp code

commit 86c311a
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Feb 28 15:03:02 2022 +0300

    home: add bsd syslog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants