Neo4j (pid 774) took more than 120 seconds to stop

kumar.suman328 · November 17, 2018, 2:21pm

Suddenly Neo4j Stop working when i going to restart stop with following command

./bin/neo4j restart

Error

Neo4j (pid 774) took more than 120 seconds to stop.

Please let me know how can i solve this issues.

Thanks

Benoit · November 17, 2018, 2:25pm

Can you check the log files (neo4j.log and debug.log) and put an extract here ?

kumar.suman328 · November 17, 2018, 2:41pm

Ne4oj.log last error


Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminat$

Benoit · November 17, 2018, 2:46pm

I think that your logs are pretty clear, you have an OutOfMemory error, and you need to forcibly terminate the neo4j process.

Perhaps you will find the reason of this error in the debug.log file.

kumar.suman328 · November 17, 2018, 2:59pm

debug.log

2018-11-14 08:33:57.391+0000 ERROR [o.n.b.t.p.HouseKeeper] Fatal error occurred when handling a client connection: [id: 0x811304a0, L:/139.59.23.136:7687 - R:/116.75.2$
io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer
at io.netty.channel.unix.FileDescriptor.readAddress(..)(Unknown Source)
2018-11-14 08:35:39.135+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7214 checkpoint started...
2018-11-14 08:35:39.145+0000 INFO [o.n.k.i.s.c.CountsTracker] Rotated counts store at transaction 7214 to [/var/www/neo4j-enterprise-3.4.0/data/databases/graph.db/neos$
2018-11-14 08:35:39.155+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7214 checkpoint completed in 20ms
2018-11-14 08:35:39.156+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] No log version pruned, last checkpoint was made in version 0
2018-11-14 08:50:39.177+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7218 checkpoint started...
2018-11-14 08:50:39.191+0000 INFO [o.n.k.i.s.c.CountsTracker] Rotated counts store at transaction 7218 to [/var/www/neo4j-enterprise-3.4.0/data/databases/graph.db/neos$
2018-11-14 08:50:39.211+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7218 checkpoint completed in 34ms
2018-11-14 08:50:39.212+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] No log version pruned, last checkpoint was made in version 0
2018-11-14 09:13:32.047+0000 ERROR [o.n.b.t.p.HouseKeeper] Fatal error occurred when handling a client connection: [id: 0xda31a73d, L:/139.59.23.136:7687 - R:/116.75.2$
io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer
at io.netty.channel.unix.FileDescriptor.readAddress(..)(Unknown Source)
2018-11-14 09:47:18.268+0000 INFO [o.n.c.i.ExecutionEngine] Discarded stale query from the query cache after 97455 seconds: Match (s:Topic) UNWIND labels(s) as lbl wi$
2018-11-14 09:47:35.033+0000 INFO [o.n.c.i.ExecutionEngine] Discarded stale query from the query cache after 98439 seconds: MATCH (n)<-[r]-(c:Topic) where toLower(type$
2018-11-14 09:51:29.279+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7220 checkpoint started...
2018-11-14 09:51:29.291+0000 INFO [o.n.k.i.s.c.CountsTracker] Rotated counts store at transaction 7220 to [/var/www/neo4j-enterprise-3.4.0/data/databases/graph.db/neos$
2018-11-14 09:51:29.299+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7220 checkpoint completed in 20ms
2018-11-14 09:51:29.300+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] No log version pruned, last checkpoint was made in version 0
2018-11-14 10:04:39.884+0000 INFO [o.n.c.i.ExecutionEngine] Discarded stale query from the query cache after 1020170 seconds: MATCH (n)<-[r]-(c:Topic) where id(c)=145 2018-11-14 10:25:40.395+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7221 checkpoint started... 2018-11-14 10:25:40.404+0000 INFO [o.n.k.i.s.c.CountsTracker] Rotated counts store at transaction 7221 to [/var/www/neo4j-enterprise-3.4.0/data/databases/graph.db/neos
2018-11-14 10:25:40.410+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7221 checkpoint completed in 14ms
2018-11-14 10:25:40.410+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] No log version pruned, last checkpoint was made in version 0
2018-11-14 10:30:55.804+0000 INFO [o.n.c.i.EnterpriseCompatibilityFactory] Discarded stale query from the query cache after 97688 seconds: MATCH (n)<-[r]-(c:Topic) whe$
2018-11-14 10:34:58.538+0000 INFO [o.n.c.i.EnterpriseCompatibilityFactory] Discarded stale query from the query cache after 362326 seconds: match(v:Video{name:'Kamsin 2018-11-14 10:35:01.287+0000 INFO [o.n.c.i.EnterpriseCompatibilityFactory] Discarded stale query from the query cache after 362326 seconds: match(v:Video{name:'Kamsin
2018-11-14 10:40:40.558+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7222 checkpoint started...
2018-11-14 10:40:40.567+0000 INFO [o.n.k.i.s.c.CountsTracker] Rotated counts store at transaction 7222 to [/var/www/neo4j-enterprise-3.4.0/data/databases/graph.db/neos$
2018-11-14 10:40:40.574+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Checkpoint triggered by scheduler for time threshold @ txId: 7222 checkpoint completed in 16ms
2018-11-14 10:40:40.574+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] No log version pruned, last checkpoint was made in version 0

kumar.suman328 · November 17, 2018, 3:00pm

Can you let me know how can i solve this issues? I am new bibe in this domain

Benoit · November 17, 2018, 4:05pm

To restart you server you need to kill it and then start. So kill -9 774 and then ./bin/neo4j start

kumar.suman328 · November 18, 2018, 2:41pm

Please let me know how to increase memory so in future i will not face same issue ? after killing process and starting server working properly .

andrew_bowman · November 20, 2018, 10:45pm

You can use neo4j-admin memrec to generate a recommendation for memory settings based upon your system's hardware.

Here's the memory configuration documentation

Topic		Replies	Views
Stop Neo4j service is taking more than 1 hour to shutdown Neo4j Neo4j Graph Platform performance , operations	2	283	May 11, 2023
Migration to 4.0 stops Neo4j Graph Platform	8	791	February 9, 2020
Database becomes non-responsive in production Neo4j Graph Platform performance	12	7612	January 6, 2020
Cannot restart an offline DB with Java out of memory error Neo4j Graph Platform	4	380	August 3, 2021
Query running very slow after VM stop-the-world pause error Neo4j Graph Platform performance	2	140	March 4, 2024

Get Certified in June!

Neo4j (pid 774) took more than 120 seconds to stop

Related topics