ES 2.1.0 error


(Vikas Gopal) #1

Hi Experts,

While starting ES I am getting following error . Right now I do not have any index in this new setup Except .kibana as I was trying to open kibana 4.3.0 .

[2015-12-02 12:44:35,451][WARN ][index.translog ] [Morg] [.kibana][0] failed to delete temp file E:\ELK_Traning\latest\elasticsearch-2.1.0\data\elasticsearch\nodes\0\indices.kibana\0\translog\translog-7135799924942567525.tlog
java.nio.file.NoSuchFileException: E:\ELK_Traning\latest\elasticsearch-2.1.0\data\elasticsearch\nodes\0\indices.kibana\0\translog\translog-7135799924942567525.tlog
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
at sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269)
at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103)
at java.nio.file.Files.delete(Files.java:1126)
at org.elasticsearch.index.translog.Translog.recoverFromFiles(Translog.java:324)
at org.elasticsearch.index.translog.Translog.(Translog.java:166)
at org.elasticsearch.index.engine.InternalEngine.openTranslog(InternalEngine.java:209)
at org.elasticsearch.index.engine.InternalEngine.(InternalEngine.java:152)
at org.elasticsearch.index.engine.InternalEngineFactory.newReadWriteEngine(InternalEngineFactory.java:25)
at org.elasticsearch.index.shard.IndexShard.newEngine(IndexShard.java:1408)
at org.elasticsearch.index.shard.IndexShard.createNewEngine(IndexShard.java:1403)
at org.elasticsearch.index.shard.IndexShard.internalPerformTranslogRecovery(IndexShard.java:906)
at org.elasticsearch.index.shard.IndexShard.performTranslogRecovery(IndexShard.java:883)
at org.elasticsearch.index.shard.StoreRecoveryService.recoverFromStore(StoreRecoveryService.java:245)
at org.elasticsearch.index.shard.StoreRecoveryService.access$100(StoreRecoveryService.java:56)
at org.elasticsearch.index.shard.StoreRecoveryService$1.run(StoreRecoveryService.java:129)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)


(David Pilato) #2

You can ignore this message. Will be fixed in 2.1.1.


(Vikas Gopal) #3

Thanks Dadoonet,

But I guess because of this issue kibana 4.3.0 is misbehaving. Kibana is keep on searching .kibana index or any other index if created . As you said I ignored this error and created a fresh index . Now when I am trying to search this in kibana , it pics the name but it's keep on processing untill the page throws a fatal error .

Courier Fetch Error: unhandled error Error: unknown error

at respond (http://localhost:5601/bundles/kibana.bundle.js:76162:16)
at checkRespForFailure (http://localhost:5601/bundles/kibana.bundle.js:76123:8)
at http://localhost:5601/bundles/kibana.bundle.js:74741:8
at processQueue (http://localhost:5601/bundles/commons.bundle.js:42339:29)
at http://localhost:5601/bundles/commons.bundle.js:42355:28
at Scope.$eval (http://localhost:5601/bundles/commons.bundle.js:43583:29)
at Scope.$digest (http://localhost:5601/bundles/commons.bundle.js:43394:32)
at Scope.$apply (http://localhost:5601/bundles/commons.bundle.js:43691:25)
at done (http://localhost:5601/bundles/commons.bundle.js:38140:48)
at completeRequest (http://localhost:5601/bundles/commons.bundle.js:38338:8)
Version: 4.3.0
Build: 9369


(Vikas Gopal) #4

what I feel is this issue and Problem in Kibana 4.2.1 both are related.
I have created the above thread for kibana actually .


(David Pilato) #5

I don't think it's related.

BTW the PR which fixed the "issue" is https://github.com/elastic/elasticsearch/pull/14872


(David F.) #6

I 've the same error


(system) #7