A doubt about Multichain node crash

+1 vote

Hello, we have a wallet application using Multichain in production for asset management and transactions. Since last year Multichain has been running satisfactorily until on 01-28-2022 the main MC node crashed, we do not know what the reason for the crash is, we reviewed the MC log and did not find a specific reason. Attached part of the log at the time of the crash.

Log:

2022-01-28 00:39:50 MultiChainMiner: Block Found - 002036c71cec5d0d007932dec478635d5d850387c902ae8d43e8261c8aa4b0c4, prev: 00f5ec65e24ca0e31445daa722cbeb059e43e7322acb747e5ec87ec1eb87d545, height: 899756, txs: 6
2022-01-28 00:40:38 ResendWalletTransactions()
2022-01-28 00:40:38 Timeout downloading block 0070fec1205e35e65923680d842ec96b1771c70a78b77e2998320e5acf1bfaf9 from peer=19, disconnecting
2022-01-28 00:40:39 CommitTransaction: 463c14d4f1663e5bc9e3ab2634bd209a0f0a785343263269b380199f78332fa6, vin: 1, vout: 2
2022-01-28 00:40:39 mchn: Sending minimal parameter set to 172.31.0.32:39342
2022-01-28 00:40:39 receive version message: /MultiChain:0.2.0.12/: version 70002, blocks=899772, us=172.31.0.31:7185, peer=20
2022-01-28 00:41:22 UpdateTip:            new best=002036c71cec5d0d007932dec478635d5d850387c902ae8d43e8261c8aa4b0c4  height=899756  log2_work=27.779176  tx=1026581  date=2022-01-28 00:39:49 progress=1.000000  cache=0
2022-01-28 00:41:22 mchn: Connection from 12nuNkY9N8WRtWt4pVoSKPAxo1MxM7B1u2peb6 received on peer=20 in verack
2022-01-28 00:41:22 mchn: Connection from 12nuNkY9N8WRtWt4pVoSKPAxo1MxM7B1u2peb6 received on peer=20 in verackack (172.31.0.32:39342)
2022-01-28 00:41:22 mchn: Parameter set from peer=20 verified
2022-01-28 00:41:22 ResendWalletTransactions()
2022-01-28 00:42:12 ResendWalletTransactions()
2022-01-28 00:42:13 MultiChainMiner: Block Found - 00c4c7b89dd90352ce20835ecc0d52c1e5d1088d57aaf7f75931d33ef1463e7a, prev: 002036c71cec5d0d007932dec478635d5d850387c902ae8d43e8261c8aa4b0c4, height: 899757, txs: 2
2022-01-28 00:43:12 ping timeout: 60.000686s
2022-01-28 00:43:24 UpdateTip:            new best=00c4c7b89dd90352ce20835ecc0d52c1e5d1088d57aaf7f75931d33ef1463e7a  height=899757  log2_work=27.779177  tx=1026583  date=2022-01-28 00:42:12 progress=1.000000  cache=0
2022-01-28 00:45:05 mchn: Sending minimal parameter set to 172.31.0.32:39344
2022-01-28 00:45:17 socket receive timeout: 61s
2022-01-28 00:45:54 socket send error Bad file descriptor (9)
2022-01-28 00:45:54 receive version message: /MultiChain:0.2.0.12/: version 70002, blocks=899783, us=172.31.0.31:7185, peer=22
2022-01-28 00:46:23 CommitTransaction: 59ec32e160eb7fcd6d1f29faad260a8b3a6c20ab0e116b4f2055f6da58dfba10, vin: 1, vout: 2
2022-01-28 00:47:10 mchn: Sending minimal parameter set to 172.31.0.32:39348
2022-01-28 00:47:10 receive version message: /MultiChain:0.2.0.12/: version 70002, blocks=899783, us=172.31.0.31:7185, peer=24
2022-01-28 00:48:02 mchn: Connection from 12nuNkY9N8WRtWt4pVoSKPAxo1MxM7B1u2peb6 received on peer=24 in verack
2022-01-28 00:48:11 socket sending timeout: 61s
2022-01-28 00:48:50 socket send error Bad file descriptor (9)

asked Feb 2, 2022 by amroth23
I've sent this to the dev team to take a look.

1 Answer

0 votes
What version are you using? The first suggestion is to upgrade to the latest version and restart the node, then see if this happens again.
answered Feb 3, 2022 by MultiChain
...