Open MohammadJamali opened 6 days ago
i have same problem
Once you run the default command sudo ./start_ocean.sh --with-c2d --no-dashboard
, Ganache runs like this:
ganache-1 | Chain
ganache-1 | ==================
ganache-1 | Hardfork: istanbul
ganache-1 | Id: 8996
ganache-1 |
However, ocean-contracts compiles contracts for the London and Paris hardforks.
ocean-contracts-1 | Compiled 97 Solidity files successfully (evm targets: london, paris).
This leads to the following error:
DATA_data_nft, DATA_datatoken, DATA_ddo = ocean.assets.create_arweave_asset('Max', txid, {"from": alice})
ValueError: {'message': 'Could not decode transaction: invalid RLP: remainder must be zero', 'stack': 'Error: Could not decode transaction: invalid RLP: remainder must be zero\n at TransactionFactory.fromString (/app/dist/node/1.js:2:241431)\n at EthereumApi.eth_sendRawTransaction (/app/dist/node/1.js:2:65380)\n at n.value (/app/dist/node/1.js:2:159715)\n at Object.execute (/app/dist/node/1.js:2:289971)\n at RequestCoordinator.<anonymous> (/app/dist/node/1.js:2:289785)\n at /app/dist/node/1.js:2:290051\n at new Promise (<anonymous>)\n at RequestCoordinator.queue (/app/dist/node/1.js:2:289893)\n at Executor.execute (/app/dist/node/1.js:2:284503)\n at EthereumProvider._requestRaw (/app/dist/node/1.js:2:183646)', 'code': -32700}
I manually changed these parameters: "--chain.hardfork", "london", "--miner.blockTime", "0"
in the ganache.yml
file. Setting blockTime to 1 (which is the default behavior of the --predictor
flag) results in the underpriced
error. Now I am facing the following issue:
DATA_data_nft, DATA_datatoken, DATA_ddo = ocean.assets.create_arweave_asset('Max', txid, {"from": alice})
aquarius-1 | 2024-10-24 17:23:46,103 - aquarius.app.es_instance - ERROR - get: ApiError(503, 'no_shard_available_action_exception', 'No shard available for [get [aquarius][did:op:4e325bb46657ced0fbb37b80d475b54da0af3101ed161d5ae616450a35d3daa5]: routing [null]]')
/venv/lib/python3.11/site-packages/ocean_lib/ocean/ocean_assets.py", line 350, in create_bundled
raise AquariusError(
ocean_lib.exceptions.AquariusError: Asset id did:op:4e325bb46657ced0fbb37b80d475b54da0af3101ed161d5ae616450a35d3daa5 is already registered to another asset.
python-BaseException
I will update you as I work on fixing this issue as well.
curl -XGET localhost:9200/_cluster/allocation/explain
{"note":"No shard was specified in the explain API request, so this response explains a randomly chosen unassigned shard. There may be other unassigned shards in this cluster which cannot be assigned for different reasons. It may not be possible to assign this shard until one of the other shards is assigned correctly. To explain the allocation of other shards (whether assigned or unassigned) you must specify the target shard in the request to this API.","index":"aquarius_plus","shard":0,"primary":true,"current_state":"unassigned","unassigned_info":{"reason":"INDEX_CREATED","at":"2024-10-25T07:55:34.995Z","last_allocation_status":"no"},"can_allocate":"no","allocate_explanation":"Elasticsearch isn't allowed to allocate this shard to any of the nodes in the cluster. Choose a node to which you expect this shard to be allocated, find this node in the node-by-node explanation, and address the reasons which prevent Elasticsearch from allocating this shard there.","node_allocation_decisions":[{"node_id":"z53iEEILSdGocmv2YxUDWg","node_name":"31930b5ec572","transport_address":"172.15.0.6:9300","node_attributes":{"ml.max_jvm_size":"536870912","ml.allocated_processors_double":"32.0","xpack.installed":"true","ml.machine_memory":"16359354368","ml.allocated_processors":"32"},"node_decision":"no","weight_ranking":1,"deciders":[{"decider":"disk_threshold","decision":"NO","explanation":"the node is above the high watermark cluster setting [cluster.routing.allocation.disk.watermark.high=90%], having less than the minimum required [23.6gb] free space, actual free: [17.2gb], actual used: [92.7%]"}]}]}
i added a new hard drive and now it's working! why 17.2gb is not enough :| ... why ... wasted two days on this 😄
Describe the bug ocean-contracts has problem processing response in the
Deploying USDC MOC
phase:To Reproduce
Outputs
** can be fix with this: If you get a gas-related error like transaction underpriced, you'll need to change the priority_fee or max_fee.
Sorry for this issue, safely delete it. thanks