Winlogbeat fails to Start when deployed using Salt
Open
Nobody has claimed this yet.
bug
severity-high
Windows
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
While deployment of Winlogbeat seems fine within Salt, and installed the module within the Windows Servers it fails to start the service
Setup
copy_files:
file.recurse:
- source: salt://sent/winlog/
- name: C:\Program Files\Winlogbeat\
- makedirs: true
run_install:
cmd.run:
- name: '.\install-service-winlogbeat.ps1'
- shell: powershell
- cwd: C:\Program Files\Winlogbeat
run_install1:
cmd.run:
- name: '.\winlogbeat.exe setup'
- cwd: C:\Program Files\Winlogbeat
Start:
cmd.run:
- name: 'Start-Service winlogbeat'
- shell: powershell
Steps to Reproduce Issue
(Include debug logs if possible and relevant.)
Versions Report
root@salt:/srv/salt# salt --versions-report
Salt Version:
Salt: 2019.2.0
Dependency Versions:
cffi: Not Installed
cherrypy: unknown
dateutil: 2.6.1
docker-py: 3.7.0
gitdb: 2.0.3
gitpython: 2.1.8
ioflo: Not Installed
Jinja2: 2.10
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: 1.0.7
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 2.7.15+ (default, Nov 27 2018, 23:36:35)
python-gnupg: 0.4.1
PyYAML: 3.12
PyZMQ: 16.0.2
RAET: Not Installed
smmap: 2.0.3
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.2.5
System Versions:
dist: Ubuntu 18.04 bionic
locale: UTF-8
machine: x86_64
release: 4.15.0-1032-aws
system: Linux
version: Ubuntu 18.04 bionic
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Salt state using the reported Salt 2019.2.0, Ubuntu 18.04 controller, and Windows target. Inspect the commands involving install-service-winlogbeat.ps1, winlogbeat.exe setup, and Start-Service winlogbeat, then capture the missing service-start error or debug output. Done means the same deployment completes and the Winlogbeat service starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, python
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100