Error when running the testnet node

I found that there is a same issue rb2nem submitted on github some days ago, and i tried to add ‘-f’ to ‘rm’,but did not fix it.

Hello! Could you please join us on Slack (I will send an invite for you)? There is a discussion about the issue from Github.

1 Like

Thanks :smile:

1 Like

do you have the 132 code exit?

Note that this error is not due to the -fflag missing for an rm command, but is due to what is described in this issue: https://github.com/nemfoundation/symbol-testnet-bootstrap/issues/3

Restoring this file from the git history is possible with

git checkout 2338550526c181ddb8f5e2a0b9ce0431f76a960a^ \
  -- api-harvest-assembly/rest-gateway/config-input.yaml

but I suppose this makes your node use some generic keys and is not the proper solution. It points to the source of the problem though.

2 Likes

Yes.

I had the issue with all my 4th gen intel CPUs. Exiting 132. If you have the same problem, probably for the same reason. Looks like there will be a fix in the future.
But i am no Pro. In Blockchain or setting up nodes over all so maybe you have another problem.

Hi, thanks

It can fix the ‘rest.json’ error, but still exit with the code 132

Creating apiharvestassembly_generate-raw-addresses_1 … done
Creating apiharvestassembly_update_vars_1 … done
Creating apiharvestassembly_api-node_1 … done
Creating apiharvestassembly_api-broker_1 … done
Creating apiharvestassembly_db_1 … done
Creating apiharvestassembly_update_vars_1 …
Creating apiharvestassembly_init-db_1 … done
Creating apiharvestassembly_init-db_1 …
Creating apiharvestassembly_rest-gateway_1 … done
Attaching to apiharvestassembly_api-node_1, apiharvestassembly_update_vars_1, apiharvestassembly_store-addresses_1, apiharvestassembly_db_1, apiharvestassembly_api-broker_1, apiharvestassembly_generate-raw-addresses_1, apiharvestassembly_init-db_1, apiharvestassembly_rest-gateway_1
apiharvestassembly_update_vars_1 exited with code 0
db_1 | 2020-02-14T01:42:43.999+0000 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols ‘none’
apiharvestassembly_store-addresses_1 exited with code 0
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/dbdata 64-bit host=87cbaea9c090
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] db version v4.2.3
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] git version: 6874650b362138df74be53d366bbefc321ea32d4
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.1 11 Sep 2018
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] allocator: tcmalloc
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] modules: none
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] build environment:
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] distmod: ubuntu1804
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] distarch: x86_64
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] target_arch: x86_64
db_1 | 2020-02-14T01:42:44.015+0000 I CONTROL [initandlisten] options: { net: { bindIp: “db” }, storage: { dbPath: “/dbdata” } }
db_1 | 2020-02-14T01:42:44.026+0000 I STORAGE [initandlisten] Detected data files in /dbdata created by the ‘wiredTiger’ storage engine, so setting the active storage engine to ‘wiredTiger’.
db_1 | 2020-02-14T01:42:44.027+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=2390M,cache_overflow=(file_max=0M),session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress],
db_1 | 2020-02-14T01:42:44.848+0000 I STORAGE [initandlisten] WiredTiger message [1581644564:847843][1:0x7f93edecfb00], txn-recover: Recovering log 1 through 2
db_1 | 2020-02-14T01:42:44.958+0000 I STORAGE [initandlisten] WiredTiger message [1581644564:958603][1:0x7f93edecfb00], txn-recover: Recovering log 2 through 2
db_1 | 2020-02-14T01:42:45.065+0000 I STORAGE [initandlisten] WiredTiger message [1581644565:65073][1:0x7f93edecfb00], txn-recover: Main recovery loop: starting at 1/436608 to 2/256
db_1 | 2020-02-14T01:42:45.174+0000 I STORAGE [initandlisten] WiredTiger message [1581644565:174956][1:0x7f93edecfb00], txn-recover: Recovering log 1 through 2
db_1 | 2020-02-14T01:42:45.245+0000 I STORAGE [initandlisten] WiredTiger message [1581644565:245055][1:0x7f93edecfb00], txn-recover: Recovering log 2 through 2
db_1 | 2020-02-14T01:42:45.297+0000 I STORAGE [initandlisten] WiredTiger message [1581644565:297332][1:0x7f93edecfb00], txn-recover: Set global recovery timestamp: (0, 0)
db_1 | 2020-02-14T01:42:45.320+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
db_1 | 2020-02-14T01:42:45.335+0000 I STORAGE [initandlisten] Timestamp monitor starting
apiharvestassembly_api-broker_1 exited with code 132
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten]
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended.
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten]
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten]
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is ‘always’.
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten] ** We suggest setting it to ‘never’
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten]
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is ‘always’.
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten] ** We suggest setting it to ‘never’
db_1 | 2020-02-14T01:42:45.338+0000 I CONTROL [initandlisten]
apiharvestassembly_generate-raw-addresses_1 exited with code 0
db_1 | 2020-02-14T01:42:45.383+0000 I SHARDING [initandlisten] Marking collection local.system.replset as collection version:
db_1 | 2020-02-14T01:42:45.386+0000 I STORAGE [initandlisten] Flow Control is enabled on this deployment.
db_1 | 2020-02-14T01:42:45.386+0000 I SHARDING [initandlisten] Marking collection admin.system.roles as collection version:
db_1 | 2020-02-14T01:42:45.386+0000 I SHARDING [initandlisten] Marking collection admin.system.version as collection version:
db_1 | 2020-02-14T01:42:45.388+0000 I SHARDING [initandlisten] Marking collection local.startup_log as collection version:
db_1 | 2020-02-14T01:42:45.389+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory ‘/dbdata/diagnostic.data’
db_1 | 2020-02-14T01:42:45.391+0000 I SHARDING [LogicalSessionCacheRefresh] Marking collection config.system.sessions as collection version:
db_1 | 2020-02-14T01:42:45.391+0000 I SHARDING [LogicalSessionCacheReap] Marking collection config.transactions as collection version:
db_1 | 2020-02-14T01:42:45.391+0000 I NETWORK [listener] Listening on /tmp/mongodb-27017.sock
db_1 | 2020-02-14T01:42:45.392+0000 I NETWORK [listener] Listening on 172.20.0.3
db_1 | 2020-02-14T01:42:45.392+0000 I NETWORK [listener] waiting for connections on port 27017
rest-gateway_1 |
rest-gateway_1 | > [email protected] start /app/rest
rest-gateway_1 | > node _build/index.js “resources/rest.json” “/userconfig/rest.json”
rest-gateway_1 |
db_1 | 2020-02-14T01:42:45.825+0000 I NETWORK [listener] connection accepted from 172.20.0.8:55854 #1 (1 connection now open)
db_1 | 2020-02-14T01:42:45.826+0000 I NETWORK [conn1] received client metadata from 172.20.0.8:55854 conn1: { application: { name: “MongoDB Shell” }, driver: { name: “MongoDB Internal Client”, version: “4.2.3” }, os: { type: “Linux”, name: “Ubuntu”, architecture: “x86_64”, version: “18.04” } }
db_1 | 2020-02-14T01:42:45.832+0000 I SHARDING [conn1] Marking collection local.oplog.rs as collection version:
db_1 | 2020-02-14T01:42:45.865+0000 I NETWORK [conn1] end connection 172.20.0.8:55854 (0 connections now open)
init-db_1 | [+] Preparing db
init-db_1 | MongoDB shell version v4.2.3
init-db_1 | connecting to: mongodb://db:27017/catapult?compressors=disabled&gssapiServiceName=mongodb
db_1 | 2020-02-14T01:42:45.977+0000 I NETWORK [listener] connection accepted from 172.20.0.8:55856 #2 (1 connection now open)
db_1 | 2020-02-14T01:42:45.977+0000 I NETWORK [conn2] received client metadata from 172.20.0.8:55856 conn2: { application: { name: “MongoDB Shell” }, driver: { name: “MongoDB Internal Client”, version: “4.2.3” }, os: { type: “Linux”, name: “Ubuntu”, architecture: “x86_64”, version: “18.04” } }
init-db_1 | Implicit session: session { “id” : UUID(“e18f8142-d241-4912-9d6e-3db7dccd5266”) }
init-db_1 | MongoDB server version: 4.2.3
init-db_1 | Loading LockHash
init-db_1 | Loading LockSecret
init-db_1 | Loading Metadata
init-db_1 | Loading Mosaic
init-db_1 | Loading Multisig
init-db_1 | Loading Namespace
init-db_1 | Loading RestrictionAccount
init-db_1 | Loading RestrictionMosaic
init-db_1 | ===== accountRestrictions INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “accountRestrictions.address” : 1 }
init-db_1 | ===== accounts INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “account.publicKey” : 1 }
init-db_1 | { “account.address” : 1 }
init-db_1 | ===== addressResolutionStatements INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “statement.height” : 1, “statement.unresolved” : 1 }
init-db_1 | ===== blocks INDEXES =====
db_1 | 2020-02-14T01:42:46.033+0000 I SHARDING [conn2] Marking collection catapult.accountRestrictions as collection version:
db_1 | 2020-02-14T01:42:46.034+0000 I SHARDING [conn2] Marking collection catapult.accounts as collection version:
db_1 | 2020-02-14T01:42:46.035+0000 I SHARDING [conn2] Marking collection catapult.addressResolutionStatements as collection version:
init-db_1 | { “_id” : 1 }
init-db_1 | { “block.signerPublicKey” : 1 }
init-db_1 | { “block.timestamp” : -1 }
init-db_1 | { “block.height” : -1 }
init-db_1 | { “block.signerPublicKey” : 1, “block.height” : -1 }
init-db_1 | ===== hashLocks INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “lock.hash” : 1 }
init-db_1 | { “lock.senderPublicKey” : 1 }
init-db_1 | { “lock.senderAddress” : 1 }
init-db_1 | ===== metadata INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “metadataEntry.compositeHash” : 1 }
init-db_1 | {
init-db_1 | “metadataEntry.senderPublicKey” : 1,
init-db_1 | “metadataEntry.metadataType” : 1,
init-db_1 | “metadataEntry.scopedMetadataKey” : 1
init-db_1 | }
init-db_1 | {
init-db_1 | “metadataEntry.targetPublicKey” : 1,
init-db_1 | “metadataEntry.metadataType” : 1,
init-db_1 | “metadataEntry.scopedMetadataKey” : 1
init-db_1 | }
init-db_1 | ===== mosaicResolutionStatements INDEXES =====
db_1 | 2020-02-14T01:42:46.036+0000 I SHARDING [conn2] Marking collection catapult.blocks as collection version:
db_1 | 2020-02-14T01:42:46.038+0000 I SHARDING [conn2] Marking collection catapult.hashLocks as collection version:
db_1 | 2020-02-14T01:42:46.039+0000 I SHARDING [conn2] Marking collection catapult.metadata as collection version:
db_1 | 2020-02-14T01:42:46.040+0000 I SHARDING [conn2] Marking collection catapult.mosaicResolutionStatements as collection version:
init-db_1 | { “_id” : 1 }
init-db_1 | { “statement.height” : 1, “statement.unresolved” : 1 }
init-db_1 | ===== mosaicRestrictions INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “mosaicRestrictionEntry.compositeHash” : 1 }
init-db_1 | ===== mosaics INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “mosaic.id” : 1 }
init-db_1 | { “mosaic.ownerPublicKey” : 1 }
init-db_1 | ===== multisigs INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “multisig.accountPublicKey” : 1 }
init-db_1 | { “multisig.accountAddress” : 1 }
init-db_1 | ===== namespaces INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “namespace.level0” : 1, “meta.index” : 1, “namespace.depth” : 1 }
init-db_1 | {
init-db_1 | “meta.active” : -1,
init-db_1 | “meta.index” : 1,
init-db_1 | “namespace.level0” : 1,
init-db_1 | “namespace.depth” : 1
init-db_1 | }
init-db_1 | { “meta.active” : -1, “namespace.level1” : 1, “namespace.depth” : 1 }
init-db_1 | { “meta.active” : -1, “namespace.level2” : 1, “namespace.depth” : 1 }
init-db_1 | { “meta.active” : -1, “namespace.ownerPublicKey” : 1 }
init-db_1 | { “meta.active” : -1, “namespace.ownerAddress” : 1 }
init-db_1 | ===== partialTransactions INDEXES =====
db_1 | 2020-02-14T01:42:46.041+0000 I SHARDING [conn2] Marking collection catapult.mosaicRestrictions as collection version:
db_1 | 2020-02-14T01:42:46.042+0000 I SHARDING [conn2] Marking collection catapult.mosaics as collection version:
db_1 | 2020-02-14T01:42:46.043+0000 I SHARDING [conn2] Marking collection catapult.multisigs as collection version:
db_1 | 2020-02-14T01:42:46.044+0000 I SHARDING [conn2] Marking collection catapult.namespaces as collection version:
db_1 | 2020-02-14T01:42:46.046+0000 I SHARDING [conn2] Marking collection catapult.partialTransactions as collection version:
db_1 | 2020-02-14T01:42:46.047+0000 I SHARDING [conn2] Marking collection catapult.secretLocks as collection version:
db_1 | 2020-02-14T01:42:46.048+0000 I SHARDING [conn2] Marking collection catapult.system.profile as collection version:
db_1 | 2020-02-14T01:42:46.049+0000 I SHARDING [conn2] Marking collection catapult.transactionStatements as collection version:
db_1 | 2020-02-14T01:42:46.050+0000 I SHARDING [conn2] Marking collection catapult.transactionStatuses as collection version:
db_1 | 2020-02-14T01:42:46.051+0000 I SHARDING [conn2] Marking collection catapult.transactions as collection version:
init-db_1 | { “_id” : 1 }
init-db_1 | { “transaction.signerPublicKey” : 1, “_id” : -1 }
init-db_1 | { “transaction.recipientAddress” : 1, “_id” : -1 }
init-db_1 | { “meta.hash” : 1 }
init-db_1 | { “meta.addresses” : 1 }
init-db_1 | { “meta.aggregateId” : 1 }
init-db_1 | { “meta.aggregateHash” : 1 }
init-db_1 | ===== secretLocks INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “lock.compositeHash” : 1 }
init-db_1 | { “lock.senderPublicKey” : 1 }
init-db_1 | { “lock.senderAddress” : 1 }
init-db_1 | ===== system.profile INDEXES =====
init-db_1 | ===== transactionStatements INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | {
init-db_1 | “statement.height” : 1,
init-db_1 | “statement.source.primaryId” : 1,
init-db_1 | “statement.source.secondaryId” : 1
init-db_1 | }
init-db_1 | ===== transactionStatuses INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “status.hash” : 1 }
init-db_1 | { “status.deadline” : -1 }
init-db_1 | ===== transactions INDEXES =====
init-db_1 | { “_id” : 1 }
init-db_1 | { “transaction.signerPublicKey” : 1, “_id” : -1 }
init-db_1 | { “transaction.recipientAddress” : 1, “_id” : -1 }
init-db_1 | { “meta.hash” : 1 }
init-db_1 | { “meta.addresses” : 1 }
init-db_1 | { “meta.aggregateId” : 1 }
init-db_1 | { “meta.height” : -1 }
init-db_1 | { “transaction.deadline” : -1 }
init-db_1 | { “transaction.cosignatures.signerPublicKey” : 1 }
init-db_1 | { “transaction.id” : 1, “transaction.type” : 1 }
init-db_1 | ===== unconfirmedTransactions INDEXES =====
db_1 | 2020-02-14T01:42:46.054+0000 I SHARDING [conn2] Marking collection catapult.unconfirmedTransactions as collection version:
db_1 | 2020-02-14T01:42:46.060+0000 I NETWORK [conn2] end connection 172.20.0.8:55856 (0 connections now open)
init-db_1 | { “_id” : 1 }
init-db_1 | { “transaction.signerPublicKey” : 1, “_id” : -1 }
init-db_1 | { “transaction.recipientAddress” : 1, “_id” : -1 }
init-db_1 | { “meta.hash” : 1 }
init-db_1 | { “meta.addresses” : 1 }
init-db_1 | { “meta.aggregateId” : 1 }
init-db_1 | { “meta.aggregateHash” : 1 }
init-db_1 | bye
init-db_1 | [.] (exit code: 0)
init-db_1 | /
init-db_1 | [+] db prepared, checking account indexes
init-db_1 | MongoDB shell version v4.2.3
init-db_1 | connecting to: mongodb://db:27017/catapult?compressors=disabled&gssapiServiceName=mongodb
db_1 | 2020-02-14T01:42:46.178+0000 I NETWORK [listener] connection accepted from 172.20.0.8:55860 #3 (1 connection now open)
db_1 | 2020-02-14T01:42:46.178+0000 I NETWORK [conn3] received client metadata from 172.20.0.8:55860 conn3: { application: { name: “MongoDB Shell” }, driver: { name: “MongoDB Internal Client”, version: “4.2.3” }, os: { type: “Linux”, name: “Ubuntu”, architecture: “x86_64”, version: “18.04” } }
init-db_1 | Implicit session: session { “id” : UUID(“c9d2e74c-90a3-4167-bdfd-504def295be3”) }
init-db_1 | MongoDB server version: 4.2.3
db_1 | 2020-02-14T01:42:46.189+0000 I NETWORK [conn3] end connection 172.20.0.8:55860 (0 connections now open)
init-db_1 | [
init-db_1 | {
init-db_1 | “v” : 2,
init-db_1 | “key” : {
init-db_1 | “_id” : 1
init-db_1 | },
init-db_1 | “name” : “id”,
init-db_1 | “ns” : “catapult.accounts”
init-db_1 | },
init-db_1 | {
init-db_1 | “v” : 2,
init-db_1 | “key” : {
init-db_1 | “account.publicKey” : 1
init-db_1 | },
init-db_1 | “name” : “account.publicKey_1”,
init-db_1 | “ns” : “catapult.accounts”
init-db_1 | },
init-db_1 | {
init-db_1 | “v” : 2,
init-db_1 | “unique” : true,
init-db_1 | “key” : {
init-db_1 | “account.address” : 1
init-db_1 | },
init-db_1 | “name” : “account.address_1”,
init-db_1 | “ns” : “catapult.accounts”
init-db_1 | }
init-db_1 | ]
apiharvestassembly_init-db_1 exited with code 0
rest-gateway_1 | [winston] Attempt to write logs with no transports {“message”:“loading config from resources/rest.json”,“level”:“info”}
rest-gateway_1 | [winston] Attempt to write logs with no transports {“message”:“loading config from /userconfig/rest.json”,“level”:“info”}
rest-gateway_1 | info: loading config from resources/rest.json
rest-gateway_1 | info: loading config from /userconfig/rest.json
rest-gateway_1 | verbose: finished loading rest server config {“network”:{“name”:“publicTest”,“description”:“catapult public test network”},“port”:3000,“crossDomain”:{“allowedHosts”:["*"],“allowedMethods”:[“GET”,“POST”,“PUT”,“OPTIONS”]},“clientPrivateKey”:“77D07C2CA239D339FDC1E236F49A0769550DF00953B42546D8FC13AC1C8E6118”,“extensions”:[“accountLink”,“aggregate”,“lockHash”,“lockSecret”,“mosaic”,“metadata”,“multisig”,“namespace”,“receipts”,“restrictions”,“transfer”],“db”:{“url”:“mongodb://db:27017/”,“name”:“catapult”,“pageSizeMin”:10,“pageSizeMax”:100,“countRangeMin”:1,“countRangeMax”:100,“countRangePreset”:25,“maxConnectionAttempts”:5,“baseRetryDelay”:500},“apiNode”:{“host”:“api-node”,“port”:7900,“publicKey”:“PUBLIC_KEY”,“timeout”:1000},“websocket”:{“mq”:{“host”:“api-broker”,“port”:7902,“monitorInterval”:500,“connectTimeout”:10000,“monitorLoggingThrottle”:60000},“allowOptionalAddress”:true},“logging”:{“console”:{“formats”:[“colorize”,“simple”],“level”:“verbose”,“handleExceptions”:true},“file”:{“formats”:[“prettyPrint”],“level”:“verbose”,“handleExceptions”:true,“filename”:"/logs/catapult-rest.log",“maxsize”:20971520,“maxFiles”:100}},“timestamp”:“2020-02-14T01:42:46.644Z”}
rest-gateway_1 | info: connecting to mongodb://db:27017/ (database:catapult) {“timestamp”:“2020-02-14T01:42:46.646Z”}
rest-gateway_1 | (node:28) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor.
db_1 | 2020-02-14T01:42:46.682+0000 I NETWORK [listener] connection accepted from 172.20.0.9:35396 #4 (1 connection now open)
db_1 | 2020-02-14T01:42:46.696+0000 I NETWORK [conn4] received client metadata from 172.20.0.9:35396 conn4: { driver: { name: “nodejs”, version: “3.3.3” }, os: { type: “Linux”, name: “linux”, architecture: “x64”, version: “3.10.0-1062.el7.x86_64” }, platform: “Node.js v10.19.0, LE, mongodb-core: 3.3.3” }
rest-gateway_1 | verbose: connected to mongo at mongodb://db:27017/catapult {“timestamp”:“2020-02-14T01:42:46.703Z”}
rest-gateway_1 | info: registering routes {“timestamp”:“2020-02-14T01:42:46.705Z”}
rest-gateway_1 | info: listening on port 3000 {“timestamp”:“2020-02-14T01:42:46.768Z”}
api-node_1 | !!! Going to start api node now…
apiharvestassembly_api-node_1 exited with code 132

Hi,

My CPU is Intel E5-2620 v2

Provide please:

cat /proc/cpuinfo

HI,

[[email protected] api-harvest-assembly]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 62
model name : Intel® Xeon® CPU E5-2620 v2 @ 2.10GHz
stepping : 4
microcode : 0x42d
cpu MHz : 1200.091
cache size : 15360 KB
physical id : 0
siblings : 12
core id : 0
cpu cores : 6
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts spec_ctrl intel_stibp flush_l1d
bogomips : 4200.09
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:

Sadly I can’t open catapult-testnet-bootstrap issues on GitHub anymore. But the error you have is documented there.

“The release images target modern x86 architectures. It has been reported that errors are experienced on some older machines provided. If you run into any related issues, please report in the”

slack group (#help).

I got a dell with a 7th gen i5, that worked. But a Fix should be on the way.