It seems like the most common cause for this is incorrect file permissions 
on the store files. Have you checked these?

https://neo4j.com/developer/kb/how-to-fix-cannot-close-the-pagecache-while-files-are-still-mapped/

Rik

On Tuesday, June 9, 2015 at 1:02:26 AM UTC+2, Péterson Sampaio Procópio 
Júnior wrote:
>
> Hello all,
>
> after what was probably a wrong shutdown, I am failing to start Neo4j 
> server. The error occurred in the 2.2.0 windows version of Neo4j. I 
> upgraded to 2.2.2, but it still remains.
> The relevant log message follows below. I think the error is related, as 
> the message says, to the cache mechanism.
>
>
> 2015-06-08 19:48:05.251+0000 ERROR [o.n.s.d.LifecycleManagingDatabase]: 
>> Failed to start database.
>> org.neo4j.kernel.lifecycle.LifecycleException: Failed to transition 
>> component 'org.neo4j.kernel.impl.pagecache.PageCacheLifecycle@5f8dbdab' 
>> from STOPPED to SHUTTING_DOWN. Please see attached cause exception
>> ...
>> Caused by: java.lang.IllegalStateException: Cannot close the PageCache 
>> while files are still mapped:
>>     neostore.propertystore.db.index (1 mapping)
>>     neostore.propertystore.db.index.keys (1 mapping)
>>     neostore.labeltokenstore.db (1 mapping)
>>     neostore.labeltokenstore.db.names (1 mapping)
>>     neostore.relationshiptypestore.db (1 mapping)
>>     neostore.relationshiptypestore.db.names (1 mapping)
>>     at 
>> org.neo4j.io.pagecache.impl.muninn.MuninnPageCache.close(MuninnPageCache.java:483)
>>  
>> ~[neo4j-io-2.2.2.jar:2.2.2]
>>     at 
>> org.neo4j.kernel.impl.pagecache.PageCacheLifecycle.shutdown(PageCacheLifecycle.java:42)
>>  
>> ~[neo4j-kernel-2.2.2.jar:2.2.2]
>>     at 
>> org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.shutdown(LifeSupport.java:555)
>>  
>> [neo4j-kernel-2.2.2.jar:2.2.2]
>>     ... 11 common frames omitted
>>
>
>
> The most similar situation I found, and it's solution, are described in 
> this stackoverflow answe 
> <http://stackoverflow.com/questions/29713462/error-while-creating-maven-project-to-run-on-neo4j-server>
> r:
>
> I can think of two causes here:
>>
>>    1. another java process is accessing some of the files, unless 
>>    something other helps consider a kill -9 <pid>
>>    2. double check the file permissions in your graph.db folder.
>>
>>
> However, this seems to not be the same case I am running into.
> Could anyone help me with this?
> I attached the relavant pieces of my messages.log.
>
> Thank you,
>
> Péterson
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to