Installing canisters issue in 0.6.16

dfx 0.6.16
When I run
dfx new say_hello and
run dfx deploy
the canisters created and built successfully but cannot be installed and damage the while IC. following the error log

~/dfinity/say_hello$ dfx start --clean
Dec 22 12:31:35.506 INFO ic-starter. Configuration: ValidatedConfig { replica_path: Some("/home/amr/.cache/dfinity/versions/0.6.16/replica"), replica_version: “0.1.0”, log_level: Warning, subnet_id: fscpm-uiaaa-aaaaa-aaaap-yai, cargo_bin: “cargo”, cargo_opts: “”, state_dir: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state”, http_listen_addr: V4(127.0.0.1:0), http_port_file: Some("/home/amr/dfinity/say_hello/.dfx/replica-configuration/replica-1.port"), metrics_addr: None, hypervisor_create_funds_whitelist: “", artifact_pool_dir: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/ic_consensus_pool”, crypto_root: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/crypto”, state_manager_root: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/state”, registry_file: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/registry.proto”, bootstrap_registry: None, state_dir_holder: None }, Application: starter
Dec 22 12:31:35.509 INFO Initialize replica configuration “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/ic.json5”, Application: starter
Dec 22 12:31:35.551 INFO Executing “/home/amr/.cache/dfinity/versions/0.6.16/replica” “–replica-version” “0.1.0” “–config-file” “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/ic.json5”, Application: starter
Dec 22 12:31:36.151 ERRO s:fscpm-uiaaa-aaaaa-aaaap-yai/n:i4uwx-75lbf-p7d2a-sqdzu-42zw2-md3pg-rncgx-x7fjt-anwmj-y6fp4-rqe/ic_messaging/xnet_endpoint No XNet configuration for node i4uwx-75lbf-p7d2a-sqdzu-42zw2-md3pg-rncgx-x7fjt-anwmj-y6fp4-rqe. This is an error in production, but may be ignored in single-subnet test deployments.
Dec 22 12:31:37.155 WARN s:fscpm-uiaaa-aaaaa-aaaap-yai/n:i4uwx-75lbf-p7d2a-sqdzu-42zw2-md3pg-rncgx-x7fjt-anwmj-y6fp4-rqe/ic_http_handler/ic_http_handler NNS subnet not found in network topology. Skipping fetching the delegation.
Starting webserver on port 33693 for replica at “http://localhost:33693
binding to: V4(127.0.0.1:8000)
replica(s): http://localhost:33693/
thread ‘MR Batch Processor’ panicked at ‘failed to grow state file to 8GiB size: Os { code: 28, kind: Other, message: “No space left on device” }’, src/cow_state/mod.rs:703:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Dec 22 12:32:19.499 INFO ic-starter. Configuration: ValidatedConfig { replica_path: Some("/home/amr/.cache/dfinity/versions/0.6.16/replica"), replica_version: “0.1.0”, log_level: Warning, subnet_id: fscpm-uiaaa-aaaaa-aaaap-yai, cargo_bin: “cargo”, cargo_opts: “”, state_dir: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state”, http_listen_addr: V4(127.0.0.1:0), http_port_file: Some("/home/amr/dfinity/say_hello/.dfx/replica-configuration/replica-1.port"), metrics_addr: None, hypervisor_create_funds_whitelist: "
”, artifact_pool_dir: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/ic_consensus_pool”, crypto_root: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/crypto”, state_manager_root: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/state”, registry_file: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/registry.proto”, bootstrap_registry: None, state_dir_holder: None }, Application: starter
Dec 22 12:32:19.985 ERRO s:fscpm-uiaaa-aaaaa-aaaap-yai/n:i4uwx-75lbf-p7d2a-sqdzu-42zw2-md3pg-rncgx-x7fjt-anwmj-y6fp4-rqe/ic_messaging/xnet_endpoint No XNet configuration for node i4uwx-75lbf-p7d2a-sqdzu-42zw2-md3pg-rncgx-x7fjt-anwmj-y6fp4-rqe. This is an error in production, but may be ignored in single-subnet test deployments.
thread ‘MR Batch Processor’ panicked at ‘failed to grow state file to 8GiB size: Os { code: 28, kind: Other, message: “No space left on device” }’, src/cow_state/mod.rs:703:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

it seems like you don’t have enough space on your machine? can you double check this?

1 Like

I cleaned more than 20GB disk space

Installing code for canister say_hello, with canister_id rwlgt-iiaaa-aaaaa-aaaaa-cai
The replica returned an HTTP Error: Http Error: status 400 Bad Request, content type “text/plain; charset=utf-8”, content: Failed to connect to host: Connection refused (os error 111)

Starting webserver on port 33826 for replica at “http://localhost:33826
binding to: V4(127.0.0.1:8000)
replica(s): http://localhost:33826/
thread ‘MR Batch Processor’ panicked at ‘Unable to vmsplice: Sys(ENOSYS)’, src/cow_state/mod.rs:267:17
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Dec 22 13:15:47.346 INFO ic-starter. Configuration: ValidatedConfig { replica_path: Some("/home/amr/.cache/dfinity/versions/0.6.16/replica"), replica_version: “0.1.0”, log_level: Warning, subnet_id: fscpm-uiaaa-aaaaa-aaaap-yai, cargo_bin: “cargo”, cargo_opts: “”, state_dir: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state”, http_listen_addr: V4(127.0.0.1:0), http_port_file: Some("/home/amr/dfinity/say_hello/.dfx/replica-configuration/replica-1.port"), metrics_addr: None, hypervisor_create_funds_whitelist: “*”, artifact_pool_dir: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/ic_consensus_pool”, crypto_root: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/crypto”, state_manager_root: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/node-100/state”, registry_file: “/home/amr/dfinity/say_hello/.dfx/state/replicated_state/registry.proto”, bootstrap_registry: None, state_dir_holder: None }, Application: starter
Dec 22 13:15:47.859 ERRO s:fscpm-uiaaa-aaaaa-aaaap-yai/n:nan7d-4i36k-7dy7r-pcjpw-gh3h6-hu3bk-uvw52-gmxmz-pxcj4-couud-mae/ic_messaging/xnet_endpoint No XNet configuration for node nan7d-4i36k-7dy7r-pcjpw-gh3h6-hu3bk-uvw52-gmxmz-pxcj4-couud-mae. This is an error in production, but may be ignored in single-subnet test deployments.
thread ‘MR Batch Processor’ panicked at ‘Unable to vmsplice: Sys(ENOSYS)’, src/cow_state/mod.rs:267:17
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

I have two questioins
1 - whey the dfx IC goes down if such errors “fail installing canisters” occuer ?
2 - this is the standard steps not success but in the 0.6.10 all example projects succeeded. I think something related to the new canister id encryption type ?

Thanks for the feedback amr.

@alexa.smith @hansl

If you need to, you can revert to a previously installed version by editing the version no in your project’s dfx.json file.

Or to install a previous version that isn’t already cached on your machine use: DFX_VERSION=0.6.14 sh -ci "$(curl -sSL https://sdk.dfinity.org/install.sh)"

I also has problem on this version un able to start

Hi amr
Are you running version 2 of WSL? Windows isn’t officially supported but if you follow this you should have success: https://forum.dfinity.org/t/native-windows-support/1241/2

1 Like

I also encountered the same problem:
The replica returned an HTTP Error: Http Error: status 400 Bad Request, content type “text/plain; charset=utf-8”, content: Failed to connect to host: Connection refused (os error 111)