# Elastic Synthetics Journey: Receiving \`permission denied\`

**URL:** https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032
**Category:** Synthetics
**Tags:** docker
**Created:** [April 14, 2023, 5:05pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032 "2023-04-14T17:05:31Z")
**Posts on this page:** 9
**Page:** 2

<div class="post-metadata">

### Author: ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)
#### Post date: [May 8, 2023, 6:44pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/21 "2023-05-08T18:44:34Z")

</div>

> [@emilioalvap](#):
>
> Could you check under what user and capabilities `heartbeat` process is running? What does the env variable `BEAT_SETUID_AS` evaluate to inside the container?

This evaluates to `elastic-agent`.

> We have mechanisms in place to prevent running browser monitors as a root user which are probably interfering here. FYI, we have introduced a new approach on `8.7.1`.

I just updated to `8.7.1` today. However, in checking my tests, there don't seem to be any changes. I'm still receiving the same results.

> We have had issues with around mitigations in place to prevent running browser monitors under root. A new approach was implemented on 8.7.0 (not 8.7.1, as I thought) which impacts `push` monitors and other deprecated types. Since we generally recommend not running containers as root, this issue will impact ECK users mostly.

A quick question. You write "...`push` monitors and other deprecated types." Have `push` monitors been deprecated?

---

<div class="post-metadata">

### Author: ![shahzad31](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shahzad31/32/51637_2.png) [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [May 8, 2023, 8:16pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/22 "2023-05-08T20:16:51Z")

</div>

@DougR Rest of the things @emilioalvap can better answer but we are no way deprecating Push monitors 🙂

---

<div class="post-metadata">

### Author: ![emilioalvap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emilioalvap/32/99310_2.png) [@emilioalvap](https://discuss.elastic.co/u/emilioalvap)
#### Post date: [May 9, 2023, 10:09am UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/23 "2023-05-09T10:09:07Z")

</div>

Hi @DougR,

As @shahzad31 very kindly mentioned, **push monitors and their related features are not deprecated**.

What I meant to say is: other monitor types (mainly zip url and local), which are already [deprecated](https://www.elastic.co/guide/en/beats/heartbeat/current/monitor-browser-options.html#monitor-source-zipurl), are _also_ impacted. I should have used better wording on my previous comment, sorry about the confusion.

On the other topics:

- Yes, I initially thought `8.7.1` was the version that came with permissions rework, but it ended up going into `8.7.0`.
- `elastic-agent` is the user that heartbeat will switch to when running synthetic journeys, since chromium can be picky about running as root. ATM, permissions are not granted to this user in order to read journey files from disk.

---

<div class="post-metadata">

### Author: ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)
#### Post date: [May 9, 2023, 12:17pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/24 "2023-05-09T12:17:37Z")

</div>

> [@emilioalvap](#):
>
> As @shahzad31 very kindly mentioned, **push monitors and their related features are not deprecated**.
> 
> What I meant to say is: other monitor types (mainly zip url and local), which are already [deprecated](https://www.elastic.co/guide/en/beats/heartbeat/current/monitor-browser-options.html#monitor-source-zipurl), are _also_ impacted. I should have used better wording on my previous comment, sorry about the confusion.

NP. This is what I assumed, I just wanted clarification, since we've just started to go down this road for our synthetic monitoring.

> `elastic-agent` is the user that heartbeat will switch to when running synthetic journeys, since chromium can be picky about running as root. ATM, permissions are not granted to this user in order to read journey files from disk.

Are there any workarounds for this? I've attempted to set `umask` for the /tmp directory, as well as attempted to do a `setacl` + sticky bit on `/tmp` when the pod starts, but no joy so far.

Thx.

---

<div class="post-metadata">

### Author: ![emilioalvap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emilioalvap/32/99310_2.png) [@emilioalvap](https://discuss.elastic.co/u/emilioalvap)
#### Post date: [May 16, 2023, 11:20am UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/25 "2023-05-16T11:20:29Z")

</div>

Hi @DougR,

Unfortunately, there's no workaround that we can suggest using. Our recommendation would be to upgrade to `v8.8` when possible and, in the meantime, running these on our synthetics infrastructure, if that's an option for you.

---

<div class="post-metadata">

### Author: ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)
#### Post date: [May 16, 2023, 7:19pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/26 "2023-05-16T19:19:53Z")

</div>

> [@emilioalvap](#):
>
> Unfortunately, there's no workaround that we can suggest using. Our recommendation would be to upgrade to `v8.8` when possible and, in the meantime, running these on our synthetics infrastructure, if that's an option for you.

Thx. Considering that we're on `8.7.1`, is there an ETA for `8.8.x`?

---

<div class="post-metadata">

### Author: ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [May 16, 2023, 8:19pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/27 "2023-05-16T20:19:25Z")

</div>

Unfortunately we can't share expected release dates, it's always possible to find a bug that might cause us to delay a release for instance. It has been a while since our last minor, and it's our goal to get this release out to customers as soon as it's ready. Apologies for the issues you've seen, and we hope 8.8 works much better for you.

---

<div class="post-metadata">

### Author: ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)
#### Post date: [May 31, 2023, 6:41pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/28 "2023-05-31T18:41:25Z")

</div>

I've upgraded to `8.8.0`, and everything appears to be working as expected.

---

<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: [June 24, 2023, 6:41pm UTC](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032/29 "2023-06-24T18:41:26Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/elastic-synthetics-journey-receiving-permission-denied/330032.md?page=1)
