# 7.5 \[reporting\] fails randomly

**URL:** <https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160>\
**Category:** Kibana\
**Created:** [January 15, 2020, 3:01pm UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160 "2020-01-15T15:01:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [January 15, 2020, 3:01pm UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160/1 "2020-01-15T15:01:09Z")

</div>

Hello, my users want to create some reports but the completion/fail is erratic. I am running on a debian 9

Could not find more hint to solve that. Can you help, please?

best

the message in the frontend:

```auto
Unable to generate report
Failed to decrypt report job data. Please ensure that xpack.reporting.encryptionKey is set and re-generate this report. Error: Unsupported state or unable to authenticate data

```

My configuration (kibana.yml)

```auto
xpack.reporting.encryptionKey: "XXXEBHAIJXXXXXXXXXXXJESMXXXX79"
xpack.reporting.kibanaServer.port: 443
xpack.reporting.kibanaServer.protocol: https
xpack.reporting.kibanaServer.hostname: mysubdomain.flightwatching.com
xpack.reporting.index: ".reporting-mysubdomain"
xpack.reporting.capture.maxAttempts: 10
xpack.reporting.capture.loadDelay: 10000

```

The kibana.log:

```auto
{
    "type":"log",
    "@timestamp":"2020-01-15T13:53:42Z",
    "tags":["reporting","esqueue","queue-worker","warning"],
    "pid":14559,
    "message":
     "k5f3zsyv0b8f8bed02eycx6q - _claimPendingJobs encountered a version conflict on updating pending job k5fd8kpq0b8f8bed02au4mvk: 
       Error: [version_conflict_engine_exception] [k5fd8kpq0b8f8bed02au4mvk]: version conflict, required seqNo [39], primary term [1]. current document has seqNo [41] and primary term [1], with 
         { index_uuid=\"cPPJv-uMQx-kgFoblb_8-Q\" & shard=\"0\" & index=\".reporting-insight-val-2020.01.12\" }
         \n at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:349:15)
         \n at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:306:7)
         \n at HttpConnector.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)
         \n at IncomingMessage.wrapper (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4929:19)
         \n at IncomingMessage.emit (events.js:194:15)\n at endReadableNT (_stream_readable.js:1103:12)
         \n at process._tickCallback (internal/process/next_tick.js:63:19)"}

```

---

<div class="post-metadata">

**Author:** ![Aaron\_Caldwell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaron_caldwell/32/45755_2.png) [@Aaron\_Caldwell](https://discuss.elastic.co/u/Aaron_Caldwell)\
**Post date:** [January 17, 2020, 3:35am UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160/2 "2020-01-17T03:35:19Z")

</div>

Hello Olivier,

Is it a docker setup? If so, this could be related to the issue in [this discuss thread](https://discuss.elastic.co/t/randomly-getting-error-failed-to-decrypt-report-job-data-with-kibana/179135/7). Scroll to the bottom for a potential fix.

If not, I see some work around this area in this [recently merged PR](https://github.com/elastic/kibana/pull/47768). If it's related to this, or otherwise unexplained, it may be worth [creating an issue](https://github.com/elastic/kibana/issues/new?template=Bug_report.md).

Regards,  
Aaron

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [January 17, 2020, 8:43am UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160/3 "2020-01-17T08:43:23Z")

</div>

OK, we are not with docker and in version 7.5.1. Can you confirm that the [recently merged PR](https://github.com/elastic/kibana/pull/47768) has been included in the 7.5.1?

And why did you call it workaround? should I do something specific to "work around" my problem?

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [January 21, 2020, 10:27am UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160/4 "2020-01-21T10:27:23Z")

</div>

Hello,

can I have an answer? If I create an issue, what can I specify to help the resolver?

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [January 28, 2020, 9:10am UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160/5 "2020-01-28T09:10:58Z")

</div>

Can I have an update?

---

<div class="post-metadata">

**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\
**Post date:** [February 4, 2020, 4:45pm UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160/6 "2020-02-04T16:45:03Z")

</div>

Again?

---

<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 3, 2020, 4:45pm UTC](https://discuss.elastic.co/t/7-5-reporting-fails-randomly/215160/7 "2020-03-03T16:45:06Z")

</div>

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