# \[uSeekM\] Elasticsearch won't start after Tomcat restart **URL:** \ **Category:** Elasticsearch\ **Created:** [August 19, 2013, 9:42am UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255 "2013-08-19T09:42:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![s0r1n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s0r1n/32/38302_2.png) [@s0r1n](https://discuss.elastic.co/u/s0r1n)\ **Post date:** [August 19, 2013, 9:42am UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255/1 "2013-08-19T09:42:31Z")
uSeekM Sesame War's (version 1.2.1) are successfully installed and the Full Text Search works as expected ([https://dev.opensahara.com/projects/useekm](https://dev.opensahara.com/projects/useekm)), but Elasticsearch won't start after Tomcat restart, the issue is reproducible. After a full reindex everything looks fine: # curl -XGET '[http://localhost:9200/\_cluster/nodes/\_local?&pretty=true](http://localhost:9200/_cluster/nodes/_local?&pretty=true)' { "ok" : true, "cluster\_name" : "es.unit.test.cluster", "nodes" : { "1" : { "name" : "GND", "transport\_address" : "local[1]", "hostname" : "solinux", "version" : "0.20.4", "http\_address" : "inet[/134.34.201.121:9200]", "attributes" : { "local" : "true" } } } and the following error occurs after Tomcat restart: # curl -XGET '[http://localhost:9200/\_cluster/nodes/\_local?&pretty=true](http://localhost:9200/_cluster/nodes/_local?&pretty=true)' curl: (7) couldn't connect to host Here the reply from the developer: "This is an elasticsearch feature, uSeekM doesn't really play a role here." ([https://dev.opensahara.com/boards/2/topics/165?r=179](https://dev.opensahara.com/boards/2/topics/165?r=179)) Please help, thank you in advance. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 19, 2013, 9:57am UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255/2 "2013-08-19T09:57:25Z")
Sadly, you need to restart Tomcat. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 19 août 2013 à 11:42, s0r1n [sorin.gheorghiu@uni-konstanz.de](mailto:sorin.gheorghiu@uni-konstanz.de) a écrit : > uSeekM Sesame War's (version 1.2.1) are successfully installed and the Full > Text Search works as expected ([https://dev.opensahara.com/projects/useekm](https://dev.opensahara.com/projects/useekm)), > but Elasticsearch won't start after Tomcat restart, the issue is > reproducible. > > After a full reindex everything looks fine: > > # curl -XGET '[http://localhost:9200/\_cluster/nodes/\_local?&pretty=true](http://localhost:9200/_cluster/nodes/_local?&pretty=true)' > > { > "ok" : true, > "cluster\_name" : "es.unit.test.cluster", > "nodes" : { > "1" : { > "name" : "GND", > "transport\_address" : "local[1]", > "hostname" : "solinux", > "version" : "0.20.4", > "http\_address" : "inet[/134.34.201.121:9200]", > "attributes" : { > "local" : "true" > } > } > } > > and the following error occurs after Tomcat restart: > > # curl -XGET '[http://localhost:9200/\_cluster/nodes/\_local?&pretty=true](http://localhost:9200/_cluster/nodes/_local?&pretty=true)' > > curl: (7) couldn't connect to host > > Here the reply from the developer: "This is an elasticsearch feature, uSeekM > doesn't really play a role here." ( > [opensahara.com](https://dev.opensahara.com/boards/2/topics/165?r=179) > [https://dev.opensahara.com/boards/2/topics/165?r=179](https://dev.opensahara.com/boards/2/topics/165?r=179) ) > > Please help, thank you in advance. > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/uSeekM-Elasticsearch-won-t-start-after-Tomcat-restart-tp4039804.html](http://elasticsearch-users.115913.n3.nabble.com/uSeekM-Elasticsearch-won-t-start-after-Tomcat-restart-tp4039804.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![s0r1n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s0r1n/32/38302_2.png) [@s0r1n](https://discuss.elastic.co/u/s0r1n)\ **Post date:** [August 20, 2013, 1:42pm UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255/3 "2013-08-20T13:42:25Z")
Due to maintenance activities I may be forced to restart Tomcat or the whole server. When ES won't start, the workaround is to rebuild the uSeekM indexes which takes a couple of days. This not acceptable for a production server. Please provide your feedback. Thank you. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 20, 2013, 1:59pm UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255/4 "2013-08-20T13:59:24Z")
What???? When you stop your tomcat and restart it all your data are gone? I think you have something wrong in your code or something. I did that in production for years and never have such an issue! Are you using NodeClient? TransportClient? How do you connect to you elasticsearch nodes? -- David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 20 août 2013 à 15:42, s0r1n [sorin.gheorghiu@uni-konstanz.de](mailto:sorin.gheorghiu@uni-konstanz.de) a écrit : > Due to maintenance activities I may be forced to restart Tomcat or the whole > server. When ES won't start, the workaround is to rebuild the uSeekM indexes > which takes a couple of days. This not acceptable for a production server. > Please provide your feedback. Thank you. > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/uSeekM-Elasticsearch-won-t-start-after-Tomcat-restart-tp4039804p4039866.html](http://elasticsearch-users.115913.n3.nabble.com/uSeekM-Elasticsearch-won-t-start-after-Tomcat-restart-tp4039804p4039866.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![s0r1n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s0r1n/32/38302_2.png) [@s0r1n](https://discuss.elastic.co/u/s0r1n)\ **Post date:** [August 21, 2013, 1:50pm UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255/5 "2013-08-21T13:50:37Z")
Yes, in the beginning all data was gone after a tomcat restart. Since I increased the hw and sw limit for the tomcat user to 32000 the data wasn't erased anymore, but ES won't start. I can't tell if I use NodeClient or TransportClient, I haven't installed ES as standalone, but just uSeekM only. Maybe it helps to show you my config: cluster: name: es.unit.test.cluster node: name: GND local: true index: number\_of\_shards: 1 number\_of\_replicas: 0 analysis: char\_filter: my\_mapping: type: mapping mappings: [ae=\>a, oe=\>o, ue=\>u, ä=\>a, ö=\>o, ü=\>u, AE=\>A, OE=\>O, UE=\>U, Ä=\>A, Ö=\>O, Ü=\>U] analyzer: default: tokenizer: lowercase filter: asciifolding char\_filter: my\_mapping exact: tokenizer: keyword filter: [lowercase, asciifolding] char\_filter: my\_mapping path: logs: /opt/es.tst/log data: /opt/es.tst/data http.enabled: true gateway.type: none discovery.zen.ping.multicast.enabled: false Please check it and let me know if is anything missing here. Thank you. ---
**Author:** ![s0r1n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s0r1n/32/38302_2.png) [@s0r1n](https://discuss.elastic.co/u/s0r1n)\ **Post date:** [November 21, 2013, 7:56am UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255/6 "2013-11-21T07:56:08Z")
The tomcat issue with has been resolved after changing @gateway type@ from @none@ to @local@. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:05am UTC](https://discuss.elastic.co/t/useekm-elasticsearch-wont-start-after-tomcat-restart/13255/7 "2017-07-06T02:05:46Z")