-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Windows Service results in no log output #1786
Labels
bug
unexpected problem or unintended behavior
help wanted
Request for community participation, code, contribution
platform/windows
Comments
sparrc
added a commit
that referenced
this issue
Oct 3, 2016
in this commit: - centralize logging output handler. - set global Info/Debug/Error log levels based on config file or flags. - remove per-plugin debug arg handling. - add a I!, D!, or E! to every log message. - add configuration option to specify where to send logs. closes #1786
sparrc
added a commit
that referenced
this issue
Oct 3, 2016
in this commit: - centralize logging output handler. - set global Info/Debug/Error log levels based on config file or flags. - remove per-plugin debug arg handling. - add a I!, D!, or E! to every log message. - add configuration option to specify where to send logs. closes #1786
sparrc
added a commit
that referenced
this issue
Oct 3, 2016
in this commit: - centralize logging output handler. - set global Info/Debug/Error log levels based on config file or flags. - remove per-plugin debug arg handling. - add a I!, D!, or E! to every log message. - add configuration option to specify where to send logs. closes #1786
jackzampolin
pushed a commit
that referenced
this issue
Oct 7, 2016
in this commit: - centralize logging output handler. - set global Info/Debug/Error log levels based on config file or flags. - remove per-plugin debug arg handling. - add a I!, D!, or E! to every log message. - add configuration option to specify where to send logs. closes #1786
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
unexpected problem or unintended behavior
help wanted
Request for community participation, code, contribution
platform/windows
Bug report
System info:
Steps to reproduce:
Install the Windows service and then run it, there is no log output provided in files or the event log.
Expected behavior:
Log some output from the telegraf process
Actual behavior:
Nothing logged anywhere
Additional info:
In the old days of using the nssm wrapped approach, you could just redirect the stdout and stderr to a file, which worked fine.
Now that the service is being run using the Go service libraries, you probably have to utilize the event log and/or some log file output that captures the stdout/stderr differently under Windows.
The text was updated successfully, but these errors were encountered: