search

EOSIO / eos

An open source smart contract platform
https://developers.eos.io/manuals/eos
MIT License
11.27k stars 3.6k forks source link

A ERROR appeared when loading eosio.bios #4633

Closed Danilo0120 closed 6 years ago

Danilo0120 commented 6 years ago

I have no idea what's up with this:

~/eos$ cleos set contract eosio ./build/contracts/eosio.bios -p eosio Reading WAST/WASM from ./build/contracts/eosio.bios/eosio.bios.wasm... Using already assembled WASM... Publishing contract... 1419308ms thread-0 main.cpp:2756 main ] Failed with error: Assert Exception (10) response_content_length >= 0: Invalid content-length response

Danilo0120 commented 6 years ago

I will appreciate it if this error is resolved

jgiszczak commented 6 years ago

Add http-validate-host = false to your nodeos config.ini. The latest version tightened up host validation considerably. This is good for production nodes, but it does require attention in local testnets.

Danilo0120 commented 6 years ago

@jgiszczak follow your guide,but it still have problem:

~/eos/build/programs/cleos$ cleos set contract eosio ../../contracts/eosio.bios -p eosio Reading WAST/WASM from ../../contracts/eosio.bios/eosio.bios.wasm... Using already assembled WASM... Publishing contract... 2272648ms thread-0 main.cpp:2756 main ] Failed with error: Assert Exception (10)

msj121 commented 6 years ago

I just got the same error. I cleared all blocks on my nodeos startup just now (--delete-all-blocks), It had published a contract today, recently changed the table definition, but changed back and no help. I also changed the ipaddress and port I listen on, but changed back and didn't help.

Reading WAST/WASM from ./validator.wast... Assembling WASM... Publishing contract... 438324ms thread-0 main.cpp:2756 main ] Failed with error: Assert Exception (10) response_content_length >= 0: Invalid content-length response

rebooted server, with http-server-address = 127.0.0.1:8888 still not working. wallet unlocked as well. From the beginning validation was set to false.

Danilo0120 commented 6 years ago

@msj121 follow his guide and have a try again?

msj121 commented 6 years ago

@Danilo0120 Oh, I already had that set to false and still had errors. Will update my post.

Danilo0120 commented 6 years ago

@msj121 I am searching a way to resolve this error

msj121 commented 6 years ago

@Danilo0120 My problem was delete all blocks also deleted accounts. Then I also needed to specify not just my wallet url, but also the nodeos url even after creating accounts:

cleos -u http://127.0.0.1:8899 --wallet-url http://127.0.0.1:8899 set contract ....

A more helpful error like couldn't connect to nodeos would have been supremely helpful, oddly enough that is the error with some other commands

jackiesun8 commented 6 years ago

change the ~/.local/share/eosio/nodeos/config/config.ini http-server-address = 127.0.0.1:8888 to http-server-address = localhost:8888 Solved my problem

rafael81 commented 6 years ago

@jackiesun8 I resolved this issue. thanks

nb312 commented 6 years ago

I have another problem when I run cleos set contract eosio build/contracts/eosio.bios -p eosio@active

Using already assembled WASM...
Publishing contract...
Error 3090003: Provided keys, permissions, and delays do not satisfy declared authorizations
Ensure that you have the related private keys inside your wallet and your wallet is unlocked.