# Reporting generate CSV error:Unable to generate report Max attempts reached (3)
**URL:** https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155
**Category:** Kibana
**Created:** [April 24, 2019, 5:29am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155 "2019-04-24T05:29:17Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@\_Jiawen](https://discuss.elastic.co/u/_Jiawen)
#### Post date: [April 24, 2019, 5:29am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/1 "2019-04-24T05:29:18Z")
When I generate a report in kibana, the maximum CSV file I can successfully generate and download is 986062 bytes, which contains 6586 hits, and cannot be successfully generated when there are more than 10000 hits. And I have config some related fields in kibana.yml, but it still can't generate CSV.
kibana.yml :
xpack.monitoring.enabled: true
server.maxPayloadBytes: 10485760
xpack.reporting.queue.timeout: 3600000
xpack.reporting.csv.maxSizeBytes: 104857600
AND I can't find the error detail in kibana.log:confounded:
Thanks.
---
### Author:  [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)
#### Post date: [April 24, 2019, 1:12pm UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/2 "2019-04-24T13:12:50Z")
@joelgriffith can we please get some help here?
Thanks,
Bhavya
---
### Author:  [@\_Jiawen](https://discuss.elastic.co/u/_Jiawen)
#### Post date: [April 25, 2019, 1:51am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/3 "2019-04-25T01:51:31Z")
I'd like to know why I can't generate a CSV file larger than 1KB, and why I can't find the reporting error information in the kibana.log.
Thank you for your help.
---
### Author:  [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)
#### Post date: [April 27, 2019, 12:29am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/4 "2019-04-27T00:29:11Z")
@_Jiawen can you set your logging to:
```auto
logging.verbose: true
```
This should give us some better logs on what's going on inside of reporting.
---
### Author:  [@\_Jiawen](https://discuss.elastic.co/u/_Jiawen)
#### Post date: [April 28, 2019, 5:15am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/5 "2019-04-28T05:15:31Z")
Thank you for your replay.
Do you mean this :
logging.verbose: true
logging.quiet: false
I add this into kibana.yml and encountered an error that prevented kibana from starting, and I haven't been able to fix it yet. My kibana startup is started through a script that I wrote myself.
the following error：
ValidationError: child "logging" fails because [child "verbose" fails because ["verbose" must be one of [false]]]
---
### Author:  [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)
#### Post date: [May 7, 2019, 5:55pm UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/6 "2019-05-07T17:55:18Z")
Apologies for that, could you try this setting instead (removing that other config I sent)?
`logging.events.log: ['warning', 'error', 'fatal', 'info']`
---
### Author:  [@\_Jiawen](https://discuss.elastic.co/u/_Jiawen)
#### Post date: [May 10, 2019, 2:12am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/7 "2019-05-10T02:12:05Z")
Do you mean try this setting in kibana.yml? I didn't find any details about this setting.
---
### Author:  [@\_Jiawen](https://discuss.elastic.co/u/_Jiawen)
#### Post date: [May 10, 2019, 3:13am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/8 "2019-05-10T03:13:40Z")
I tried add this setting in kibana.yml, but kibana.log hasn't changed, and when the report failed still doesn't display details in kibana.log
---
### Author:  [@\_Jiawen](https://discuss.elastic.co/u/_Jiawen)
#### Post date: [May 10, 2019, 9:11am UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/9 "2019-05-10T09:11:31Z")
I think I found the problem.
I found an error message in the access.log of Nginx: "POST /.reporting-2019.05.05/esqueue/jvhqzbtn0ixp3d278gyb3/\_update?version=2 HTTP/1.1" 413 199 "-" "-" "-" "0.043" "-" - -.
The server returns a status code of 413 means that the uploaded file is too large, the related parameter is client\_max\_body\_size which defalut is 1M , modify the client\_max\_body\_size in nginx.conf can solve my problem. Although I still can't find any detail in kibana.log.
Thank you for your help.🥰🥰🥰
---
### Author:  [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)
#### Post date: [May 10, 2019, 3:03pm UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/10 "2019-05-10T15:03:55Z")
Glad you found it! There is some logging we do when there's a discrepancy between elasticsearch and kibana, but it's not foolproof.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 7, 2019, 3:03pm UTC](https://discuss.elastic.co/t/reporting-generate-csv-error-unable-to-generate-report-max-attempts-reached-3/178155/11 "2019-06-07T15:03:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.