SearchService.Failed to commit index changes, error: java.io.IOException: The specified network name is no longer available

Helo everyone,

We're in progress of migration our teamcity server. The new one has been spitting out this error frequently:

[2014-04-22 15:53:40,167]  ERROR -   jetbrains.buildServer.SERVER - SearchService.Failed to commit index changes, error: java.io.IOException: The specified network name is no longer available
java.io.IOException: The specified network name is no longer available
    at java.io.RandomAccessFile.readBytes0(Native Method)
    at java.io.RandomAccessFile.readBytes(RandomAccessFile.java:350)
    at java.io.RandomAccessFile.read(RandomAccessFile.java:385)
    at org.apache.lucene.store.SimpleFSDirectory$SimpleFSIndexInput.readInternal(SimpleFSDirectory.java:132)
    at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:157)
    at org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:38)
    at org.apache.lucene.store.IndexInput.readVInt(IndexInput.java:80)
    at org.apache.lucene.index.TermBuffer.read(TermBuffer.java:64)
    at org.apache.lucene.index.SegmentTermEnum.next(SegmentTermEnum.java:129)
    at org.apache.lucene.index.SegmentTermEnum.scanTo(SegmentTermEnum.java:160)
    at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:232)
    at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:179)
    at org.apache.lucene.index.SegmentTermDocs.seek(SegmentTermDocs.java:57)
    at org.apache.lucene.index.DocumentsWriter.applyDeletes(DocumentsWriter.java:984)
    at org.apache.lucene.index.DocumentsWriter.applyDeletes(DocumentsWriter.java:956)
    at org.apache.lucene.index.IndexWriter.applyDeletes(IndexWriter.java:5190)
    at org.apache.lucene.index.IndexWriter.doFlushInternal(IndexWriter.java:4354)
    at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:4192)
    at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:4183)
    at org.apache.lucene.index.IndexWriter.prepareCommit(IndexWriter.java:4073)
    at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:4136)
    at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:4114)
    at jetbrains.buildServer.serverSide.search.LuceneIndex.releaseWriter(LuceneIndex.java:141)
    at jetbrains.buildServer.serverSide.search.SearchService.applyChanges(SearchService.java:483)
    at jetbrains.buildServer.serverSide.search.BackgroundIndexer$1.run(BackgroundIndexer.java:43)
    at jetbrains.buildServer.serverSide.impl.cleanup.ServerCleanupManagerImpl.executeWithInactiveCleanup(ServerCleanupManagerImpl.java:55)
    at jetbrains.buildServer.serverSide.impl.cleanup.ServerCleanupManagerImpl$$FastClassByCGLIB$$ba2c8525.invoke(<generated>)
    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
    at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:688)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
    at jetbrains.buildServer.serverSide.impl.auth.TeamCityMethodSecurityInterceptor.invoke(TeamCityMethodSecurityInterceptor.java:21)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
    at org.springframework.aop.framework.Cglib2AopProxy$FixedChainStaticTargetInterceptor.intercept(Cglib2AopProxy.java:572)
    at jetbrains.buildServer.serverSide.impl.cleanup.ServerCleanupManagerImpl$$EnhancerByCGLIB$$a8fb8f3.executeWithInactiveCleanup(<generated>)
    at jetbrains.buildServer.serverSide.search.BackgroundIndexer.run(BackgroundIndexer.java:41)
    at java.lang.Thread.run(Thread.java:744)


At first, I thought this was related to unavailability of the data directory, but after testing the availability of this it became clear that this wasn't the problem.
The teamcity server has been running and building stuff for a few weeks now, and this error doesn't seems to have any impact on the proper functioning of teamcity or the builds.
However, having an error in the log files is never good. Does anyone knows what can be the cause of this error?
(Full teamcity-server log in attachment)

Regards,

Projan



Attachment(s):
teamcity-server.log.zip
1 comment
Comment actions Permalink

Judging from your log, it's definetely something with shared network directory TC data directory points to. There are a lot of exceptions in log related to it.

We don't recommend putting data directory on a remote folder: http://confluence.jetbrains.com/display/TCD8/TeamCity+Data+Directory. TC uses data directory quite extensively (caches, logs, etc.). It's better to have data directory local with, for instance, rsync to remote location for backup purposes.

0

Please sign in to leave a comment.