Error: grin docker floonet container exits with non-zero 135 code

Tech Support
1

Hi,

I experience an issue with running the docker floonet container. The container seems to start correctly, it shows it is downloading headers and blocks and connected with peers etc. and then suddenly it crashes. From docker ps -a I see it twice exited with error code 135 “Exited (135)”

19
191194×472 137 KB

It happend twice and the issue occurs after a couple of minutes when the grin status overview (when docker exec’ed into the running container) shows it is downloading headers/blocks and also shows it is connected to 13 (the irony :wink: ) peers (see uploaded printscrn).

I’ll try and analyse further, but for now I wanted to share this. Perhaps anyone knows what is causing this.

EDIT::
Running the docker through overriding the entrypoint and command is more stable:

docker run -it -d -v $HOME/.grin:/root/.grin --entrypoint /bin/bash grin-floonet:latest -s

followed by (inside the container)

grin --floonet server run

and now it runs stable it seems:

50
501834×524 220 KB

If it were to crash I could perhaps have obtained more details inside the still running container itself.

/end of EDIT:

container info
On master (git hash 3b4492495f9247c) built image with:

docker build -t grin-floonet -f etc/Dockerfile.floonet .

and then run the built image with:

docker run -it -d -v $HOME/.grin:/root/.grin grin-floonet:latest

Grin-server.log 1 (last lines)
20190104 12:29:16.340 DEBUG grin_p2p::protocol - handle_payload: received block: msg_len: 1255

20190104 12:29:16.340 DEBUG grin_servers::common::adapters - Received block 00a666c6 at 4206 from 45.61.156.122:13414 [in/out/kern: 0/1/1] going to process.

20190104 12:29:16.341 DEBUG grin_chain::pipe - pipe: process_block 00a666c6 at 4206 [in/out/kern: 0/1/1]

20190104 12:29:16.342 DEBUG grin_chain::txhashset::txhashset - Error returned, discarding txhashset header extension: Invalid Root

Cause: Unknown

Backtrace:

20190104 12:29:16.343 INFO grin_chain::chain - Rejected block 00a666c6 at 4206: Error { inner:

Invalid Root }

20190104 12:29:16.343 DEBUG grin_servers::common::adapters - process_block: block 00a666c6 refused by chain: Other Error: Error { inner:

Invalid Root }

20190104 12:29:16.389 DEBUG grin_servers::grin::sync::header_sync - sync: locator : [(9361, 02eaa149), (9359, 002eb72b), (9355, 02f780bd), (9347, 034b94ff), (9331, 02e337b8), (9299, 01be9fe1), (9235, 38bc1398), (9107, 02441abb), (8863, 004f99bf), (8413, 01f1ea60), (7389, 012f9992), (6365, 015dea5d), (0, edc758c1)]

20190104 12:29:16.389 DEBUG grin_servers::grin::sync::header_sync - sync: request_headers: asking 54.148.113.184:13414 for headers, [02eaa149, 002eb72b, 02f780bd, 034b94ff, 02e337b8, 01be9fe1, 38bc1398, 02441abb, 004f99bf, 01f1ea60, 012f9992, 015dea5d, edc758c1]

20190104 12:29:16.682 DEBUG grin_servers::common::types - sync_state: sync_status: BodySync { current_height: 4205, highest_height: 9361 } -> HeaderSync { current_height: 9361, highest_height: 9362 }

20190104 12:29:16.685 DEBUG grin_servers::grin::sync::header_sync - sync: locator : [(9361, 02eaa149), (9359, 002eb72b), (9355, 02f780bd), (9347, 034b94ff), (9331, 02e337b8), (9299, 01be9fe1), (9235, 38bc1398), (9107, 02441abb), (8863, 004f99bf), (8413, 01f1ea60), (7389, 012f9992), (4319, 01ca447e), (0, edc758c1)]

20190104 12:29:16.686 DEBUG grin_servers::grin::sync::header_sync - sync: request_headers: asking 46.101.201.216:13414 for headers, [02eaa149, 002eb72b, 02f780bd, 034b94ff, 02e337b8, 01be9fe1, 38bc1398, 02441abb, 004f99bf, 01f1ea60, 012f9992, 01ca447e, edc758c1]

20190104 12:29:16.739 INFO grin_servers::common::adapters - Received 1 block headers from 46.101.201.216:13414

20190104 12:29:16.740 DEBUG grin_chain::pipe - pipe: sync_block_headers: 1 headers from 01d977ef at 9362

20190104 12:29:16.741 DEBUG grin_chain::txhashset::txhashset - Rewind header extension to 02eaa149 at 9361

Grin-server.log 2 (last lines)
0190104 12:42:21.604 DEBUG grin_servers::common::adapters - process_block: block 0a325eaf refused by chain: Other Error: Error { inner:

Old Block }

20190104 12:42:21.605 DEBUG grin_p2p::protocol - handle_payload: received block: msg_len: 6069

20190104 12:42:21.606 DEBUG grin_servers::common::adapters - Received block 06ac2a09 at 1917 from 106.75.115.115:13414 [in/out/kern: 5/7/4] going to process.

20190104 12:42:21.606 DEBUG grin_chain::pipe - pipe: process_block 06ac2a09 at 1917 [in/out/kern: 5/7/4]

20190104 12:42:21.606 INFO grin_chain::chain - Rejected block 06ac2a09 at 1917: Error { inner:

Old Block }

20190104 12:42:21.607 DEBUG grin_servers::common::adapters - process_block: block 06ac2a09 refused by chain: Other Error: Error { inner:

Old Block }

20190104 12:42:21.618 DEBUG grin_servers::common::adapters - Received block header 1abbb470 at 9377 from 106.75.115.115:13414, going to process.

20190104 12:42:21.618 DEBUG grin_chain::pipe - pipe: process_block_header: 1abbb470 at 9377

20190104 12:42:21.620 DEBUG grin_p2p::peer - Requesting compact block 1abbb470 from 106.75.115.115:13414

20190104 12:42:21.636 INFO grin_servers::common::adapters - Received 1 block headers from 147.91.82.116:13414

20190104 12:42:21.636 DEBUG grin_chain::pipe - pipe: sync_block_headers: 1 headers from 1abbb470 at 9377

20190104 12:42:21.637 DEBUG grin_chain::txhashset::txhashset - Rewind header extension to 02322992 at 9376

2

Interesting, pretty sure there is a command in the Dockerfile that disables the TUI but you seem to be running with it enabled?

3

Thanks for reaching out. I have not configured anything special, like e.g. toggling on or off any config for the TUI. I did exec into the running container, docker exec -it 39d /bin/bash, followed by grin --floonet inside the container. The one I started through overriding entrypoint & docker cmd (see ‘EDIT’ section above) is still running stable after > 9 hrs.

4

Yes, I am wondering whether the pregenerated config is used appropriately by grin or grin generates its own on startup. I will have a closer look over the weekend, haven’t touched the docker image for a while.