[graylog2] Building graylog2 from source fails for proprietary sun.security.x509.CertificateAlgorithmId

[Tech Id]

Hi,

I am trying to build graylog2 from source.

git remote -v

origin https://github.com/Graylog2/graylog2-server (fetch)

origin https://github.com/Graylog2/graylog2-server (push)


And I am building from the 'master' branch (updated today).


On giving the command 'mvn clean install', build fails with 'package 
org.apache.lucene.analysis.standard does not exist'

So I add the maven dependency:



org.apache.lucene

lucene-analyzers-common

5.4.0




Then it fails as: 

[ERROR] symbol:   class ParseException

[ERROR] location: package org.apache.lucene.queryparser.classic

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/rest/resources/search/SearchResource.java:[24,45]
 
cannot find symbol

[ERROR] symbol:   class QueryParser

[ERROR] location: package org.apache.lucene.queryparser.classic

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/rest/resources/search/SearchResource.java:[25,45]
 
cannot find symbol

[ERROR] symbol:   class Token

[ERROR] location: package org.apache.lucene.queryparser.classic


For which I have to add:



org.apache.lucene

lucene-queryparser

5.4.0





Third time, it fails with 'package com.carrotsearch.hppc.cursors does not 
exist'

For which I add:



com.carrotsearch

hppc

0.3.4





I also have to add:

org.scala-lang
scala-library
2.10.0-M3



Finally, it is now failing as: 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.3:compile 
(default-compile) on project graylog2-server: Compilation failure: 
Compilation failure:

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[21,25]
 
sun.security.x509.AlgorithmId is internal proprietary API and may be 
removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[22,25]
 
sun.security.x509.CertificateAlgorithmId is internal proprietary API and 
may be removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[23,25]
 
sun.security.x509.CertificateIssuerName is internal proprietary API and may 
be removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[24,25]
 
sun.security.x509.CertificateSerialNumber is internal proprietary API and 
may be removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[25,25]
 
sun.security.x509.CertificateSubjectName is internal proprietary API and 
may be removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[26,25]
 
sun.security.x509.CertificateValidity is internal proprietary API and may 
be removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[27,25]
 
sun.security.x509.CertificateVersion is internal proprietary API and may be 
removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[28,25]
 
sun.security.x509.CertificateX509Key is internal proprietary API and may be 
removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[29,25]
 
sun.security.x509.X500Name is internal proprietary API and may be removed 
in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[30,25]
 
sun.security.x509.X509CertImpl is internal proprietary API and may be 
removed in a future release

[ERROR] 
graylog2-server/graylog2-server/src/main/java/org/graylog2/shared/security/tls/SelfSignedCertificate.java:[31,25]
 
sun.security.x509.X509CertInfo is internal proprietary API and may be 
removed in a future release


And I am stuck at this point.


Is this a problem with building graylog from source?

Or I am doing something wrong?

Do I need to specify some maven profile or option to build this?


Any help appreciated.



I need to build graylog2 from sources because it's crashing with our kafka 
input and we need to debug this.

I will submit a pull request for build/documentation to save others 
sometime once it builds up cleanly for myself.


Thanks !



-- 
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/54aa1ebc-d6a9-407a-93a0-92c1be95c7f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Building graylog2 from source fails for proprietary sun.security.x509.CertificateAlgorithmId

[Tech Id]

I also see an exception:



$ java -version

java version "1.8.0_71"

Java(TM) SE Runtime Environment (build 1.8.0_71-b15)

Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)


$ mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V



[INFO] Compiling 1065 source files to 
graylog2-server/graylog2-server/target/classes


An exception has occurred in the compiler (1.8.0_71). Please file a bug at 
the Java Bug Database (http://bugreport.java.com/bugreport/) after checking 
the database for duplicates. Include your program and the following 
diagnostic in your report.  Thank you.


java.lang.IllegalStateException: endPosTable already set

at 
com.sun.tools.javac.util.DiagnosticSource.setEndPosTable(DiagnosticSource.java:136)

at com.sun.tools.javac.util.Log.setEndPosTable(Log.java:350)

at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:667)

at com.sun.tools.javac.main.JavaCompiler.parseFiles(JavaCompiler.java:950)

at 
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:892)

at 
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.next(JavacProcessingEnvironment.java:921)

at 
com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1187)

at 
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)

at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)

at com.sun.tools.javac.main.Main.compile(Main.java:523)

at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)

at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)

at 
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125)

at 
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)

at 
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:825)

at 
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)

at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)




-- 
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/3633b118-e31c-4175-be56-8e7e9499b407%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Does Graylog2 have an input that reads from Kafka?

[Tech Id]

Thanks Jason,

I finally found it in the system->inputs on the browser UI for graylog.

I think it would be good to mention that somewhere in the documentation as 
well.
Perhaps just a mention of all the supported types in the docs would make it 
google friendly and hence easily searchable.

-- 
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/33e5f9b3-900f-4788-9af9-f62a4f70f4ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Building graylog2 from source fails for proprietary sun.security.x509.CertificateAlgorithmId

[Tech Id]

This exception looks similar 
to http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8067747

But I want to know how graylog is being built by the graylog community.
Are they using Java 7 or OpenJDK or something else?

Is it possible to fix this such that it works with Oracle JDK 8 too?

-- 
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/0d2f4419-0507-4d04-830f-963906a9fdda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: Web interface not connecting, mongodb down

[Jochen Schalanda]

Hi Obie,

whatever works better for you. FWIW, I think the MongoDB upgrade process 
should be quite painless and fast (since Graylog doesn't store much data in 
MongoDB).


Cheers,
Jochen

On Tuesday, 9 February 2016 10:46:05 UTC+1, Obie wrote:
>
> No, haven't tried upgrading mongodb yet. I may just deploy a newer 
> appliance instead,
>

-- 
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/bbda36fa-84d1-4d52-b3ad-c16f16fc8112%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: Web interface not connecting, mongodb down

[Obie]

What would the db path be for the appliance? He are the upgrade results...

Thanks


ubuntu@graylog:/opt/graylog/mongodb/bin$ ./mongod --upgrade
2016-02-09T05:05:06.225-0500 [initandlisten] MongoDB starting : pid=8587 
port=27017 dbpath=/data/db 64-bit host=graylog
2016-02-09T05:05:06.225-0500 [initandlisten] db version v2.6.4
2016-02-09T05:05:06.225-0500 [initandlisten] git version: 
3a830be0eb92d772aa855ebb711ac91d658ee9102016-02-09T05:05:06.225-0500 
[initandlisten] build info: Linux build7.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 
#1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2016-02-09T05:05:06.225-0500 [initandlisten] allocator: tcmalloc
2016-02-09T05:05:06.225-0500 [initandlisten] options: { upgrade: true }
2016-02-09T05:05:06.305-0500 [initandlisten] exception in initAndListen: 10296
*
 ERROR: dbpath (/data/db) does not exist.
 Create this directory or give existing directory in --dbpath.
 See http://dochub.mongodb.org/core/startingandstoppingmongo
*
, terminating
2016-02-09T05:05:06.306-0500 [initandlisten] dbexit:

-- 
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/8476123c-6328-4015-9e65-dd2d0ae55caf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: Web interface not connecting, mongodb down

[Obie]

Well... It's been so long since I configured this that I forgot the db path was 
changed to mounted NFS. I applied that mount point as the db path and was able 
to start all processes.

Thanks!

-- 
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/f292cd72-ad25-432a-9fd3-671b06e5211d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Web interface not connecting, mongodb down

[Jochen Schalanda]

Hi Obie,

did you try upgrading the MongoDB data files as the message suggested? This 
is necessary when you upgrade from an old MongoDB version (before 3.0) to 
MongoDB 3.0.


Cheers,
Jochen

On Monday, 8 February 2016 23:37:21 UTC+1, Obie wrote:
>
> Here's some log info...
>
> 2016-02-08_21:41:56.23058 2016-02-08T16:41:56.230-0500 [initandlisten] 
> MongoDB starting : pid=13559 port=27017 
> dbpath=/var/opt/graylog/data/mongodb 64-bit host=graylog
> 2016-02-08_21:41:56.23069 2016-02-08T16:41:56.230-0500 [initandlisten] db 
> version v2.6.4
> 2016-02-08_21:41:56.23072 2016-02-08T16:41:56.230-0500 [initandlisten] git 
> version: 3a830be0eb92d772aa855ebb711ac91d658ee910
> 2016-02-08_21:41:56.23075 2016-02-08T16:41:56.230-0500 [initandlisten] 
> build info: Linux build7.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP 
> Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
> 2016-02-08_21:41:56.23078 2016-02-08T16:41:56.230-0500 [initandlisten] 
> allocator: tcmalloc
> 2016-02-08_21:41:56.23081 2016-02-08T16:41:56.230-0500 [initandlisten] 
> options: { storage: { dbPath: "/var/opt/graylog/data/mongodb" } }
> 2016-02-08_21:41:56.23237 2016-02-08T16:41:56.232-0500 [initandlisten] 
> journal dir=/var/opt/graylog/data/mongodb/journal
> 2016-02-08_21:41:56.23257 2016-02-08T16:41:56.232-0500 [initandlisten] 
> recover : no journal files present, no recovery needed
> 2016-02-08_21:41:56.23709 2016-02-08T16:41:56.237-0500 [initandlisten] 
> 2016-02-08_21:41:56.23712 2016-02-08T16:41:56.237-0500 [initandlisten] 
> 2016-02-08_21:41:56.23715 2016-02-08T16:41:56.237-0500 [initandlisten] 
> need to upgrade database local with pdfile version 4.21, new version: 4.5
> 2016-02-08_21:41:56.23718 2016-02-08T16:41:56.237-0500 [initandlisten]   
> Not upgrading, exiting
> 2016-02-08_21:41:56.23721 2016-02-08T16:41:56.237-0500 [initandlisten]   
> run --upgrade to upgrade dbs, then start again
> 2016-02-08_21:41:56.23723 2016-02-08T16:41:56.237-0500 [initandlisten] 
> 2016-02-08_21:41:56.23726 2016-02-08T16:41:56.237-0500 [initandlisten] 
> dbexit: 
> 2016-02-08_21:41:56.23729 2016-02-08T16:41:56.237-0500 [initandlisten] 
> shutdown: going to close listening sockets...
> 2016-02-08_21:41:56.23732 2016-02-08T16:41:56.237-0500 [initandlisten] 
> shutdown: going to flush diaglog...
> 2016-02-08_21:41:56.23734 2016-02-08T16:41:56.237-0500 [initandlisten] 
> shutdown: going to close sockets...
> 2016-02-08_21:41:56.23741 2016-02-08T16:41:56.237-0500 [initandlisten] 
> shutdown: waiting for fs preallocator...
> 2016-02-08_21:41:56.23744 2016-02-08T16:41:56.237-0500 [initandlisten] 
> shutdown: lock for final commit...
> 2016-02-08_21:41:56.23747 2016-02-08T16:41:56.237-0500 [initandlisten] 
> shutdown: final commit...
> 2016-02-08_21:41:56.23751 2016-02-08T16:41:56.237-0500 [initandlisten] 
> shutdown: closing all files...
> 2016-02-08_21:41:56.23762 2016-02-08T16:41:56.237-0500 [initandlisten] 
> closeAllFiles() finished
> 2016-02-08_21:41:56.23769 2016-02-08T16:41:56.237-0500 [initandlisten] 
> journalCleanup...
> 2016-02-08_21:41:56.23772 2016-02-08T16:41:56.237-0500 [initandlisten] 
> removeJournalFiles
> 2016-02-08_21:41:56.24015 2016-02-08T16:41:56.240-0500 [initandlisten] 
> shutdown: removing fs lock...
> 2016-02-08_21:41:56.24058 2016-02-08T16:41:56.240-0500 [initandlisten] 
> dbexit: really exiting now
>
>>
>>

-- 
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/941f3b93-6c9d-46ae-b9ff-f6f328e6db54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Does Graylog2 have an input that reads from Kafka?

[Jochen Schalanda]

Hi,

as a matter of fact, Graylog supports ingesting messages from Apache Kafka 
out-of-the-box. The message payload can be simple plaintext, syslog 
messages, or GELF messages.

There is no exhaustive documentation about the Kafka inputs but you should 
be able to simply create those inputs in your Graylog installation and fill 
out the configuration just fine.


Cheers,
Jochen


On Monday, 8 February 2016 23:34:53 UTC+1, Tech Id wrote:
>
> Hi,
>
> We have lots of log-data being pumped into Kafka topics and it goes onto 
> Hadoop for Hive querying.
> Now we want to push the same into graylog2.
>
> So I was wondering if graylog2 has a kafka-reader-plugin (input) ?
> Please point me to the same if so.
>
> Thanks
> T.Id
>

-- 
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/4a7131ea-04d5-4f3f-b656-c4ba282bd46a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Graylog 2.0.0 alpha - can't log into web-gui

[Edmundo Alvarez]

Hi,

Thank you for your feedback!

There are many changes in 2.0, and one of them is that you need access to the 
Graylog server from your browser. Could you please execute 
"appConfig.gl2ServerUrl" in your JS console and verify that it is returning the 
right URI to connect to the Graylog server?

The web interface uses the URI set in the "rest_transport_uri" configuration 
option, so you may need to adapt it to make it work: 
https://github.com/Graylog2/graylog2-server/blob/master/misc/graylog.conf#L45

Regards,
Edmundo

> On 08 Feb 2016, at 19:02, thePretender  wrote:
> 
> - tar ball, not OVA
> - Yes, wasn't a problem with 1.3.2
> - No, tested with HTTPS with same result
> 
> This is the output from the console:
> 
> "Download the React DevTools for a better development experience: 
> https://fb.me/react-devtools; vendor.js:402:1688
> unreachable code after return statement app.f09f6a84a11bb9a40b39.js:4773:4
> unreachable code after return statement app.f09f6a84a11bb9a40b39.js line 7 > 
> eval:4773:4
> mutating the [[Prototype]] of an object will cause your code to run very 
> slowly; instead create the object with the correct initial [[Prototype]] 
> value using Object.create app.f09f6a84a11bb9a40b39.js line 1 > eval:19:415
> Password fields present on an insecure (http://) page. This is a security 
> risk that allows user login credentials to be stolen.[Learn More] 
> 
> -- 
> 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/1c732455-02ee-4c23-82af-d90eb2f0c717%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/D0A8B060-3867-4349-AD71-07214C73E782%40graylog.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Building graylog2 from source fails for proprietary sun.security.x509.CertificateAlgorithmId

[Tech Id]

ok, so looking at the JDK bug, if you do an install twice, this bug shows 
up.
So if I do clean install every time, this error should go away and it does !

But the maven dependencies still have to be added locally.


-- 
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/4e759c38-d183-45d0-8a5b-a4a3134e9f70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Graylog fails to start due to ElasticSearch crash

[nicocofo2]

Hello,
I'm testing Graylog solution.
This morning, when I came back to work, Graylog fails to start, 
Elasticsearch seems to be out.

Here's the ES start log :
[2016-02-10 08:34:45,931][INFO ][node ] [Moon-Boy] 
version[1.7.3], pid[4430], build[05d4530/2015-10-15T09:14:17Z]
[2016-02-10 08:34:45,932][INFO ][node ] [Moon-Boy] 
initializing ...
[2016-02-10 08:34:46,034][INFO ][plugins  ] [Moon-Boy] 
loaded [], sites []
[2016-02-10 08:34:46,073][INFO ][env  ] [Moon-Boy] 
using [1] data paths, mounts [[/ (rootfs)]], net usable_space [841.3gb], 
net total_space [901gb], types [rootfs]
[2016-02-10 08:34:48,498][INFO ][node ] [Moon-Boy] 
initialized
[2016-02-10 08:34:48,499][INFO ][node ] [Moon-Boy] 
starting ...
[2016-02-10 08:34:48,558][INFO ][transport] [Moon-Boy] 
bound_address {inet[/0.0.0.0:9300]}, publish_address 
{inet[/192.168.xxx.xxx:9300]}
[2016-02-10 08:34:48,566][INFO ][discovery] [Moon-Boy] 
graylog2/0DkFmDQqRxaD0LC5du8wrg
[2016-02-10 08:34:51,594][INFO ][cluster.service  ] [Moon-Boy] 
new_master 
[Moon-Boy][0DkFmDQqRxaD0LC5du8wrg][graylog][inet[/192.168.xxx.xxx:9300]]{master=true},
 
reason: zen-disco-join (elected_as_master)
[2016-02-10 08:34:51,616][INFO ][http ] [Moon-Boy] 
bound_address {inet[/0.0.0.0:9200]}, publish_address 
{inet[/192.168.xxx.xxx:9200]}
[2016-02-10 08:34:51,616][INFO ][node ] [Moon-Boy] 
started
[2016-02-10 08:34:51,666][INFO ][gateway  ] [Moon-Boy] 
recovered [1] indices into cluster_state
[2016-02-10 08:34:52,026][WARN ][indices.cluster  ] [Moon-Boy] 
[[graylog2_0][0]] marking and sending shard failed due to [failed recovery]
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: 
[graylog2_0][0] failed to fetch index version after copying it over
at 
org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:161)
at 
org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:112)
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)
Caused by: org.apache.lucene.index.CorruptIndexException: [graylog2_0][0] 
Preexisting corrupted index [corrupted_AXCaFkUiQgKLQJ_-3Ikqaw] caused by: 
IOException[failed engine (reason: [corrupt file detected source: [merge]])]
CorruptIndexException[checksum failed (hardware problem?) : 
expected=8f75bb00 actual=eb43241c 
(resource=BufferedChecksumIndexInput(_b8mh.fdt))]
java.io.IOException: failed engine (reason: [corrupt file detected source: 
[merge]])
at org.elasticsearch.index.engine.Engine.failEngine(Engine.java:492)
at 
org.elasticsearch.index.engine.InternalEngine$FailEngineOnMergeFailure.onFailedMerge(InternalEngine.java:1245)
at 
org.elasticsearch.index.merge.scheduler.MergeSchedulerProvider$1.run(MergeSchedulerProvider.java:103)
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)
Caused by: org.apache.lucene.index.CorruptIndexException: checksum failed 
(hardware problem?) : expected=8f75bb00 actual=eb43241c 
(resource=BufferedChecksumIndexInput(_b8mh.fdt))
at 
org.apache.lucene.codecs.CodecUtil.checkFooter(CodecUtil.java:211)
at 
org.apache.lucene.codecs.compressing.CompressingStoredFieldsReader$ChunkIterator.checkIntegrity(CompressingStoredFieldsReader.java:521)
at 
org.apache.lucene.codecs.compressing.CompressingStoredFieldsWriter.merge(CompressingStoredFieldsWriter.java:394)
at 
org.apache.lucene.index.SegmentMerger.mergeFields(SegmentMerger.java:332)
at 
org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:100)
at 
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:4223)
at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3811)
at 
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:409)
at 
org.apache.lucene.index.TrackingConcurrentMergeScheduler.doMerge(TrackingConcurrentMergeScheduler.java:107)
at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:486)

at 
org.elasticsearch.index.store.Store.failIfCorrupted(Store.java:602)
at 
org.elasticsearch.index.store.Store.failIfCorrupted(Store.java:583)
at 
org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:124)
... 4 more
[2016-02-10 08:34:52,029][WARN ][cluster.action.shard ] [Moon-Boy] 
[graylog2_0][0] received