Mining halted in all nodes.

+1 vote

I set up a blockchain on a server. Now the blockchain has stopped mining after attaining a block height of 1451. I tried restarting the blockchain with the runtime parameters -reindex=1 and -miningrequirespeers=0. Now the multichaind is not starting at all. It throws the following error:

MultiChain Core Daemon build 1.0 alpha 27 protocol 10007

Other nodes can connect to this node using:
multichaind testchain@55.51.83.156:7401


This host has multiple IP addresses, so from some networks:
multichaind testchain@10.15.0.2:7401

Protocol version 10006

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

 

Given below are the parameters for my chain. Any idea what went wrong?

{
    "chain-protocol" : "multichain",
    "chain-description" : "MultiChain testchain",
    "root-stream-name" : "root",
    "root-stream-open" : false,
    "chain-is-testnet" : false,
    "target-block-time" : 45,
    "maximum-block-size" : 1000000000,
    "default-network-port" : 7401,
    "default-rpc-port" : 7400,
    "anyone-can-connect" : false,
    "anyone-can-send" : false,
    "anyone-can-receive" : false,
    "anyone-can-create" : false,
    "anyone-can-issue" : false,
    "anyone-can-mine" : false,
    "anyone-can-activate" : false,
    "anyone-can-admin" : false,
    "allow-p2sh-outputs" : true,
    "allow-multisig-outputs" : true,
    "setup-first-blocks" : 60,
    "mining-diversity" : 0.30000000,
    "admin-consensus-admin" : 0.50000000,
    "admin-consensus-activate" : 0.50000000,
    "admin-consensus-mine" : 0.50000000,
    "admin-consensus-create" : 0.00000000,
    "admin-consensus-issue" : 0.00000000,
    "mining-requires-peers" : true,
    "first-block-reward" : -1,
    "initial-block-reward" : 0,
    "reward-halving-interval" : 52560000,
    "reward-spendable-delay" : 1,
    "minimum-per-output" : 0,
    "maximum-per-output" : 100000000000000,
    "minimum-relay-fee" : 0,
    "native-currency-multiple" : 100000000,
    "skip-pow-check" : false,
    "pow-minimum-bits" : 16,
    "target-adjust-freq" : 172800,
    "allow-min-difficulty-blocks" : false,
    "only-accept-std-txs" : true,
    "max-std-tx-size" : 8388608,
    "max-std-op-returns-count" : 10,
    "max-std-op-return-size" : 4194304,
    "max-std-op-drops-count" : 5,
    "max-std-element-size" : 16384,
    "chain-name" : "testchain",
    "protocol-version" : 10006,
    "network-message-start" : "fbf7f9e6",
    "address-pubkeyhash-version" : "00d80a0a",
    "address-scripthash-version" : "05e7e57d",
    "private-key-version" : "80426016",
    "address-checksum-value" : "8576a4c3",
    "genesis-pubkey" : "0321a68694831e67fe861565e1a391ab9e69586ef46190fd2b5d876a24474c0426",
    "genesis-version" : 1,
    "genesis-timestamp" : 1486696226,
    "genesis-nbits" : 520159231,
    "genesis-nonce" : 6546,
    "genesis-pubkey-hash" : "40a6ce97eb6160864286250f9319914525aef40a",
    "genesis-hash" : "0000559a05825eb28b2a3994d161152d9d4a39a7353b0fc2ff5488faaeb1d817",
    "chain-params-hash" : "e3824014a7fd92eb808bc961ef922bc854c4d4551029791ac8ec1d26e3fe9287"
}

asked Feb 13, 2017 by Cypher
edited Feb 13, 2017 by Cypher
Have you been running some kind of stress test with millions of transactions?

Please log in or register to answer this question.

...