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.

Sign up for GitHub

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

Jump to bottom

System log on macOS doesn't receive messages #3

Open
4 tasks done
EugeneOne1 opened this issue Jul 8, 2024 · 2 comments
Open
4 tasks done

System log on macOS doesn't receive messages #3

EugeneOne1 opened this issue Jul 8, 2024 · 2 comments
Assignees
@EugeneOne1
Labels
bug Something isn't working external-dependencies An external dependency is causing the issue
Milestone
v0.1.0

Comments

@EugeneOne1
Copy link
Member

EugeneOne1 commented Jul 8, 2024 •
edited
Loading

Prerequisites

  • I have checked the Knowledge Base and the Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to report a bug and not ask a question or ask for help

  • I have set up AdGuard DNS Clients correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Darwin (aka macOS), AMD64 (aka x86_64)

Installation

GitHub releases

Setup

On a personal machine

AdGuard DNS Client version

v0.0.1

Action

Without any configuration run:

cd /Applications/AdGuardDNSClient
sudo env LOG_OUTPUT=syslog ./AdGuardDNSClient

Expected result

An error message in the Console app:

level=ERROR msg="fatal error" err="parsing configuration: open /Applications/AdGuardDNSClient/config.yaml: no such file or directory"

Actual result

No mentions of AdGuardDNSClient process.

Additional information and/or screenshots

May be related to golang/go#59229.
@EugeneOne1 EugeneOne1 added the bug Something isn't working label Jul 8, 2024
@EugeneOne1 EugeneOne1 added this to the v0.0.2 milestone Jul 8, 2024
@EugeneOne1 EugeneOne1 self-assigned this Jul 8, 2024
@ainar-g ainar-g added the external-dependencies An external dependency is causing the issue label Jul 8, 2024
@ainar-g ainar-g modified the milestones: v0.0.2, v0.1.0 Jul 8, 2024
@ainar-g
Copy link
Contributor

ainar-g commented Jul 8, 2024

Both workarounds are quite suboptimal. Rescheduling to v0.1.0. Perhaps we'll figure something out by then.

adguard pushed a commit that referenced this issue Jul 22, 2024
@EugeneOne1
Pull request 60: 3 darwin syslog
a51b997 
Updates #3.

Squashed commit of the following:

commit d7f07af
Author: Eugene Burkov <[email protected]>
Date:   Thu Jul 18 14:48:34 2024 +0300

    agdcslog: imp code

commit 4c4abd7
Author: Eugene Burkov <[email protected]>
Date:   Wed Jul 17 19:45:27 2024 +0300

    agdcslog: fix panic

commit 3b2c62a
Author: Eugene Burkov <[email protected]>
Date:   Wed Jul 17 19:34:37 2024 +0300

    agdcslog: imp code, docs

commit 39a9e61
Author: Eugene Burkov <[email protected]>
Date:   Wed Jul 17 17:48:34 2024 +0300

    all: implement piped logger on darwin
@EugeneOne1
Copy link
Member Author

EugeneOne1 commented Jul 22, 2024 •
edited
Loading

As per a51b997, we've implemented logging to the system logger via the /usr/bin/logger utility. This issue will remain open until the mentioned Go issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EugeneOne1 EugeneOne1

Labels
bug Something isn't working external-dependencies An external dependency is causing the issue
Projects
None yet
Milestone
v0.1.0
Development

No branches or pull requests
2 participants
@ainar-g @EugeneOne1