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
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
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
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
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
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]
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
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
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,
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" :
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,
>
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
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):
13 matches
Mail list logo