-
Notifications
You must be signed in to change notification settings - Fork 685
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 winrm: cannot install using internal install method #72
Comments
Does winrm and Ansible have full admin rights? It sounds like a fine grain On Wed, Sep 14, 2016, 02:57 Cameron Sparr notifications@github.com wrote:
|
That's a good question, @one1zero1one any idea if this could just be a permissions issue? I'm not very familiar with the stack, but maybe there is a way to give ansible heightened permissions for this operation. |
Ansible connects to the host via winrm - with the same user (local admin). No issues otherwise, session is running elevated:
however when running telegraf:
no out, no err, just the eventID 3 in eventlog. |
@one1zero1one Please try to install telegraf.exe by using the windows provided tool "sc.exe" under winrm. If sc works and the internal install fails, then it is a Having the windows role Administrator does not guarantee the appropriate rights. |
@kardianos thanks for the suggestion, sc.exe seems to do the job, both in console and under winrm. Internal install works only from console, fails from winrm. |
@one1zero1one Feel free to use sc.exe for now to install telegraf in your deployments. I'll need to examine what can be done differently for both methods to work. |
When installing a windows service via WinRM (via ansible), we get an error saying that "The service process could not connect to the service controller."
This was originally reported in Telegraf: influxdata/telegraf#1760
and here is the issue text:
System info:
Win2012R2
Steps to reproduce:
Running in powershell/console works OK (both interactive and installing the service)
Deploying via winrm (ansible) on the same box rc:0, no stdout or stderr output + eventlog error.
Expected behavior:
installing/running telegraf
rc:0, stderr NOT "" and/or stdout NOT "" and no eventID
Actual behavior:
"rc": 0, "stderr": "", "stdout": "", "stdout_lines": [] + eventID:3 "The service process could not connect to the service controller."
Use case:
testing telegraf on windows works fine, mass-deploying it using ansible (or any other deployment method that uses winrm) doesn't, and this is a blocker for using telegraf on windows.
The text was updated successfully, but these errors were encountered: