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

[Bug]: Windows application event log has the same Event ID (0) for all netclient events #2818

Open
1 task done
unquietwiki opened this issue Feb 9, 2024 · 3 comments
Open
1 task done
Assignees
Labels
bug Something isn't working

Comments

@unquietwiki
Copy link

Contact Details

[email protected]

What happened?

I was trying to write a Task Scheduler event to remap DNS whenever netclient restarts, or does a pull. However, all the event log IDs are 0, meaning that the DNS will be set against an unstable adapter entry. Having specific event log IDs for connections and disconnections would be helpful for this, and for debugging in general. Thanks!

Version

v0.22.0

What OS are you using?

Windows

Relevant log output

No response

Contributing guidelines

  • Yes, I did.
@unquietwiki unquietwiki added the bug Something isn't working label Feb 9, 2024
@unquietwiki
Copy link
Author

I found one workaround for determining when the network's been reset: an Time Service event 37 gets triggered whenever the network changes; at least for machines on a domain.

@yabinma
Copy link
Collaborator

yabinma commented Mar 2, 2024

@unquietwiki , currently Windows client does not manage the service by itself, but it's delegated to Winsw. The event log(start, stop) is written by Winsw, not by netclient code. I raised a git issue winsw/winsw#1078 let's see if it's possible to improve in Winsw level.

@unquietwiki
Copy link
Author

Thank you @yabinma for looking into this, and opening that request. It's appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants