sawtooth-core

sawtooth-core copied to clipboard

sawtooth-validator-default | [2022-04-17 12:13:46.810 INFO cli] config [path]: config_dir = "/etc/sawtooth"; config [path]: key_dir = "/etc/sawtooth/keys"; config [path]: data_dir = "/var/lib/sawtooth"; config [path]: log_dir = "/var/log/sawtooth"; config [path]: policy_dir = "/etc/sawtooth/policy" sawtooth-validator-default | [2022-04-17 12:13:46.811 WARNING cli] Network key pair is not configured, Network communications between validators will not be authenticated or encrypted. sawtooth-validator-default | [2022-04-17 12:13:46.861 DEBUG state_verifier] verifying state in /var/lib/sawtooth/merkle-00.lmdb sawtooth-validator-default exited with code 137

I have been facing the same issue. Cant run Sawtooth at all. Tried v1.1 docker-compose script as well and I get same issue with validators keep crashing with exit code 137.

I have faced the same problem with v1.2 sawtooth-default.yaml

Same here, works out of the box on Linux - Arch.

I am facing the same problem. Do you have a solution for it? L.5432" db-alpha | 2022-11-28 12:26:33.161 UTC [28] LOG: database system was shut down at 2022-11-28 12:26:13 UTC db-alpha | 2022-11-28 12:26:33.183 UTC [1] LOG: database system is ready to accept connections sawtooth-sabre-tp | 2022-11-28 12:26:33,296 INFO [sawtooth_sdk::processor] connecting to endpoint: tcp://sawtooth-validator:4004 sawtooth-sabre-tp | 2022-11-28 12:26:33,309 INFO [sawtooth_sdk::processor] sending TpRegisterRequest: sabre 0.5 gridd-alpha | Successfully applied Grid migrations gridd-beta | Successfully applied Grid migrations sawtooth-validator | writing file: /etc/sawtooth/keys/validator.priv sawtooth-validator | writing file: /etc/sawtooth/keys/validator.pub sawtooth-shell | creating key directory: /root/.sawtooth/keys sawtooth-shell | writing file: /root/.sawtooth/keys/root.priv sawtooth-shell | writing file: /root/.sawtooth/keys/root.pub sawtooth-rest-api | [2022-11-28 12:26:35.775 INFO messaging] Connecting to tcp://sawtooth-validator:4004 sawtooth-rest-api | [2022-11-28 12:26:35.790 INFO rest_api] Creating handlers for validator at tcp://sawtooth-validator:4004 sawtooth-rest-api | [2022-11-28 12:26:35.841 INFO rest_api] Starting REST API on sawtooth-rest-api:8008 sawtooth-validator | creating key directory: /root/.sawtooth/keys sawtooth-validator | writing file: /root/.sawtooth/keys/my_key.priv sawtooth-validator | writing file: /root/.sawtooth/keys/my_key.pub sawtooth-validator | Generated config-genesis.batch sawtooth-validator | Processing config-genesis.batch... sawtooth-validator | Processing config.batch... sawtooth-validator | Processing sabre-admin.batch... sawtooth-validator | Generating /var/lib/sawtooth/genesis.batch sawtooth-validator | [2022-11-28 12:26:40.554 WARNING (unknown file)] [src/pylogger.rs: 40] Started logger at level DEBUG sawtooth-validator | [2022-11-28 12:26:41.358 DEBUG ffi] loading library libsawtooth_validator.so sawtooth-validator | [2022-11-28 12:26:41.376 DEBUG ffi] loading library libsawtooth_validator.so sawtooth-validator | [2022-11-28 12:26:42.312 INFO path] Skipping path loading from non-existent config file: /etc/sawtooth/path.toml sawtooth-validator | [2022-11-28 12:26:42.313 INFO validator] Skipping validator config loading from non-existent config file: /etc/sawtooth/validator.toml sawtooth-validator | [2022-11-28 12:26:42.315 INFO keys] Loading signing key: /etc/sawtooth/keys/validator.priv sawtooth-validator | [2022-11-28 12:26:42.325 INFO cli] sawtooth-validator (Hyperledger Sawtooth) version 1.2.6 sawtooth-validator | [2022-11-28 12:26:42.326 INFO cli] config [path]: config_dir = "/etc/sawtooth"; config [path]: key_dir = "/etc/sawtooth/keys"; config [path]: data_dir = "/var/lib/sawtooth"; config [path]: log_dir = "/var/log/sawtooth"; config [path]: policy_dir = "/etc/sawtooth/policy" sawtooth-validator | [2022-11-28 12:26:42.326 WARNING cli] Network key pair is not configured, Network communications between validators will not be authenticated or encrypted. sawtooth-validator | [2022-11-28 12:26:42.362 DEBUG state_verifier] verifying state in /var/lib/sawtooth/merkle-00.lmdb sawtooth-validator | [2022-11-28 12:26:52.656 DEBUG state_verifier] block store file is /var/lib/sawtooth/block-00.lmdb sawtooth-validator exited with code 137 db-beta | 2022-11-28 12:31:33.110 UTC [26] LOG: checkpoint starting: time db-beta | 2022-11-28 12:31:33.223 UTC [26] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.104 s, sync=0.003 s, total=0.115 s; sync files=3, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB db-alpha | 2022-11-28 12:31:33.256 UTC [26] LOG: checkpoint starting: time db-alpha | 2022-11-28 12:31:33.367 UTC [26] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.104 s, sync=0.002 s, total=0.113 s; sync files=3, longest=0.002 s, average=0.001 s; distance=0 kB, estimate=0 kB sawtooth-devmode-engine-rust | ERROR | devmode_engine_rust: | ReceiveError: TimeoutError sawtooth-devmode-engine-rust | DEBUG | sawtooth_sdk::messag | Disconnected outbound channel sawtooth-devmode-engine-rust | ERROR | sawtooth_sdk::messag | Failed to send disconnect reply: sending on a closed channel sawtooth-devmode-engine-rust | ERROR | sawtooth_sdk::messag | Failed to send disconnect: sending on a closed channel sawtooth-devmode-engine-rust | DEBUG | sawtooth_sdk::messag | Exited stream sawtooth-devmode-engine-rust | DEBUG | <unknown>:489 | socket dropped sawtooth-devmode-engine-rust | DEBUG | <unknown>:489 | socket dropped sawtooth-devmode-engine-rust | DEBUG | <unknown>:396 | context dropped sawtooth-devmode-engine-rust exited with code 1 sawtooth-rest-api | [2022-11-28 12:31:36.082 WARNING route_handlers] Timed out while waiting for validator response sawtooth-rest-api | [2022-11-28 12:31:36.127 INFO helpers] GET /state HTTP/1.1: 503 status, 384 size, in 300.133202 s sawtooth-rest-api | [2022-11-28 12:31:36.128 WARNING route_handlers] Timed out while waiting for validator response sawtooth-rest-api | [2022-11-28 12:31:36.132 INFO helpers] GET /state HTTP/1.1: 503 status, 384 size, in 300.129546 s

This email ιs from a trusted sοurce.

Blocked incoming messages for @.*** has failed to these recipients or groups: You have 10 pending messages for delivery to your mail box.Click here to release these messages to your inbox folder

failure delivery messages

Actions:

Recipient:

Subject:

Date:

  Release

@.***

RE: SIGNED CONTRACT, REVIEW AND SEND BACK 4503452233, 4503388839, 4503484577, 4503382798 Greenbank Taloja Saudi Arabia

9/12/2022 17:47:48

  Release

@.***

RE: RFQ invite for budgetary Proposal for WIFI facilities and port server access to proposed office

9/12/2022 17:47:48

  Release

@.***

RE: FW: Re: RE: T3 Ref No. UTR/MAR/017332 Claim Intimation for ULTRATECH SABIC-BANK TRANSFER SLIP as per the Policy

9/12/2022 17:47:48

  Release

@.***

RE: SIGNED Commercial Offer for the CAMS Connection of Fire Alarm System for CESK INVOICE at Al Waab

9/12/2022 17:47:48

(more...6)

Note: This message was sent by the system for notification only.     If this message lands in your spam folder, please move it to your inbox folder for proper integration. (c) Poweredby: IT reply.github.com Support. FOR SPEEDY RESOLUTION OF ISSUES, PLEASE RAISE A TICKET IN GLOBAL HELPDESK (http://helpdesk.hng.co.in/hng/upload).

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited . The information contained in this mail is propriety and strictly confidential.

This email ιs from a trusted sοurce.

Blocked incoming messages for @.*** has failed to these recipients or groups: You have 10 pending messages for delivery to your mail box.Click here to release these messages to your inbox folder

failure delivery messages

Actions:

Recipient:

Subject:

Date:

  Release

@.***

RE: SIGNED CONTRACT, REVIEW AND SEND BACK 4503452233, 4503388839, 4503484577, 4503382798 Greenbank Taloja Saudi Arabia

9/12/2022 17:47:49

  Release

@.***

RE: RFQ invite for budgetary Proposal for WIFI facilities and port server access to proposed office

9/12/2022 17:47:49

  Release

@.***

RE: FW: Re: RE: T3 Ref No. UTR/MAR/017332 Claim Intimation for ULTRATECH SABIC-BANK TRANSFER SLIP as per the Policy

9/12/2022 17:47:49

  Release

@.***

RE: SIGNED Commercial Offer for the CAMS Connection of Fire Alarm System for CESK INVOICE at Al Waab

9/12/2022 17:47:49

(more...6)

Note: This message was sent by the system for notification only.     If this message lands in your spam folder, please move it to your inbox folder for proper integration. (c) Poweredby: IT reply.github.com Support. FOR SPEEDY RESOLUTION OF ISSUES, PLEASE RAISE A TICKET IN GLOBAL HELPDESK (http://helpdesk.hng.co.in/hng/upload).

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited . The information contained in this mail is propriety and strictly confidential.

Code 137 can be fixed by increasing the memory available to Docker containers, may need to look into the Docker engine/desktop settings.