Thanks for all the help everyone. I know it probably wasn't a great thing to do, but I just deleted all the indexes manually. System is back up and running now.
On Wednesday, February 10, 2016 at 12:48:36 PM UTC-6, jeremys wrote: > > Thank you for the info. > > The problem is I have a ton of unassigned shards in a bunch of indices. > From the link you gave me, it seems that he only has one index he is > dealing with which is t37. Am I incorrect? > > Here are just a few: > > curl: (3) [globbing] unmatched close brace/bracket in column 2 > graylog_521 0 p STARTED 541796 238.4mb 127.0.1.1 Obituary > graylog_521 0 r UNASSIGNED > graylog_521 3 p STARTED 546640 239.5mb 127.0.1.1 Obituary > graylog_521 3 r UNASSIGNED > graylog_521 1 p STARTED 547201 239.6mb 127.0.1.1 Obituary > graylog_521 1 r UNASSIGNED > graylog_521 2 p STARTED 554210 242.8mb 127.0.1.1 Obituary > graylog_521 2 r UNASSIGNED > graylog_488 0 p STARTED 558381 232mb 127.0.1.1 Obituary > graylog_488 0 r UNASSIGNED > graylog_488 3 p STARTED 567360 234.4mb 127.0.1.1 Obituary > graylog_488 3 r UNASSIGNED > graylog_488 1 p STARTED 568455 235.2mb 127.0.1.1 Obituary > graylog_488 1 r UNASSIGNED > graylog_488 2 p STARTED 578076 239.1mb 127.0.1.1 Obituary > graylog_488 2 r UNASSIGNED > graylog_522 0 p STARTED 540005 230.9mb 127.0.1.1 Obituary > graylog_522 0 r UNASSIGNED > graylog_522 3 p STARTED 547906 233.9mb 127.0.1.1 Obituary > graylog_522 3 r UNASSIGNED > graylog_522 1 p STARTED 548048 233.7mb 127.0.1.1 Obituary > graylog_522 1 r UNASSIGNED > graylog_522 2 p STARTED 555826 236.9mb 127.0.1.1 Obituary > graylog_522 2 r UNASSIGNED > graylog_489 0 p STARTED 568793 239.3mb 127.0.1.1 Obituary > graylog_489 0 r UNASSIGNED > graylog_489 3 p STARTED 563228 236.8mb 127.0.1.1 Obituary > graylog_489 3 r UNASSIGNED > graylog_489 1 p STARTED 564485 237.2mb 127.0.1.1 Obituary > graylog_489 1 r UNASSIGNED > graylog_489 2 p STARTED 560340 235.9mb 127.0.1.1 Obituary > > > On Wednesday, February 10, 2016 at 11:51:00 AM UTC-6, Jochen Schalanda > wrote: >> >> Hi, >> >> I assume that there are lots of unassigned shards now in your >> Elasticsearch cluster. >> >> See >> https://t37.net/how-to-fix-your-elasticsearch-cluster-stuck-in-initializing-shards-mode.html >> >> for details how to handle this. >> >> Cheers, >> Jochen >> >> On Wednesday, 10 February 2016 18:28:39 UTC+1, jeremys wrote: >>> >>> Elasticsearch cluster is still red. Here is the current log after a >>> reboot >>> >> -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/1b8b81cb-ab38-42a3-abfa-96e393c3444a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
