# “No processor type exists with name \[attachment\]”

**URL:** <https://discuss.elastic.co/t/no-processor-type-exists-with-name-attachment/270076>\
**Category:** Elasticsearch\
**Created:** [April 14, 2021, 3:27am UTC](https://discuss.elastic.co/t/no-processor-type-exists-with-name-attachment/270076 "2021-04-14T03:27:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![judy369](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@judy369](https://discuss.elastic.co/u/judy369)\
**Post date:** [April 14, 2021, 3:27am UTC](https://discuss.elastic.co/t/no-processor-type-exists-with-name-attachment/270076/1 "2021-04-14T03:27:30Z")

</div>

when i create pipline,

```auto
 curl --user elastic:ny123456 -H 'Content-Type: application/json' -XPUT   
 'http://192.168.250.49:9200/_ingest/pipeline/attachment' -d'
{
  "description" : "Extract attachment information",
  "processors" : [
    {
      "attachment" : {
        "field": "data",
        "indexed_chars" : -1,
        "ignore_missing" : true
      }
    }
  ]
}'

```

i got

```auto
    {"error":{"root_cause":[{"type":"parse_exception","reason":"No processor type exists with name [attachment]","processor_type":"attachment"}],"type":"parse_exception","reason":"No processor type exists with name [attachment]","processor_type":"attachment"},"status":400}

```

i did restart the elasticsearch service,but it didn’t work.

i run `curl --user elastic:ny123456 'http://192.168.250.49:9200/_cat/plugins?v' `  
the result is : `name component version, and there is no log`

other message :

```auto
    testuser 60577 1 7 10:55 pts/2 00:02:01 /opt/dev_environment/jdk/bin/java -Xshare:auto -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -XX:+ShowCodeDetailsInExceptionMessages -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.locale.providers=SPI,COMPAT -Xms1g -Xmx1g -XX:+UseG1GC -XX:G1ReservePercent=25 -XX:InitiatingHeapOccupancyPercent=30 -Djava.io.tmpdir=/tmp/elasticsearch-13929928909011903201 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=data -XX:ErrorFile=logs/hs_err_pid%p.log -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m -XX:MaxDirectMemorySize=536870912 -Des.path.home=/usr/local/elk/elasticsearch-7.9.0 -Des.path.conf=/usr/local/elk/elasticsearch-7.9.0/config -Des.distribution.flavor=default -Des.distribution.type=tar -Des.bundled_jdk=true -cp /usr/local/elk/elasticsearch-7.9.0/lib/* org.elasticsearch.bootstrap.Elasticsearch -d
testuser 60598 60577 0 10:55 pts/2 00:00:00 /usr/local/elk/elasticsearch-7.9.0/modules/x-pack-ml/platform/linux-x86_64/bin/controller
testuser 62040 60415 0 11:22 pts/2 00:00:00 grep --color=auto elasticsearch

```

i try this: `https://discuss.elastic.co/t/i-get-the-error-no-processor-type-exists-with-name-attachment/188935`  
`https://discuss.elastic.co/t/ingest-attachment-plugin-exception/69167`

but they didn't solve my problem.

---

<div class="post-metadata">

**Author:** ![judy369](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@judy369](https://discuss.elastic.co/u/judy369)\
**Post date:** [April 14, 2021, 3:43am UTC](https://discuss.elastic.co/t/no-processor-type-exists-with-name-attachment/270076/2 "2021-04-14T03:43:02Z")

</div>

i found elasticsearch-plugin was missed.  
check it by run : bin/elasticsearch-plugin list

reinstall the plugin, then restart the node ,the problem solved

---

<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:** [May 12, 2021, 3:43am UTC](https://discuss.elastic.co/t/no-processor-type-exists-with-name-attachment/270076/3 "2021-05-12T03:43:51Z")

</div>

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