Upgrade to 1.2.1, now broken and status yellow


(Justin-3) #1

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I
stopped it, did the upgrade and started ES again. However, now it is
showing status yellow and not storing any documents:

{"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","build_hash
": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp": "
2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8"},"
tagline": "You Know, for Search"}

{"cluster_name": "es","status": "yellow","timed_out": false,"number_of_nodes
": 1,"number_of_data_nodes": 1,"active_primary_shards": 77,"active_shards":
77,"relocating_shards": 0,"initializing_shards": 0,"unassigned_shards": 77}

Any ideas how to fix?

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #2

Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin info@nodesocket.com a écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I stopped it, did the upgrade and started ES again. However, now it is showing status yellow and not storing any documents:

{
"status": 200,
"name": "Dead Girl",
"version": {
"number": "1.2.1",
"build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
"build_timestamp": "2014-06-03T15:02:52Z",
"build_snapshot": false,
"lucene_version": "4.8"
},
"tagline": "You Know, for Search"
}

{
"cluster_name": "es",
"status": "yellow",
"timed_out": false,
"number_of_nodes": 1,
"number_of_data_nodes": 1,
"active_primary_shards": 77,
"active_shards": 77,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 77
}

Any ideas how to fix?

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/B667A3D9-D45E-49D2-A3B7-0CDF05627939%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(Justin-3) #3

Kibana is showing: Error Could not find Logstash. If you are using a proxy,
ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:

Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin <in...@nodesocket.com <javascript:>> a
écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I
stopped it, did the upgrade and started ES again. However, now it is
showing status yellow and not storing any documents:

{"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp
": "2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8"}
,"tagline": "You Know, for Search"}

{"cluster_name": "es","status": "yellow","timed_out": false,"
number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards": 77,
"active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,"
unassigned_shards": 77}

Any ideas how to fix?

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #4

Probably something wrong in your Kibana dashboard settings, but from an elasticsearch point of view, everything looks fine to me.

Check your Kibana dashboard settings.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:11, Justin info@nodesocket.com a écrit :

Kibana is showing: Error Could not find Logstash. If you are using a proxy, ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin in...@nodesocket.com a écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I stopped it, did the upgrade and started ES again. However, now it is showing status yellow and not storing any documents:

{
"status": 200,
"name": "Dead Girl",
"version": {
"number": "1.2.1",
"build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
"build_timestamp": "2014-06-03T15:02:52Z",
"build_snapshot": false,
"lucene_version": "4.8"
},
"tagline": "You Know, for Search"
}

{
"cluster_name": "es",
"status": "yellow",
"timed_out": false,
"number_of_nodes": 1,
"number_of_data_nodes": 1,
"active_primary_shards": 77,
"active_shards": 77,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 77
}

Any ideas how to fix?

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(Commando.io) #5

Nothing changed, worked with ES 1.2.0 and now I can't view anything in
Kibana. If I go to the default Logstash in Kibana I see all documents up
until the point I upgraded to 1.2.1, but then no documents after.


Justin Keller (Founder)
Commando.io - Manage servers easily online.
commando@nodesocket.com


Twitter: @commando_io

On Sat, Jun 14, 2014 at 1:23 AM, David Pilato david@pilato.fr wrote:

Probably something wrong in your Kibana dashboard settings, but from an
elasticsearch point of view, everything looks fine to me.

Check your Kibana dashboard settings.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:11, Justin info@nodesocket.com a écrit :

Kibana is showing: Error Could not find Logstash. If you are using a
proxy, ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:

Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin in...@nodesocket.com a écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I
stopped it, did the upgrade and started ES again. However, now it is
showing status yellow and not storing any documents:

{"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp
": "2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8"
},"tagline": "You Know, for Search"}

{"cluster_name": "es","status": "yellow","timed_out": false,"
number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards": 77
,"active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,"
unassigned_shards": 77}

Any ideas how to fix?

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.

To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/1yjtq-nS43E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #6

What gives

curl localhost:9200/_search?pretty

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:31, "Commando.io" commando@nodesocket.com a écrit :

Nothing changed, worked with ES 1.2.0 and now I can't view anything in Kibana. If I go to the default Logstash in Kibana I see all documents up until the point I upgraded to 1.2.1, but then no documents after.


Justin Keller (Founder)
Commando.io - Manage servers easily online.
commando@nodesocket.com


Twitter: @commando_io

On Sat, Jun 14, 2014 at 1:23 AM, David Pilato david@pilato.fr wrote:
Probably something wrong in your Kibana dashboard settings, but from an elasticsearch point of view, everything looks fine to me.

Check your Kibana dashboard settings.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:11, Justin info@nodesocket.com a écrit :

Kibana is showing: Error Could not find Logstash. If you are using a proxy, ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin in...@nodesocket.com a écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I stopped it, did the upgrade and started ES again. However, now it is showing status yellow and not storing any documents:

{
"status": 200,
"name": "Dead Girl",
"version": {
"number": "1.2.1",
"build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
"build_timestamp": "2014-06-03T15:02:52Z",
"build_snapshot": false,
"lucene_version": "4.8"
},
"tagline": "You Know, for Search"
}

{
"cluster_name": "es",
"status": "yellow",
"timed_out": false,
"number_of_nodes": 1,
"number_of_data_nodes": 1,
"active_primary_shards": 77,
"active_shards": 77,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 77
}

Any ideas how to fix?

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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.

To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/1yjtq-nS43E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr.

For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/74F28145-F1A9-44EF-9B81-2654F6D5AD79%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(Justin-3) #7

Seemed to work.

{"took": 41,"timed_out": false,"_shards": {"total": 77,"successful": 77,"
failed": 0},"hits": {"total": 334881,"max_score": 1,"hits": [....
On Saturday, June 14, 2014 1:50:27 AM UTC-7, David Pilato wrote:

What gives

curl localhost:9200/_search?pretty

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:31, "Commando.io" <comm...@nodesocket.com
<javascript:>> a écrit :

Nothing changed, worked with ES 1.2.0 and now I can't view anything in
Kibana. If I go to the default Logstash in Kibana I see all documents up
until the point I upgraded to 1.2.1, but then no documents after.


Justin Keller (Founder)
Commando.io - Manage servers easily online.
comm...@nodesocket.com <javascript:>
https://commando.io
Twitter: @commando_io

On Sat, Jun 14, 2014 at 1:23 AM, David Pilato <da...@pilato.fr
<javascript:>> wrote:

Probably something wrong in your Kibana dashboard settings, but from an
elasticsearch point of view, everything looks fine to me.

Check your Kibana dashboard settings.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:11, Justin <in...@nodesocket.com <javascript:>> a
écrit :

Kibana is showing: Error Could not find Logstash. If you are using a
proxy, ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:

Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin in...@nodesocket.com a écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I
stopped it, did the upgrade and started ES again. However, now it is
showing status yellow and not storing any documents:

{"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp
": "2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8
"},"tagline": "You Know, for Search"}

{"cluster_name": "es","status": "yellow","timed_out": false,"
number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards":
77,"active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,"
unassigned_shards": 77}

Any ideas how to fix?

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearc...@googlegroups.com <javascript:>.

To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/1yjtq-nS43E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/aeb767ab-ffc0-4117-83ed-55d67a21134e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Justin-3) #8

So loading the default Logstash dashboard view in Kibana works after all.
Seems just my custom dashboard somehow got corrupted which is really
unfortunate since I spent a long time configuring and setting it up.

On Saturday, June 14, 2014 2:00:44 AM UTC-7, Justin wrote:

Seemed to work.

{"took": 41,"timed_out": false,"_shards": {"total": 77,"successful": 77,"
failed": 0},"hits": {"total": 334881,"max_score": 1,"hits": [....
On Saturday, June 14, 2014 1:50:27 AM UTC-7, David Pilato wrote:

What gives

curl localhost:9200/_search?pretty

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:31, "Commando.io" comm...@nodesocket.com a écrit :

Nothing changed, worked with ES 1.2.0 and now I can't view anything in
Kibana. If I go to the default Logstash in Kibana I see all documents up
until the point I upgraded to 1.2.1, but then no documents after.


Justin Keller (Founder)
Commando.io - Manage servers easily online.
comm...@nodesocket.com
https://commando.io
Twitter: @commando_io

On Sat, Jun 14, 2014 at 1:23 AM, David Pilato da...@pilato.fr wrote:

Probably something wrong in your Kibana dashboard settings, but from an
elasticsearch point of view, everything looks fine to me.

Check your Kibana dashboard settings.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:11, Justin in...@nodesocket.com a écrit :

Kibana is showing: Error Could not find Logstash. If you are using a
proxy, ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:

Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin in...@nodesocket.com a écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I
stopped it, did the upgrade and started ES again. However, now it is
showing status yellow and not storing any documents:

{"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","
build_timestamp": "2014-06-03T15:02:52Z","build_snapshot": false,"
lucene_version": "4.8"},"tagline": "You Know, for Search"}

{"cluster_name": "es","status": "yellow","timed_out": false,"
number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards":
77,"active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,
"unassigned_shards": 77}

Any ideas how to fix?

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearc...@googlegroups.com.

To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/1yjtq-nS43E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3c6cb5f1-b2dd-4315-b542-654103ac0fd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #9

It should not be broken as you just upgraded Elasticsearch.
The same json document stored in /kibana-int/dashboard should work.

I don't see what could break it.

May be you should look at what it looks like:

curl localhost:9200/kibana-int/_search?pretty

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 11:07, Justin info@nodesocket.com a écrit :

So loading the default Logstash dashboard view in Kibana works after all. Seems just my custom dashboard somehow got corrupted which is really unfortunate since I spent a long time configuring and setting it up.

On Saturday, June 14, 2014 2:00:44 AM UTC-7, Justin wrote:
Seemed to work.

{
"took": 41,
"timed_out": false,
"_shards": {
"total": 77,
"successful": 77,
"failed": 0
},
"hits": {
"total": 334881,
"max_score": 1,
"hits": [
....

On Saturday, June 14, 2014 1:50:27 AM UTC-7, David Pilato wrote:
What gives

curl localhost:9200/_search?pretty

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:31, "Commando.io" comm...@nodesocket.com a écrit :

Nothing changed, worked with ES 1.2.0 and now I can't view anything in Kibana. If I go to the default Logstash in Kibana I see all documents up until the point I upgraded to 1.2.1, but then no documents after.


Justin Keller (Founder)
Commando.io - Manage servers easily online.
comm...@nodesocket.com
https://commando.io
Twitter: @commando_io

On Sat, Jun 14, 2014 at 1:23 AM, David Pilato da...@pilato.fr wrote:
Probably something wrong in your Kibana dashboard settings, but from an elasticsearch point of view, everything looks fine to me.

Check your Kibana dashboard settings.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 10:11, Justin in...@nodesocket.com a écrit :

Kibana is showing: Error Could not find Logstash. If you are using a proxy, ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 09:21, Justin in...@nodesocket.com a écrit :

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I stopped it, did the upgrade and started ES again. However, now it is showing status yellow and not storing any documents:

{
"status": 200,
"name": "Dead Girl",
"version": {
"number": "1.2.1",
"build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
"build_timestamp": "2014-06-03T15:02:52Z",
"build_snapshot": false,
"lucene_version": "4.8"
},
"tagline": "You Know, for Search"
}

{
"cluster_name": "es",
"status": "yellow",
"timed_out": false,
"number_of_nodes": 1,
"number_of_data_nodes": 1,
"active_primary_shards": 77,
"active_shards": 77,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 77
}

Any ideas how to fix?

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/1yjtq-nS43E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr.

For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3c6cb5f1-b2dd-4315-b542-654103ac0fd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/356E4041-50EA-41C6-8D61-D049EDEB3DD1%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(system) #10