Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via JIRA by Paul Czarkowski, 1 year ago
[logstash-syslog-%{+YYYY.MM.dd}] Invalid index name [logstash-syslog-%{+YYYY.MM.dd}], must be lowercase
via JIRA by Paul Czarkowski, 2 years ago
[logstash-syslog-%{+YYYY.MM.dd}] Invalid index name [logstash-syslog-%{+YYYY.MM.dd}], must be lowercase
via Google Groups by rob...@quizlet.com, 2 years ago
[quizlet] Invalid index name [quizlet], an alias with the same name already exists
via GitHub by Flupsy
, 1 year ago
[sayit] Invalid index name [sayit], an alias with the same name already exists
via GitHub by j0hnsmith
, 2 years ago
[files] Invalid index name [files], an alias with the same name already exists
org.elasticsearch.indices.InvalidIndexNameException: [logstash-syslog-%{+YYYY.MM.dd}] Invalid index name [logstash-syslog-%{+YYYY.MM.dd}], must be lowercase	at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validate(MetaDataCreateIndexService.java:494)	at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.access$100(MetaDataCreateIndexService.java:79)	at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$1.execute(MetaDataCreateIndexService.java:139)	at org.elasticsearch.cluster.service.InternalClusterService$2.run(InternalClusterService.java:223)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)	at java.lang.Thread.run(Thread.java:636)