This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Help

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

Database cannot started after load database

johnson_zhangc
Node

‎08-27-2020 02:08 AM

I'm trying to migrating our demo database (Community version) from Amazon Linux 2 AMI to RedHat 7.6.

We installed 4.0.4 on AMI server, and 4.1.1 on RedHat server.

We dump the data from AMI server and copy it to the RedHat server. Here is what we did on RedHat server:

  1. remove the comment # from dbms.allow_upgrade=true in neo4j.conf
  2. service neo4j stop
  3. neo4j-admin load --from=20200826.dump --database=neo4j --force
  4. service neo4j start

Then connect to 7474 then we got neo4j cannot be started.
We even install the same version(4.0.4) on RedHat, it comes out the same result.

2X_5_54437629a72086c3d242e47966c732e120936dca.png

Here is the log we have

Aug 27 15:50:52 Chat-Flow-Plus-01 systemd[1]: Started Neo4j Graph Database.
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: Directories in use:
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: home:         /var/lib/neo4j
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: config:       /etc/neo4j
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: logs:         /var/log/neo4j
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: plugins:      /var/lib/neo4j/plugins
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: import:       /var/lib/neo4j/import
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: data:         /var/lib/neo4j/data
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: certificates: /var/lib/neo4j/certificates
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: run:          /var/run/neo4j
Aug 27 15:50:52 Chat-Flow-Plus-01 neo4j[141333]: Starting Neo4j.
Aug 27 15:50:53 Chat-Flow-Plus-01 neo4j[141333]: 2020-08-27 08:50:53.444+0000 INFO  Starting...
Aug 27 15:50:55 Chat-Flow-Plus-01 neo4j[141333]: 2020-08-27 08:50:55.592+0000 INFO  ======== Neo4j 4.1.1 ========
Aug 27 15:50:56 Chat-Flow-Plus-01 neo4j[141333]: 2020-08-27 08:50:56.949+0000 INFO  Performing postInitialization step for component 'security-users' with version 2 and status CURRENT
Aug 27 15:50:56 Chat-Flow-Plus-01 neo4j[141333]: 2020-08-27 08:50:56.950+0000 INFO  Updating the initial password in component 'security-users'
Aug 27 15:50:57 Chat-Flow-Plus-01 neo4j[141333]: 2020-08-27 08:50:57.010+0000 INFO  Bolt enabled on 0.0.0.0:7687.
Aug 27 15:50:57 Chat-Flow-Plus-01 neo4j[141333]: 2020-08-27 08:50:57.937+0000 INFO  Remote interface available at http://localhost:7474/
Aug 27 15:50:57 Chat-Flow-Plus-01 neo4j[141333]: 2020-08-27 08:50:57.938+0000 INFO  Started.

and here is the debug.log we have:

2020-08-22 10:57:27.323+0000 WARN [o.n.k.i.JvmChecker] The dbms.memory.heap.max_size setting has not been configured. It is recommended that this setting is always explicitly configured, to ensure the system has a balanced configuration. Until then, a JVM computed heuristic of 2042626048 bytes is used instead. Run `neo4j-admin memrec` for memory configuration suggestions.
2020-08-22 10:57:27.324+0000 WARN [o.n.k.i.JvmChecker] The dbms.memory.heap.initial_size setting has not been configured. It is recommended that this setting is always explicitly configured, to ensure the system has a balanced configuration. Until then, a JVM computed heuristic of 127926272 bytes is used instead. Run `neo4j-admin memrec` for memory configuration suggestions.
2020-08-22 10:57:27.396+0000 WARN [o.n.i.p.PageCache] The dbms.memory.pagecache.size setting has not been configured. It is recommended that this setting is always explicitly configured, to ensure the system has a balanced configuration. Until then, a computed heuristic value of 3060848640 bytes will be used instead. Run `neo4j-admin memrec` for memory configuration suggestions.
2020-08-22 10:57:27.437+0000 INFO [o.n.i.d.DiagnosticsManager] ********************************************************************************
2020-08-22 10:57:27.438+0000 INFO [o.n.i.d.DiagnosticsManager]                              [ System diagnostics ]
2020-08-22 10:57:27.438+0000 INFO [o.n.i.d.DiagnosticsManager] ********************************************************************************
2020-08-22 10:57:27.441+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.441+0000 INFO [o.n.i.d.DiagnosticsManager]                          [ System memory information ]
2020-08-22 10:57:27.442+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.443+0000 INFO [o.n.i.d.DiagnosticsManager] Total Physical memory: 7.604GiB
2020-08-22 10:57:27.443+0000 INFO [o.n.i.d.DiagnosticsManager] Free Physical memory: 5.811GiB
2020-08-22 10:57:27.444+0000 INFO [o.n.i.d.DiagnosticsManager] Committed virtual memory: 4.853GiB
2020-08-22 10:57:27.444+0000 INFO [o.n.i.d.DiagnosticsManager] Total swap space: 5.000GiB
2020-08-22 10:57:27.444+0000 INFO [o.n.i.d.DiagnosticsManager] Free swap space: 5.000GiB
2020-08-22 10:57:27.444+0000 INFO [o.n.i.d.DiagnosticsManager]
2020-08-22 10:57:27.444+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.444+0000 INFO [o.n.i.d.DiagnosticsManager]                            [ JVM memory information ]
2020-08-22 10:57:27.445+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.445+0000 INFO [o.n.i.d.DiagnosticsManager] Free  memory: 59.42MiB
2020-08-22 10:57:27.445+0000 INFO [o.n.i.d.DiagnosticsManager] Total memory: 124.0MiB
2020-08-22 10:57:27.446+0000 INFO [o.n.i.d.DiagnosticsManager] Max   memory: 1.902GiB
2020-08-22 10:57:27.450+0000 INFO [o.n.i.d.DiagnosticsManager] Garbage Collector: G1 Young Generation: [G1 Eden Space, G1 Survivor Space, G1 Old Gen]
2020-08-22 10:57:27.450+0000 INFO [o.n.i.d.DiagnosticsManager] Garbage Collector: G1 Old Generation: [G1 Eden Space, G1 Survivor Space, G1 Old Gen]
2020-08-22 10:57:27.453+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: CodeHeap 'non-nmethods' (Non-heap memory): committed=2.438MiB, used=1.147MiB, max=5.563MiB, threshold=0B
2020-08-22 10:57:27.454+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: Metaspace (Non-heap memory): committed=13.63MiB, used=13.01MiB, max=-1B, threshold=0B
2020-08-22 10:57:27.454+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: CodeHeap 'profiled nmethods' (Non-heap memory): committed=3.563MiB, used=3.553MiB, max=117.2MiB, threshold=0B
2020-08-22 10:57:27.455+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: Compressed Class Space (Non-heap memory): committed=1.625MiB, used=1.374MiB, max=1024MiB, threshold=0B
2020-08-22 10:57:27.455+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: G1 Eden Space (Heap memory): committed=61.00MiB, used=53.00MiB, max=-1B, threshold=?
2020-08-22 10:57:27.456+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: G1 Old Gen (Heap memory): committed=61.00MiB, used=8.080MiB, max=1.902GiB, threshold=0B
2020-08-22 10:57:27.456+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: G1 Survivor Space (Heap memory): committed=2.000MiB, used=2.000MiB, max=-1B, threshold=?
2020-08-22 10:57:27.456+0000 INFO [o.n.i.d.DiagnosticsManager] Memory Pool: CodeHeap 'non-profiled nmethods' (Non-heap memory): committed=2.438MiB, used=777.5KiB, max=117.2MiB, threshold=0B
2020-08-22 10:57:27.456+0000 INFO [o.n.i.d.DiagnosticsManager]
2020-08-22 10:57:27.457+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.457+0000 INFO [o.n.i.d.DiagnosticsManager]                         [ Operating system information ]
2020-08-22 10:57:27.457+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.457+0000 INFO [o.n.i.d.DiagnosticsManager] Operating System: Linux; version: 3.10.0-957.el7.x86_64; arch: amd64; cpus: 4
2020-08-22 10:57:27.459+0000 INFO [o.n.i.d.DiagnosticsManager] Max number of file descriptors: 60000
2020-08-22 10:57:27.460+0000 INFO [o.n.i.d.DiagnosticsManager] Number of open file descriptors: 158
2020-08-22 10:57:27.470+0000 INFO [o.n.i.d.DiagnosticsManager] Process id: 26354@XXXXX
2020-08-22 10:57:27.470+0000 INFO [o.n.i.d.DiagnosticsManager] Byte order: LITTLE_ENDIAN
2020-08-22 10:57:27.470+0000 INFO [o.n.i.d.DiagnosticsManager] Local timezone: Asia/Bangkok
2020-08-22 10:57:27.470+0000 INFO [o.n.i.d.DiagnosticsManager]
2020-08-22 10:57:27.471+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.471+0000 INFO [o.n.i.d.DiagnosticsManager]                               [ JVM information ]
2020-08-22 10:57:27.471+0000 INFO [o.n.i.d.DiagnosticsManager] --------------------------------------------------------------------------------
2020-08-22 10:57:27.471+0000 INFO [o.n.i.d.DiagnosticsManager] VM Name: OpenJDK 64-Bit Server VM
2020-08-22 10:57:27.471+0000 INFO [o.n.i.d.DiagnosticsManager] VM Vendor: Oracle Corporation
2020-08-22 10:57:27.472+0000 INFO [o.n.i.d.DiagnosticsManager] VM Version: 11.0.8+10-LTS
2020-08-22 10:57:27.472+0000 INFO [o.n.i.d.DiagnosticsManager] JIT compiler: HotSpot 64-Bit Tiered Compilers
"debug.log" 39179L, 4709337C

Would appreciated if anyone knows how we can resolve this problem. Thanks,

Labels:
0 Kudos
Reply
1 REPLY 1

johnson_zhangc
Node

‎08-27-2020 10:39 PM

I ever tried dump and load the same database on RedHat, it also showed neo4j is unavailable. What is the problem of this?

0 Kudos
Reply
Nodes 2022
Nodes
NODES 2022, Neo4j Online Education Summit

All the sessions of the conference are now available online

Watch replays