# Bug: Ec2 process access error - causing silent failure

**URL:** <https://discuss.elastic.co/t/bug-ec2-process-access-error-causing-silent-failure/168128>\
**Category:** Beats\
**Created:** [February 12, 2019, 11:57pm UTC](https://discuss.elastic.co/t/bug-ec2-process-access-error-causing-silent-failure/168128 "2019-02-12T23:57:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ensemblebd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ensemblebd/32/120119_2.png) [@ensemblebd](https://discuss.elastic.co/u/ensemblebd)\
**Post date:** [February 12, 2019, 11:57pm UTC](https://discuss.elastic.co/t/bug-ec2-process-access-error-causing-silent-failure/168128/1 "2019-02-12T23:57:51Z")

</div>

On windows, the **wininit.exe** process can't be accessed by the service (some machines .. EC2 specifically with DataCenter edition 2016 server), which can only be detected by turning on debug logging.  
Logs look totally normal (other than lack of json post ops), but elastisearch shows nothing except the very first poll operation.. system goes totally silent.

Disabling the **process** metricset[s] within **system** module resumes normal data dispatch routine.

Took a solid hour or so to figure this out.  
Figured someone should know about it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 13, 2019, 1:57am UTC](https://discuss.elastic.co/t/bug-ec2-process-access-error-causing-silent-failure/168128/2 "2019-03-13T01:57:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.