# Filebeat Event Hub - 409 The specified blob already exists **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [July 20, 2020, 10:39pm UTC](https://discuss.elastic.co/t/filebeat-event-hub-409-the-specified-blob-already-exists/241942 "2020-07-20T22:39:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![CSelastic](https://avatars.discourse-cdn.com/v4/letter/c/e0b2c6/32.png) [@CSelastic](https://discuss.elastic.co/u/CSelastic)\ **Post date:** [July 20, 2020, 10:39pm UTC](https://discuss.elastic.co/t/filebeat-event-hub-409-the-specified-blob-already-exists/241942/1 "2020-07-20T22:39:56Z")
Hi -- I'm running filebeat 7.6.2 and am encountering an issue with the Azure Event Hub input plugin. I believe this was caused due to unclean shutdown. I'm seeing the following errors, and messages are not pulled in from the Event Hub: RESPONSE Status: 409 The specified blob already exists. Full log: ```auto Jul 20 22:21:24 systemd[1]: Started Filebeat sends log files to Logstash or directly to Elasticsearch.. Jul 20 22:21:34 filebeat[1622]: ________ ____ __ Jul 20 22:21:34 filebeat[1622]: / ____/_____ ____/ /_/ / / /___ / /_ _____ Jul 20 22:21:34 filebeat[1622]: / __/ | | / / _ \/__ \/ __/ /_/ / / / /__ \/ ___/ Jul 20 22:21:34 filebeat[1622]: / / ___| |/ /__ / / / / /_/ __/ /_/ / /_/ (__ ) Jul 20 22:21:34 filebeat[1622]: / _____/ |___ /\ ___/_/ /_/\__ /_/ /_/\ __,_/_.___ / ____ / Jul 20 22:21:34 filebeat[1622]: => processing events, ctrl+c to exit Jul 20 22:21:34 /usr/share/filebeat/bin/filebeat[1622]: 2020/07/20 22:21:34 ==> REQUEST/RESPONSE (Try=1/7.254983ms, OpTime=7.337978ms) -- REQUEST ERROR PUT https://.blob.core.windows.net/filebeat-logevents/0?timeout=61 Authorization: REDACTED Content-Length: [80] If-None-Match: [*] User-Agent: [Azure-Storage/0.7 (go1.13.8; linux)] X-Ms-Blob-Cache-Control: [] X-Ms-Blob-Content-Disposition: [] X-Ms-Blob-Content-Encoding: [] X-Ms-Blob-Content-Language: [] X-Ms-Blob-Content-Type: [] X-Ms-Blob-Type: [BlockBlob] X-Ms-Client-Request-Id: [60e9b] X-Ms-Version: [2018-11-09] x-ms-date: [Mon, 20 Jul 2020 22:21:34 GMT] -------------------------------------------------------------------------------- RESPONSE Status: 409 The specified blob already exists. Content-Length: [220] Content-Type: [application/xml] Date: [Mon, 20 Jul 2020 22:21:42 GMT] Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0] X-Ms-Error-Code: [BlobAlreadyExists] X-Ms-Request-Id: [53000] X-Ms-Version: [2018-11-09] -------------------------------------------------------------------------------- ERROR: -> github.com/elastic/beats/vendor/github.com/Azure/azure-storage-blob-go/azblob.newStorageError, /go/src/github.com/elastic/beats/vendor/github.com/Azure/azure-storage-blob-go/azblob/zc_storage_error.go:42 ===== RESPONSE ERROR (ServiceCode=BlobAlreadyExists) ===== Description=The specified blob already exists. RequestId:530000 Time:2020-07-20T22:21:43.1409467Z, Details: Code: BlobAlreadyExists PUT https://.blob.core.windows.net/filebeat-logevents/0?timeout=61 Authorization: REDACTED Content-Length: [80] If-None-Match: [*] User-Agent: [Azure-Storage/0.7 (go1.13.8; linux)] X-Ms-Blob-Cache-Control: [] X-Ms-Blob-Content-Disposition: [] X-Ms-Blob-Content-Encoding: [] X-Ms-Blob-Content-Language: [] X-Ms-Blob-Content-Type: [] X-Ms-Blob-Type: [BlockBlob] X-Ms-Client-Request-Id: [60e9b] X-Ms-Date: [Mon, 20 Jul 2020 22:21:34 GMT] X-Ms-Version: [2018-11-09] -------------------------------------------------------------------------------- RESPONSE Status: 409 The specified blob already exists. Content-Length: [220] Content-Type: [application/xml] Date: [Mon, 20 Jul 2020 22:21:42 GMT] Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0] X-Ms-Error-Code: [BlobAlreadyExists] X-Ms-Request-Id: [5300] X-Ms-Version: [2018-11-09] goroutine 57 [running]: github.com/elastic/beats/vendor/github.com/Azure/azure-storage-blob-go/azblob.stack(0xc0008637d0, 0xc00015af00, 0xc0008ce510) /go/src/github.com/elastic/beats/vendor/github.com/Azure/azure-storage-blob-go/azblob/zc_policy_request_log.go:146 +0x9d github.com/elastic/beats/vendor/github.com/Azure/azure-storage-blob-go/azblob.NewRequestLogPolicyFactory.func1.1(0x37512a0, 0xc0001c97a0, 0xc00015af00, 0x10, 0x2ec2420, 0x1, 0xc000753600) ``` I've tried renaming my registry file, no luck. Any help is appreciated! ---
**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\ **Post date:** [July 21, 2020, 11:03am UTC](https://discuss.elastic.co/t/filebeat-event-hub-409-the-specified-blob-already-exists/241942/2 "2020-07-21T11:03:13Z")
This looks more like an Azure error than a Beats one. At least it happens in the Azure's Go library (outside of Beats). Have you posted the same question in Azure forums? Does it happens with a new / fresh instance? The only suggestion that comes to my mind is to remove the `data` folder where the registry is, maybe that will help. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 18, 2020, 1:03pm UTC](https://discuss.elastic.co/t/filebeat-event-hub-409-the-specified-blob-already-exists/241942/3 "2020-08-18T13:03:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.