Did you come up with a solution without deleting the indexes?

On Tuesday, April 16, 2013 7:22:06 PM UTC+2, Kaushal Kapadia wrote:
>
> Dear Denny,
>
> Given that deleting the previous index resolved the web-ui search problem. 
> But didnt doing so erase the previous data? If yes, isnt this a rather 
> risky solution?
>
> On Monday, 8 April 2013 13:43:38 UTC+5:30, Denny Gebel wrote:
>>
>> Hi Aurelien,
>>
>> this worked like a charm! Thank you :)
>>
>> If any1 else is encountering this issue, this is what I exactly did:
>>
>> /etc/init.d/rsyslog stop; /etc/init.d/graylog2-radio stop; 
>>> /etc/init.d/graylog2-server stop; /etc/init.d/rabbitmq-server stop; 
>>> /etc/init.d/httpd stop
>>> curl -XDELETE localhost:9200/graylog2_*
>>> mongo
>>> use graylog2
>>> db.auth("user","pass")
>>> db.message_counts.remove();
>>> exit
>>> /etc/init.d/rsyslog start; /etc/init.d/graylog2-radio start; 
>>> /etc/init.d/graylog2-server start; /etc/init.d/rabbitmq-server start; 
>>> /etc/init.d/httpd start
>>
>>
>> //Denny
>>
>>
>> Am Freitag, 5. April 2013 14:30:00 UTC+2 schrieb Aurelien Vaillant:
>>>
>>> Hi,
>>>
>>> I fix the problem doing this maybe It can work for you
>>> On a crash recovery you have to stop graylog2 service(s) before deleting 
>>> Elasticsearch indexes.
>>> You can even clear mongodb to clear message stats.
>>>
>>> Stop syslog/logstash log collector
>>> Stop graylog2 service
>>> delete ES index using head plugins or curl
>>> On mongodb: use graylog2; db.message_counts.remove();
>>> Start graylog2 service
>>> start log collector
>>>
>>> Regards,
>>> Aurelien
>>>
>>> On Thursday, April 4, 2013 4:09:30 PM UTC+2, Denny Gebel wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I just set up graylog2 0.11.0 with the help of this tutorial: 
>>>> http://baskarc12.blogspot.de/2013/03/graylog2-v010-finally-released-install.html
>>>>
>>>> Messages are arriving, everything looks fine until I try to use the 
>>>> search field with anything else then "All time"
>>>>
>>>> I'll get this Message: "Sorry, but something went wrong."
>>>>
>>>> Logile:
>>>>
>>>> Started GET "/messages/universalsearch?timespan=1800&query=ntp*" for 
>>>>> 172.16.1.42 at 2013-04-04 15:54:35 +0200
>>>>> Processing by MessagesController#universalsearch as HTML
>>>>>   Parameters: {"timespan"=>"1800", "query"=>"ntp*"}
>>>>> Completed 500 Internal Server Error in 117ms
>>>>> URI::InvalidURIError (bad URI(is not URI?): 
>>>>> http://localhost:9200/NOTARGET*,-graylog2_recent/message/_search?from=0&size=100):
>>>>>   app/models/message_gateway.rb:16:in `get'
>>>>>   app/models/message_gateway.rb:101:in `universal_search'
>>>>>   app/controllers/messages_controller.rb:161:in `universalsearch'
>>>>
>>>>
>>>>
>>>>
>>>> If I set the timefilter to "All time" I'll get results but the chart is 
>>>> broken. The wheel is spinning all the time.
>>>>
>>>> Logfile:
>>>>
>>>> Started GET "/messages/universalsearch?timespan=0&query=ntp*" for 
>>>>> 172.16.1.42 at 2013-04-04 15:58:08 +0200
>>>>> Processing by MessagesController#universalsearch as HTML
>>>>>   Parameters: {"timespan"=>"0", "query"=>"ntp*"}
>>>>>   Rendered messages/_sidebar_index.html.erb (77.1ms)
>>>>>   Rendered messages/_result_graph.html.erb (3.3ms)
>>>>>   Rendered messages/_table.html.erb (13.4ms)
>>>>>   Rendered messages/universalsearch.html.erb within 
>>>>> layouts/application (236.7ms)
>>>>>   Rendered shared/_universalsearch.html.erb (3.2ms)
>>>>> Completed 200 OK in 485ms (Views: 309.5ms)
>>>>> Started GET "/visuals/fetch/totalgraph?hours=2" for 172.16.1.42 at 
>>>>> 2013-04-04 15:58:09 +0200
>>>>> Started GET 
>>>>> "/visuals/fetch/resultgraph?interval=hour&query=ntp%2A&since=0" for 
>>>>> 172.16.1.42 at 2013-04-04 15:58:09 +0200
>>>>> Processing by VisualsController#fetch as JSON
>>>>>   Parameters: {"hours"=>"2", "id"=>"totalgraph"}
>>>>> Processing by VisualsController#fetch as JSON
>>>>>   Parameters: {"interval"=>"hour", "query"=>"ntp*", "since"=>"0", 
>>>>> "id"=>"resultgraph"}
>>>>> LOL STREAM 1: nil
>>>>> Completed 200 OK in 120ms (Views: 0.2ms)
>>>>> Completed 500 Internal Server Error in 200ms
>>>>> URI::InvalidURIError (bad URI(is not URI?): 
>>>>> http://localhost:9200/NOTARGET*,-graylog2_recent/message/_search?from=0&size=100):
>>>>>   app/models/message_gateway.rb:16:in `get'
>>>>>   app/models/message_gateway.rb:101:in `universal_search'
>>>>>   app/controllers/visuals_controller.rb:84:in `calculate_querygraph'
>>>>>   app/controllers/visuals_controller.rb:41:in `block in fetch'
>>>>>   app/controllers/visuals_controller.rb:7:in `fetch'
>>>>
>>>>
>>>> I'd guess the "NO TARGET*" is the problem. I think this happened after 
>>>> I tried to remove all test messages with this creepy command: curl 
>>>> -XDELETE localhost:9200/graylog2_*
>>>>
>>>> Shame on me, but is there any fix for it?
>>>>
>>>>
>>>>
>>>> Thanks, Denny
>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to