Can't running elasticsearch after update ubuntu and java

[longcnttbkhn]

Describe the feature: I can't running elasticsearch after update ubuntu and java

Elasticsearch version (bin/elasticsearch --version): 2.4.1

Plugins installed: []

JVM version (java -version): OpenJDK 1.8.0_151

OS version (uname -a if on a Unix-like system): Linux 4.13.0-31-generic #34~16.04.1-Ubuntu x86_64 GNU/Linux

Description of the problem including expected versus actual behavior: Normally I can run elasticsearch with the ./elasticsearch command. But this morning, after updating ubuntu and java, I was not able to boot up elasticsearch anymore.

[jpountz]

Please describe the problem you are having, otherwise it's very hard to help.

[exorbit]

I have the same problem since OS update this morning. Befor the update all was fine.

Elasticsearch version (bin/elasticsearch --version): 2.4.6

JVM version (java -version): 1.8.0_131

OS version (uname -a if on a Unix-like system): Linux dellXPS 4.13.0-31-generic #34-Ubuntu 17.10

Description of the problem including expected versus actual behavior:
./elasticsearch did nothing. No message, no log entry.

I noticed that with the update also an update of intels microcode was installed:
intel-microcode 3.20180108.0+really20170707ubuntu17.10.1

[simonwillnauer]

can you folks give us some logging information otherwise everything is a shot in the dark

[exorbit]

There is no logging anymore. I start ./elasticsearch in a terminal and after a second it comes back without any messages. Logfiles are empty also with DEBUG.
I also tried without any java params: /usr/lib/jvm/java-8-oracle/bin/java -Dfile.encoding=UTF-8 -Des.path.home=/home/xxx/elasticsearch-2.4.6 -cp /home/xxx/programs/elasticsearch-2.4.6/lib/elasticsearch-2.4.6.jar:/home/xxx/elasticsearch-2.4.6/lib/* org.elasticsearch.bootstrap.Elasticsearch start without message

[reggieb]

Sorry - when I started writing my bug report there was only the first entry and I wasn't sure this was the same bug. But looking at the two more recent entries, I think it is. I do have a related system log error. See #28354

[jasontedor]

I think you should check your kernel log messages (e.g., dmesg).

[exorbit]

Yep, this is the same issue with the same kernel output.
So, meltdown has killed my ES!

[jasontedor]

Sorry, this is not an Elasticsearch issue then. I suggest rolling back your kernel.

[exorbit]

I also suspect the microcode update from intel is involved.

[longcnttbkhn]

Thank for your support! But I used docker elasticsearch instead, hoping to fix the kenel soon.

[jasontedor]

The kernel is that of your underlying host, it does not have anything to do with the image.

[dadoonet]

For the record, another report of this here: https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865