date:20150921

[graylog2] Re: Search issues after update to 1.2

2015-09-21 Thread Jochen Schalanda

Hi Arkadiy,

thanks for posting these log messages. The underlying issue will be fixed 
in Graylog 1.2.1 which we plan to release soon (see 
https://github.com/Graylog2/graylog2-server/pull/1427).


Cheers,
Jochen

On Monday, 21 September 2015 11:37:31 UTC+2, Arkadiy Shinkarev wrote:
>
> Now I see following errors while try to recalculate index ranges:
> 2015-09-21T12:25:29.681+03:00 INFO  [RebuildIndexRangesJob] Re-calculating 
> index ranges.
> 2015-09-21T12:25:29.681+03:00 INFO  [SystemJobManager] Submitted SystemJob 
>  
> [org.graylog2.indexer.ranges.RebuildIndexRangesJob]
> 2015-09-21T12:25:33.656+03:00 INFO  [RebuildIndexRangesJob] Could not 
> calculate range of index [graylog2_30]. Skipping.
> java.lang.IllegalArgumentException: Invalid format: "1.436259964997E12" is 
> malformed at ".436259964997E12"
> at 
> org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
> at 
> org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
> at 
> org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
> at 
> org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
> at 
> org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
> at 
> com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2015-09-21T12:25:36.550+03:00 INFO  [RebuildIndexRangesJob] Could not 
> calculate range of index [graylog2_41]. Skipping.
> java.lang.IllegalArgumentException: Invalid format: "1.441446878921E12" is 
> malformed at ".441446878921E12"
> at 
> org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
> at 
> org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
> at 
> org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
> at 
> org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
> at 
> org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
> at 
> com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
>
> On Monday, September 21, 2015 at 11:59:24 AM UTC+3, Arkadiy Shinkarev 
> wrote:
>>
>> Current index is graylog2_44
>>
>> On Monday, September 21, 2015 at 11:58:19 AM UTC+3, Arkadiy Shinkarev 
>> wrote:
>>>
>>> Thanks for your reply!
>>>
>>> There is no error messages in logs at all.
>>>
>>> $  curl -XGET '
>>> http://m1-gl-es01:9200/graylog2_*/index_range/_search?pretty=true'
>>>
>>>   "took" : 38,
>>>   "timed_out" : false,
>>>   "_shards" : {
>>> "total" : 40,
>>> "successful" : 40,
>>> "failed" : 0
>>>   },
>>>   "hits" : {
>>> "total" : 20,
>>> "max_score" : 1.0,
>>> "hits" : [ {
>>>   "_index" : "graylog2_25",
>>>   "_type" : "index_range",
>>>   "_id" : "graylog2_25",
>>>   "_score" : 1.0,
>>>   
>>> "_source":{"gl2_index_range_index_name":"graylog2_25","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-17T21:06:14.000Z","gl2_index_range_
>>> calculated_at":"2015-09-12T23:01:29.000Z","gl2_index_range_took_ms":4191}
>>> }, {
>>>   "_index" : "graylog2_27",
>>>   "_type" : "index_range",
>>>   "_id" : "graylog2_27",
>>>   "_score" : 1.0,
>>>   
>>>

[graylog2] Re: Search issues after update to 1.2

2015-09-21 Thread Arkadiy Shinkarev

Thank you for your reply!

Additionally - I just upgraded Elasticsearch cluster to 1.7.2 and run 
recalculate index range job - it fixed the problem.


On Monday, September 21, 2015 at 2:45:04 PM UTC+3, Jochen Schalanda wrote:
>
> Hi Arkadiy,
>
> thanks for posting these log messages. The underlying issue will be fixed 
> in Graylog 1.2.1 which we plan to release soon (see 
> https://github.com/Graylog2/graylog2-server/pull/1427).
>
>
> Cheers,
> Jochen
>
> On Monday, 21 September 2015 11:37:31 UTC+2, Arkadiy Shinkarev wrote:
>>
>> Now I see following errors while try to recalculate index ranges:
>> 2015-09-21T12:25:29.681+03:00 INFO  [RebuildIndexRangesJob] 
>> Re-calculating index ranges.
>> 2015-09-21T12:25:29.681+03:00 INFO  [SystemJobManager] Submitted 
>> SystemJob  
>> [org.graylog2.indexer.ranges.RebuildIndexRangesJob]
>> 2015-09-21T12:25:33.656+03:00 INFO  [RebuildIndexRangesJob] Could not 
>> calculate range of index [graylog2_30]. Skipping.
>> java.lang.IllegalArgumentException: Invalid format: "1.436259964997E12" 
>> is malformed at ".436259964997E12"
>> at 
>> org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
>> at 
>> org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
>> at 
>> org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
>> at 
>> org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
>> at 
>> org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
>> at 
>> com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
>> at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at 
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>> at 
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>> 2015-09-21T12:25:36.550+03:00 INFO  [RebuildIndexRangesJob] Could not 
>> calculate range of index [graylog2_41]. Skipping.
>> java.lang.IllegalArgumentException: Invalid format: "1.441446878921E12" 
>> is malformed at ".441446878921E12"
>> at 
>> org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
>> at 
>> org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
>> at 
>> org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
>> at 
>> org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
>> at 
>> org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
>> at 
>> com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
>> at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at 
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>> at 
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> On Monday, September 21, 2015 at 11:59:24 AM UTC+3, Arkadiy Shinkarev 
>> wrote:
>>>
>>> Current index is graylog2_44
>>>
>>> On Monday, September 21, 2015 at 11:58:19 AM UTC+3, Arkadiy Shinkarev 
>>> wrote:

 Thanks for your reply!

 There is no error messages in logs at all.

 $  curl -XGET '
 http://m1-gl-es01:9200/graylog2_*/index_range/_search?pretty=true'

   "took" : 38,
   "timed_out" : false,
   "_shards" : {
 "total" : 40,
 "successful" : 40,
 "failed" : 0
   },
   "hits" : {
 "total" : 20,
 "max_score" : 1.0,
 "hits" : [ {
   "_index" : "graylog2_25",
   "_type" : "index_range",
   "_id" : "graylog2_25",
   "_score" : 1.0,
   
 "_source":{"gl2_index_range_index_name":"graylog2_25","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-17T21:06:14.000Z","gl2_index_range_

Re: [graylog2] graylog2-web-interface - build_release.sh fails today

2015-09-21 Thread Edmundo Alvarez

Hi Jesse,

The npm team released version 3 these days and that is breaking our 
build_release.sh script at the moment. Please stick with npm 2 or use a newer 
version of the build_release.sh script that fixes the installed version to the 
latest npm 2 available.

Regards,

Edmundo

> On 18 Sep 2015, at 23:06, Jesse Skrivseth  wrote:
> 
> Yesterday the build worked fine, but today I've made no changes and I'm 
> getting npm issues:
> 
> npm WARN package.json graylog-web-interface@1.3.0-SNAPSHOT No repository 
> field.
> npm WARN package.json graylog-web-interface@1.3.0-SNAPSHOT No README data
> npm http GET https://registry.npmjs.org/npm/3.3.4
> npm http 200 https://registry.npmjs.org/npm/3.3.4
> npm http GET https://registry.npmjs.org/npm/-/npm-3.3.4.tgz
> npm http 200 https://registry.npmjs.org/npm/-/npm-3.3.4.tgz
> npm WARN prefer global npm@3.3.4 should be installed with -g
> npm@3.3.4 node_modules/npm
> Using npm 
> module.js:340
> throw err;
>   ^
> Error: Cannot find module 'are-we-there-yet'
> at Function.Module._resolveFilename (module.js:338:15)
> at Function.Module._load (module.js:280:25)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object. 
> (/home/jesse/IdeaProjects/graylog2-web-interface/javascript/node_modules/npm/node_modules/npmlog/log.js:2:16)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> 
> 
> Changing build_release.sh from:
> 
> # Install same npm version as we use in travis
> rm -rf ./node_modules
> npm install --no-spin npm@latest
> 
> to
> 
> # Install same npm version as we use in travis
> rm -rf ./node_modules
> npm install --no-spin npm@2
> 
> 
> allows it to build properly. Any ideas?
> 
> -- 
> 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 graylog2+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/graylog2/c5303cb6-f651-4cc5-bd04-fedab9a9e6da%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/1D7B26FF-5E12-40F4-A6BB-478201E8F442%40graylog.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Search issues after update to 1.2

2015-09-21 Thread Jochen Schalanda

Cool, thanks for your feedback, Arkadiy!

Cheers,
Jochen

On Monday, 21 September 2015 14:47:17 UTC+2, Arkadiy Shinkarev wrote:
>
> Thank you for your reply!
>
> Additionally - I just upgraded Elasticsearch cluster to 1.7.2 and run 
> recalculate index range job - it fixed the problem.
>
>
> On Monday, September 21, 2015 at 2:45:04 PM UTC+3, Jochen Schalanda wrote:
>>
>> Hi Arkadiy,
>>
>> thanks for posting these log messages. The underlying issue will be fixed 
>> in Graylog 1.2.1 which we plan to release soon (see 
>> https://github.com/Graylog2/graylog2-server/pull/1427).
>>
>>
>> Cheers,
>> Jochen
>>
>> On Monday, 21 September 2015 11:37:31 UTC+2, Arkadiy Shinkarev wrote:
>>>
>>> Now I see following errors while try to recalculate index ranges:
>>> 2015-09-21T12:25:29.681+03:00 INFO  [RebuildIndexRangesJob] 
>>> Re-calculating index ranges.
>>> 2015-09-21T12:25:29.681+03:00 INFO  [SystemJobManager] Submitted 
>>> SystemJob  
>>> [org.graylog2.indexer.ranges.RebuildIndexRangesJob]
>>> 2015-09-21T12:25:33.656+03:00 INFO  [RebuildIndexRangesJob] Could not 
>>> calculate range of index [graylog2_30]. Skipping.
>>> java.lang.IllegalArgumentException: Invalid format: "1.436259964997E12" 
>>> is malformed at ".436259964997E12"
>>> at 
>>> org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
>>> at 
>>> org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
>>> at 
>>> org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
>>> at 
>>> org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
>>> at 
>>> org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
>>> at 
>>> com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
>>> at 
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>> at 
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>>> at 
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>> 2015-09-21T12:25:36.550+03:00 INFO  [RebuildIndexRangesJob] Could not 
>>> calculate range of index [graylog2_41]. Skipping.
>>> java.lang.IllegalArgumentException: Invalid format: "1.441446878921E12" 
>>> is malformed at ".441446878921E12"
>>> at 
>>> org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
>>> at 
>>> org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
>>> at 
>>> org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
>>> at 
>>> org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
>>> at 
>>> org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
>>> at 
>>> com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
>>> at 
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>> at 
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>>> at 
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>> On Monday, September 21, 2015 at 11:59:24 AM UTC+3, Arkadiy Shinkarev 
>>> wrote:

 Current index is graylog2_44

 On Monday, September 21, 2015 at 11:58:19 AM UTC+3, Arkadiy Shinkarev 
 wrote:
>
> Thanks for your reply!
>
> There is no error messages in logs at all.
>
> $  curl -XGET '
> http://m1-gl-es01:9200/graylog2_*/index_range/_search?pretty=true'
>
>   "took" : 38,
>   "timed_out" : false,
>   "_shards" : {
> "total" : 40,
> "successful" : 40,
> "failed" : 0
>   },
>   "hits" : {
> "total" : 20,
> "max_score" : 1.0,
> "hits" : [ {
>   "_index" : "graylog2_25",
>   "_type" : "index_range",
>

[graylog2] Graylog SSl configuration query.

2015-09-21 Thread Anant Sawant

Hi!!

We have done the manual setup of Graylog web and Graylog server component 
on Ubuntu 14.04.4. From the document provided at "http://docs.graylog.org; 
we are unable to find setting up SSl for Graylog. I am running Graylog 
1.1.6. Kindly provide/guide us with steps to configure SSL.

Thanks in Advance!!

Anant :-)

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/0e4b2616-2271-4b11-8f91-5818592cb62e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Search issues after update to 1.2

2015-09-21 Thread Arkadiy Shinkarev

Now I see following errors while try to recalculate index ranges:
2015-09-21T12:25:29.681+03:00 INFO  [RebuildIndexRangesJob] Re-calculating 
index ranges.
2015-09-21T12:25:29.681+03:00 INFO  [SystemJobManager] Submitted SystemJob 

[org.graylog2.indexer.ranges.RebuildIndexRangesJob]
2015-09-21T12:25:33.656+03:00 INFO  [RebuildIndexRangesJob] Could not 
calculate range of index [graylog2_30]. Skipping.
java.lang.IllegalArgumentException: Invalid format: "1.436259964997E12" is 
malformed at ".436259964997E12"
at 
org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
at 
org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
at 
org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
at 
org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
at 
org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
at 
com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2015-09-21T12:25:36.550+03:00 INFO  [RebuildIndexRangesJob] Could not 
calculate range of index [graylog2_41]. Skipping.
java.lang.IllegalArgumentException: Invalid format: "1.441446878921E12" is 
malformed at ".441446878921E12"
at 
org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:899)
at 
org.graylog2.indexer.ranges.EsIndexRangeService.timestampStatsOfIndex(EsIndexRangeService.java:258)
at 
org.graylog2.indexer.ranges.EsIndexRangeService.calculateRange(EsIndexRangeService.java:216)
at 
org.graylog2.indexer.ranges.RebuildIndexRangesJob.execute(RebuildIndexRangesJob.java:96)
at 
org.graylog2.system.jobs.SystemJobManager$1.run(SystemJobManager.java:88)
at 
com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

On Monday, September 21, 2015 at 11:59:24 AM UTC+3, Arkadiy Shinkarev wrote:
>
> Current index is graylog2_44
>
> On Monday, September 21, 2015 at 11:58:19 AM UTC+3, Arkadiy Shinkarev 
> wrote:
>>
>> Thanks for your reply!
>>
>> There is no error messages in logs at all.
>>
>> $  curl -XGET '
>> http://m1-gl-es01:9200/graylog2_*/index_range/_search?pretty=true'
>>
>>   "took" : 38,
>>   "timed_out" : false,
>>   "_shards" : {
>> "total" : 40,
>> "successful" : 40,
>> "failed" : 0
>>   },
>>   "hits" : {
>> "total" : 20,
>> "max_score" : 1.0,
>> "hits" : [ {
>>   "_index" : "graylog2_25",
>>   "_type" : "index_range",
>>   "_id" : "graylog2_25",
>>   "_score" : 1.0,
>>   
>> "_source":{"gl2_index_range_index_name":"graylog2_25","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-17T21:06:14.000Z","gl2_index_range_
>> calculated_at":"2015-09-12T23:01:29.000Z","gl2_index_range_took_ms":4191}
>> }, {
>>   "_index" : "graylog2_27",
>>   "_type" : "index_range",
>>   "_id" : "graylog2_27",
>>   "_score" : 1.0,
>>   
>> "_source":{"gl2_index_range_index_name":"graylog2_27","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-26T22:43:14.000Z","gl2_index_range_
>> calculated_at":"2015-09-12T23:01:09.000Z","gl2_index_range_took_ms":10686}
>> }, {
>>   "_index" : "graylog2_29",
>>   "_type" : "index_range",
>>   "_id" : "graylog2_29",
>>   "_score" : 1.0,
>>   
>> "_source":{"gl2_index_range_index_name":"graylog2_29","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-07-07T09:06:05.000Z","gl2_index_range_

Re: [graylog2] Graylog plugin - elastic field types

2015-09-21 Thread Joey Lane

Jesse, any chance you would consider posting the template you used for 
this?  I think we are both doing something similar.  I have written a 
Graylog plugin which retrieves geo-location data from a local server using 
a RESTful API.  The lat/lon is stored as a field in Elasticsearch, however 
when I try to use the tile map in Kibana 4, the field is detected as 
STRING, and not GEO POINT, so I cannot use the map.  Very curious to see 
how using an index template can help me ensure the field is processed as 
GEO POINT and not STRING.

On Tuesday, June 23, 2015 at 1:17:04 PM UTC-5, Jesse Skrivseth wrote:
>
> Hi Kay! Thanks for the detailed response. Using templates is the route we 
> took and it works great. One shortcoming is that you must know the names of 
> the fields to define them in the template. If you're coding a plugin that 
> dynamically adds fields back to the message, and you can't know the names 
> beforehand, you're kind of out of luck. You can add the elastic template 
> and cycle the index deflector in Graylog and it'll hold from there on out. 
> I suppose that'll do for the near term. 
>
> Thanks again!
>
> -Jesse
>

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/760cc90e-3f58-4b3d-be6f-f9681da919b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Trends presentation in dashboard

2015-09-21 Thread Edmundo Alvarez

Hi Stan,

I have been trying to reproduce this issue on 1.2 but I couldn't. 1.2.1 will be 
out soon, so I think it would be best that you give it a try and see if it 
fixes the problem. Otherwise, please open an issue on 
https://github.com/Graylog2/graylog2-web-interface/issues so we can investigate 
further.

Thank you,

Edmundo

> On 18 Sep 2015, at 16:23, Stanislav Kopp  wrote:
> 
> Hi Edmundo,
> 
> thx for explanation, I did some research for another counter, see
> screenshots: http://imgur.com/a/765md
> the first one is counter for errors in last hour, you see 3437 messages
> the second one is the same stream for last 2 hours, 6636 messages,
> what makes 6636-3437=3199, so this mean for me the number of errors
> now is more than for "another" last hour, but the widget is still
> green (no screenshot, but you can trust me :)
> 
> 
> Best,
> Stan
> 
> 
> 
> 2015-09-18 16:06 GMT+02:00 Edmundo Alvarez :
>> To be honest I'm not sure if it is an actual error or some misunderstanding 
>> of how it works, as it is tricky. I will explain it here a bit more in 
>> depth, so you can investigate further, and decide if it is working or not.
>> 
>> When you add a count widget for the last 5 minutes, Graylog will do a search 
>> in the last 5 minutes and count the number of messages. Adding a trend to 
>> that widget means that Graylog will do two searches: one in the last 5 
>> minutes for the actual number you want to see, and another one in the 
>> previous 5 minutes that is, since 10 minutes ago to 5 minutes ago, and 
>> compare the results to show the trend information.
>> 
>> So, in summary, to see if it is working as expected, you could do a search 
>> in the last 10 minutes, subtract the count for the last 5 minutes, and see 
>> if the previous count was higher or lower. Please let us know the results, 
>> so we know if there is a problem with it.
>> 
>> Cheers,
>> 
>> Edmundo
>> 
>>> On 18 Sep 2015, at 15:39, Stanislav Kopp  wrote:
>>> 
>>> Hi Edmundo,
>>> 
>>> thx, I will try upgrade graylog to 1.2 next week (I wanted to wait
>>> till 1.2.1 honestly), here some screenshot of my dasboard
>>> http://imgur.com/a/l0t02, the widget shows count of specific errors
>>> every 5 minutes (so less is better). here is "4", 5 minutes before it
>>> was "1", so if I understood correctly the arrow should be red
>>> (pointing up).
>>> 
>>> Best,
>>> Stan
>>> 
>>> 2015-09-18 14:21 GMT+02:00 Edmundo Alvarez :
 Hi Stanislav,
 
 The "lower is better" option changes the used colour for arrows indicating 
 the trend. With that option enabled, arrows pointing down will be in 
 green, and arrows pointing up in red. I am not aware of any issues with 
 that feature, at least seems to be working in 1.2.0. Could you please 
 upgrade to 1.2.0 and see if the problem disappears?
 
 In other case, please attach an screenshot of the problem, and the 
 configuration of the widget (you get it by clicking on the info button on 
 the bottom-right corner of the widget).
 
 Regards,
 
 Edmundo
 
> On 17 Sep 2015, at 18:18, Stanislav Kopp  wrote:
> 
> Hi all,
> 
> I have a question about trends in dashboard, I've activated trend for 
> simple logs counter with option "Lower is better", but no matter if 
> number of logs is lower or higher, it always remains "green". Did I 
> misunderstood this feature or it is something wrong with my setup?
> 
> I'm using Graylog 1.1.4
> 
> Thanks,
> Stan
> 
> --
> 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 graylog2+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/graylog2/c186a534-3577-4455-9a5c-5c4876a75fb0%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 "Graylog Users" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/graylog2/rgagiaf8MgM/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 graylog2+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/graylog2/3FF40F9E-94B6-4586-9C93-3CA575A83222%40graylog.com.
 For more options, visit https://groups.google.com/d/optout.
>>> 
>>> --
>>> 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 graylog2+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit 
>>>

[graylog2] Search issues after update to 1.2

2015-09-21 Thread Arkadiy Shinkarev

Hi!

I have search issues after update Graylog to 1.2.
I able to search data only in current index.
Actually, previous indexes contain all data (I see them when perform query 
to elastic).

I tryed to recalculate index range, but there is no luck.

Any suggestions?

ES: 1.3.4
Graylog (server, web): 1.2

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/bf0b7ea0-313e-492a-93a8-aa818dce9a60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Search issues after update to 1.2

2015-09-21 Thread Arkadiy Shinkarev

Thanks for your reply!

There is no error messages in logs at all.

$  curl -XGET 
'http://m1-gl-es01:9200/graylog2_*/index_range/_search?pretty=true'

  "took" : 38,
  "timed_out" : false,
  "_shards" : {
"total" : 40,
"successful" : 40,
"failed" : 0
  },
  "hits" : {
"total" : 20,
"max_score" : 1.0,
"hits" : [ {
  "_index" : "graylog2_25",
  "_type" : "index_range",
  "_id" : "graylog2_25",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_25","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-17T21:06:14.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:01:29.000Z","gl2_index_range_took_ms":4191}
}, {
  "_index" : "graylog2_27",
  "_type" : "index_range",
  "_id" : "graylog2_27",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_27","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-26T22:43:14.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:01:09.000Z","gl2_index_range_took_ms":10686}
}, {
  "_index" : "graylog2_29",
  "_type" : "index_range",
  "_id" : "graylog2_29",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_29","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-07-07T09:06:05.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:00:45.000Z","gl2_index_range_took_ms":7077}
}, {
  "_index" : "graylog2_30",
  "_type" : "index_range",
  "_id" : "graylog2_30",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_30","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-07-11T21:37:45.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:00:35.000Z","gl2_index_range_took_ms":14713}
}, {
  "_index" : "graylog2_32",
  "_type" : "index_range",
  "_id" : "graylog2_32",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_32","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-07-22T05:26:06.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:01:33.000Z","gl2_index_range_took_ms":3401}
}, {
  "_index" : "graylog2_34",
  "_type" : "index_range",
  "_id" : "graylog2_34",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_34","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-08-01T16:14:17.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:00:58.000Z","gl2_index_range_took_ms":2560}
}, {
  "_index" : "graylog2_36",
  "_type" : "index_range",
  "_id" : "graylog2_36",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_36","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-08-13T10:29:23.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:02:12.000Z","gl2_index_range_took_ms":4309}
}, {
  "_index" : "graylog2_38",
  "_type" : "index_range",
  "_id" : "graylog2_38",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_38","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-08-26T06:34:49.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:02:01.000Z","gl2_index_range_took_ms":7399}
}, {
  "_index" : "graylog2_41",
  "_type" : "index_range",
  "_id" : "graylog2_41",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_41","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-09-12T22:58:39.000Z","gl2_index_range_
calculated_at":"2015-09-12T23:00:38.000Z","gl2_index_range_took_ms":2912}
}, {
  "_index" : "graylog2_43",
  "_type" : "index_range",
  "_id" : "graylog2_43",
  "_score" : 1.0,
  
"_source":{"gl2_index_range_index_name":"graylog2_43","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"1970-01-01T00:00:00.000Z","gl2_index_range_
calculated_at":"2015-09-19T13:04:36.210Z","gl2_index_range_took_ms":8}
} ]
  }
}

On Monday, September 21, 2015 at 11:56:08 AM UTC+3, Jochen Schalanda wrote:
>
> Hi Arkadiy,
>
> are there any related error messages in your Graylog server node's logs?
>
> Additionally, please post the output of the following cURL command 
> (replace "localhost" with the hostname or IP address of one of your 
> Elasticsearch nodes, and "graylog2_*" with your actual index prefix):
>
> curl -XGET '
> http://localhost:9200/graylog2_*/index_range/_search?pretty=true'
>
>
>
> Cheers,
> Jochen
>
> On Monday, 21 September 2015 10:45:40 UTC+2, Arkadiy Shinkarev wrote:
>>
>> Hi!
>>
>> I have search issues after update Graylog to 1.2.
>> I able to search data only in current index.
>> Actually, previous indexes contain all data (I see them when perform 
>> query to elastic).
>>
>> I tryed to recalculate index range, but there is no luck.
>>
>> Any suggestions?
>>
>> ES: 1.3.4
>> Graylog

[graylog2] Re: Search issues after update to 1.2

2015-09-21 Thread Arkadiy Shinkarev

Current index is graylog2_44

On Monday, September 21, 2015 at 11:58:19 AM UTC+3, Arkadiy Shinkarev wrote:
>
> Thanks for your reply!
>
> There is no error messages in logs at all.
>
> $  curl -XGET '
> http://m1-gl-es01:9200/graylog2_*/index_range/_search?pretty=true'
>
>   "took" : 38,
>   "timed_out" : false,
>   "_shards" : {
> "total" : 40,
> "successful" : 40,
> "failed" : 0
>   },
>   "hits" : {
> "total" : 20,
> "max_score" : 1.0,
> "hits" : [ {
>   "_index" : "graylog2_25",
>   "_type" : "index_range",
>   "_id" : "graylog2_25",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_25","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-17T21:06:14.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:01:29.000Z","gl2_index_range_took_ms":4191}
> }, {
>   "_index" : "graylog2_27",
>   "_type" : "index_range",
>   "_id" : "graylog2_27",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_27","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-06-26T22:43:14.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:01:09.000Z","gl2_index_range_took_ms":10686}
> }, {
>   "_index" : "graylog2_29",
>   "_type" : "index_range",
>   "_id" : "graylog2_29",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_29","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-07-07T09:06:05.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:00:45.000Z","gl2_index_range_took_ms":7077}
> }, {
>   "_index" : "graylog2_30",
>   "_type" : "index_range",
>   "_id" : "graylog2_30",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_30","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-07-11T21:37:45.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:00:35.000Z","gl2_index_range_took_ms":14713}
> }, {
>   "_index" : "graylog2_32",
>   "_type" : "index_range",
>   "_id" : "graylog2_32",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_32","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-07-22T05:26:06.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:01:33.000Z","gl2_index_range_took_ms":3401}
> }, {
>   "_index" : "graylog2_34",
>   "_type" : "index_range",
>   "_id" : "graylog2_34",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_34","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-08-01T16:14:17.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:00:58.000Z","gl2_index_range_took_ms":2560}
> }, {
>   "_index" : "graylog2_36",
>   "_type" : "index_range",
>   "_id" : "graylog2_36",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_36","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-08-13T10:29:23.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:02:12.000Z","gl2_index_range_took_ms":4309}
> }, {
>   "_index" : "graylog2_38",
>   "_type" : "index_range",
>   "_id" : "graylog2_38",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_38","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-08-26T06:34:49.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:02:01.000Z","gl2_index_range_took_ms":7399}
> }, {
>   "_index" : "graylog2_41",
>   "_type" : "index_range",
>   "_id" : "graylog2_41",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_41","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"2015-09-12T22:58:39.000Z","gl2_index_range_
> calculated_at":"2015-09-12T23:00:38.000Z","gl2_index_range_took_ms":2912}
> }, {
>   "_index" : "graylog2_43",
>   "_type" : "index_range",
>   "_id" : "graylog2_43",
>   "_score" : 1.0,
>   
> "_source":{"gl2_index_range_index_name":"graylog2_43","gl2_index_range_begin":"1970-01-01T00:00:00.000Z","gl2_index_range_end":"1970-01-01T00:00:00.000Z","gl2_index_range_
> calculated_at":"2015-09-19T13:04:36.210Z","gl2_index_range_took_ms":8}
> } ]
>   }
> }
>
> On Monday, September 21, 2015 at 11:56:08 AM UTC+3, Jochen Schalanda wrote:
>>
>> Hi Arkadiy,
>>
>> are there any related error messages in your Graylog server node's logs?
>>
>> Additionally, please post the output of the following cURL command 
>> (replace "localhost" with the hostname or IP address of one of your 
>> Elasticsearch nodes, and "graylog2_*" with your actual index prefix):
>>
>> curl -XGET '
>> http://localhost:9200/graylog2_*/index_range/_search?pretty=true'
>>
>>
>>
>> Cheers,
>> Jochen
>>
>> On Monday, 21 September 2015 10:45:40 UTC+2, Arkadiy Shinkarev

Re: [graylog2] Encoding problem in email alert callback.

2015-09-21 Thread Alexander Ivanes

Hi.
Thanks for the reply, Edmundo.
I've opened an issue with some additional info.
Here's the link: https://github.com/Graylog2/graylog2-server/issues/1435

Regards,
Alexander.

On Friday, September 18, 2015 at 5:09:50 PM UTC+3, Edmundo Alvarez wrote:
>
> Hi Alexander, 
>
> Could you please open an issue in Github 
> https://github.com/Graylog2/graylog2-server/issues? Please include an 
> example log message, so we can test it more easily. 
>
> Thank you, 
>
> Edmundo 
>
> > On 17 Sep 2015, at 18:33, Alexander Ivanes  > wrote: 
> > 
> > Hello! 
> > 
> > We have a standard email callback configuration: 
> > 
> > body: 
> > ## 
> > Alert Description: ${check_result.resultDescription} 
> > Date: ${check_result.triggeredAt} 
> > Stream ID: ${stream.id} 
> > Stream title: ${stream.title} 
> > Stream description: ${stream.description} 
> > ${if stream_url}Stream URL: ${stream_url}${end} 
> > Triggered condition: ${check_result.triggeredCondition} 
> > ## 
> > ${if backlog}Last messages accounting for this alert: 
> > ${foreach backlog message}${message} 
> > ${end}${else} 
> > ${end} 
> > 
> > sender: 
> > graylog@*** 
> > 
> > subject: 
> > Graylog alert for stream: ${stream.title}: 
> ${check_result.resultDescription} 
> > 
> > 
> > Everything works fine, except that ${message} contain question marks 
> instead of cyrillic symbols. 
> > 
> > From graylog stream documentation: 
> > 
> > message (only available via iteration over the backlog object) 
> > The message object has several fields with details about the message. 
> When using the message object without accessing any fields, the toString() 
> method of the underlying Java object is used to display it. 
> > 
> > I think that problem is in the toString() method, that doesn't work with 
> unicode. 
> > 
> > Is there any way to solve this problem? JMTE magic maybe? 
> > 
> > Thanks in advance. 
> > 
> > Alexander. 
> > 
> > 
> > 
> > -- 
> > 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 graylog2+u...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/graylog2/53519954-d73e-4351-b3b9-3300a06b94af%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/24196c9b-1b54-44e6-a26b-0468d5a518b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Search issues after update to 1.2

2015-09-21 Thread Jochen Schalanda

Hi Arkadiy,

are there any related error messages in your Graylog server node's logs?

Additionally, please post the output of the following cURL command (replace 
"localhost" with the hostname or IP address of one of your Elasticsearch 
nodes, and "graylog2_*" with your actual index prefix):

curl -XGET 
'http://localhost:9200/graylog2_*/index_range/_search?pretty=true'



Cheers,
Jochen

On Monday, 21 September 2015 10:45:40 UTC+2, Arkadiy Shinkarev wrote:
>
> Hi!
>
> I have search issues after update Graylog to 1.2.
> I able to search data only in current index.
> Actually, previous indexes contain all data (I see them when perform query 
> to elastic).
>
> I tryed to recalculate index range, but there is no luck.
>
> Any suggestions?
>
> ES: 1.3.4
> Graylog (server, web): 1.2
>

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/157aac71-1b33-4733-922f-05b565eae043%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Search issues after update to 1.2

[graylog2] Re: Search issues after update to 1.2

Re: [graylog2] graylog2-web-interface - build_release.sh fails today

[graylog2] Re: Search issues after update to 1.2

[graylog2] Graylog SSl configuration query.

[graylog2] Re: Search issues after update to 1.2

Re: [graylog2] Graylog plugin - elastic field types

Re: [graylog2] Trends presentation in dashboard

[graylog2] Search issues after update to 1.2

[graylog2] Re: Search issues after update to 1.2

[graylog2] Re: Search issues after update to 1.2

Re: [graylog2] Encoding problem in email alert callback.

[graylog2] Re: Search issues after update to 1.2

13 matches

Site Navigation

Mail list logo

Footer information