Nem.core crashes

Tech Support
#1

Hello

I’m running nem.com v0.6.97 and it keeps crashing. The logs as it crashes are:

2020-12-02 02:35:27.903 INFO loadBlocks (from height 1766302 to height 1766401) needed 9ms (org.nem.nis.dao.BlockDaoImpl d)
2020-12-02 02:35:28.472 INFO loadBlocks (from height 1766402 to height 1766501) needed 10ms (org.nem.nis.dao.BlockDaoImpl d)
2020-12-02 02:35:29.043 INFO loadBlocks (from height 1766502 to height 1766601) needed 7ms (org.nem.nis.dao.BlockDaoImpl d)
2020-12-02 02:35:30.095 INFO loadBlocks (from height 1766602 to height 1766701) needed 9ms (org.nem.nis.dao.BlockDaoImpl d)
2020-12-02 02:35:30.543 INFO loadBlocks (from height 1766702 to height 1766801) needed 6ms (org.nem.nis.dao.BlockDaoImpl d)
2020-12-02 02:35:31.078 INFO loadBlocks (from height 1766802 to height 1766901) needed 8ms (org.nem.nis.dao.BlockDaoImpl d)
2020-12-02 02:35:32.025 WARN SQL Error: 50000, SQLState: HY000 (org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions)
2020-12-02 02:35:32.025 ERROR General error: "java.lang.RuntimeException: page[966266] data leaf table:198 TRANSFERREDMOSAICS entries:66 parent:970661 keys:[400093, 400094, 400095, 400096, 400097, 400098, 400099, 400100, 400101, 400102, 400103, 400104, 400105, 400106, 400107, 400108, 400109, 400110, 400111, 400112, 400113, 400114, 400115, 400116, 400117, 400118, 400119, 400120, 400121, 400122, 400123, 400124, 400125, 400126, 400127, 400128, 400129, 400130, 400131, 400132, 400133, 400134, 400135, 400136, 400137, 400138, 400139, 400140, 400141, 400142, 400143, 400144, 400145, 400146, 400147, 400148, 400149, 400150, 400151, 400152, 400153, 400154, 400155, 400156, 400157, 400158] offsets:[2034, 2015, 1996, 1982, 1963, 1944, 1931, 1918, 1899, 1885, 1871, 1857, 1843, 1829, 1814, 1795, 1781, 1767, 1752, 1738, 1724, 1710, 1696, 1682, 1663, 1649, 1630, 1611, 1597, 1583, 1569, 1555, 1536, 1522, 1508, 1489, 1470, 1456, 1437, 1423, 1404, 1390, 1376, 1362, 1343, 1329, 1316, 1299, 1285, 1271, 1257, 1240, 1222, 1208, 1194, 1181, 1164, 1147, 1129, 1115, 1098, 1084, 1067, 1053, 1039, 1025] parent 970661 expected 978596"; SQL statement:
SELECT t.*, tm.id as id1, tm.dbMosaicId as dbMosaicId1, tm.quantity as quantity1 FROM transfers t LEFT OUTER JOIN transferredMosaics tm ON tm.transferId = t.id WHERE blockid > ? AND blockid < ? ORDER BY blockid ASC [50000-176] (org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions)
2020-12-02 02:35:32.033 SEVERE something really bad happened: java.util.concurrent.CompletionException: org.hibernate.exception.GenericJDBCException: could not extract ResultSet (org.nem.nis.NisMain b)
2020-12-02 02:35:32.050:INFO:oejs.ServerConnector:Thread-3: Stopped ServerConnector@6cbb7a7d{HTTP/1.1}{0.0.0.0:7778}
2020-12-02 02:35:32.052:INFO:/:Thread-3: Destroying Spring FrameworkServlet 'Spring Websocket Dispatcher Servlet'
2020-12-02 02:35:32.095:INFO:/:Thread-3: Closing Spring root WebApplicationContext
2020-12-02 02:35:32.102:INFO:oejsh.ContextHandler:Thread-3: Stopped o.e.j.s.ServletContextHandler@578a5ce8{/,null,UNAVAILABLE}
2020-12-02 02:35:32.125:INFO:oejs.ServerConnector:Thread-3: Stopped ServerConnector@4bf4680c{HTTP/1.1}{0.0.0.0:7890}
2020-12-02 02:35:32.125:INFO:/:Thread-3: Destroying Spring FrameworkServlet 'Spring MVC Dispatcher Servlet'
2020-12-02 02:35:32.136:INFO:/:Thread-3: Closing Spring root WebApplicationContext
2020-12-02 02:35:32.136:INFO:oejsh.ContextHandler:Thread-3: Stopped o.e.j.s.ServletContextHandler@eaf8427{/,null,UNAVAILABLE}

What can I do about this?

Thanks

#2

Hi. Looks like your node db is corrupted.
What I can suggest is to start sync from beginning (remove node db) or remove and use presynced db (https://bob.nem.ninja/nis5_mainnet.h2-2764k.db.zip) to speedup process.

#3

Thanks.

I havent tried with the presynced db yet, but thanks for the suggestion.

I did try removing the node db. However the issue is still occurring.

The log output prior to crashing contains lots of the following:

2020-12-08 22:12:49.370 INFO loadBlocks (from height 1520702 to height 1520801) needed 17ms (org.nem.nis.dao.BlockDaoImpl d)

Am I correct in thinking this is reading, and perhaps validating, already downloaded blocks?

What are the recommended Java opt settings for running nem.core? We are now using -Xms3G -Xmx6G having bumped it up from -Xms1G -Xmx3G - but are still experiencing the same issue.
Thanks

#4

What you included are only INFO logs that blocks from disk are loaded. Did you removed db or replaced it by this one https://bob.nem.ninja/nis5_mainnet.h2-2764k.db.zip? If you only removed then node should sync from scratch and should no load blocks from disk.

BTW what is your goal? Only to opt-in?

#5

Opt in is certainly one of our goals, yes.

#6

You can also opt-in from desktop wallet (connecting to other public nodes) if importing private key there is option for you.

Please let me know if you solved problems with node. If not please include fresh logs

There is also new presynced db available:
https://bob.nem.ninja/nis5_mainnet.h2-2967k.db.zip

#7

You can also opt-in from desktop wallet (connecting to other public nodes) if importing private key there is option for you.

Yes, it is possibly an option.

And yes I got the problem resolved. The machine needed more CPU cores.

1 Like