Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RPC call failed: ErrorObject { code: MethodNotFound, message: "method not found", data: Some(RawValue("getAccount")) } / soroban-rpc (exit status 1; not expected) #29

Closed
karolrojas07 opened this issue Apr 4, 2023 · 0 comments
Closed

RPC call failed: ErrorObject { code: MethodNotFound, message: "method not found", data: Some(RawValue("getAccount")) } / soroban-rpc (exit status 1; not expected) #29

karolrojas07 opened this issue Apr 4, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@karolrojas07
Copy link

What version are you using?

cargo: 1.68.0
rustup: 1.25.2
rustc: 1.68.0
Docker: 23.0.2
Operating System:
image

What did you do?

I am testing the "Getting Starting" guide for Soroban Smart Contract and I am stuck when doing the deployment to the Local Network:
These steps: https://soroban.stellar.org/docs/getting-started/deploy-to-a-local-network

I run the docker image to run the local network like this:

docker run --rm -it \
  -p 8000:8000 \
  --name stellar \
  stellar/quickstart:soroban-dev \
  --standalone \
  --enable-soroban-rpc

I got this output:

Starting Stellar Quickstart
mode: ephemeral
network: standalone (Standalone Network ; February 2017)
postgres user: stellar
postgres password: XsbnaRGf97ETa5aU
finalize-pgpass: ok
init-postgres: ok
Waiting for postgres to be available...
Waiting for postgres to be available...
postgres: up
create-horizon-db: ok
create-core-db: ok
stellar-postgres-user: ok
chown-core: ok
finalize-core-config-pgpass: ok
finalize-core-config-run-standalone: ok
finalize-core-config-artificially-accelerate-time-for-testing: ok
finalize-core-config-manual-close: ok

init-core-db: ok
init-core-scp: ok
init-history: ok
finalize-horizon-checkpoint-frequency: ok
chown-horizon: ok
init-horizon-db: ok
init-genesis-state: ok
finalize-soroban-rpc-captivecore-db: ok
finalize-core-config-artificially-accelerate-time-for-testing: ok
finalize-core-config-enable-soroban-diagnostic-events: ok
finalize-horizon-checkpoint-frequency: ok
init-soroban-rpc: ok
postgres: down
supervisor: starting
soroban rpc: waiting for ready state...
horizon: waiting for ingestion to catch up...
supervisor: 2023-04-04 11:27:58,827 INFO Included extra file "/opt/stellar/supervisor/etc/supervisord.conf.d/friendbot.conf" during parsing
supervisor: 2023-04-04 11:27:58,827 INFO Included extra file "/opt/stellar/supervisor/etc/supervisord.conf.d/horizon.conf" during parsing
supervisor: 2023-04-04 11:27:58,827 INFO Included extra file "/opt/stellar/supervisor/etc/supervisord.conf.d/nginx.conf" during parsing
supervisor: 2023-04-04 11:27:58,827 INFO Included extra file "/opt/stellar/supervisor/etc/supervisord.conf.d/postgresql.conf" during parsing
supervisor: 2023-04-04 11:27:58,827 INFO Included extra file "/opt/stellar/supervisor/etc/supervisord.conf.d/soroban-rpc.conf" during parsing
supervisor: 2023-04-04 11:27:58,828 INFO Included extra file "/opt/stellar/supervisor/etc/supervisord.conf.d/stellar-core.conf" during parsing
supervisor: 2023-04-04 11:27:58,828 INFO Set uid to user 0 succeeded
supervisor: 2023-04-04 11:27:58,832 INFO RPC interface 'supervisor' initialized
supervisor: 2023-04-04 11:27:58,832 CRIT Server 'unix_http_server' running without any HTTP authentication checking
supervisor: 2023-04-04 11:27:58,832 INFO supervisord started with pid 1
supervisor: 2023-04-04 11:27:59,835 INFO spawned: 'postgresql' with pid 354
supervisor: 2023-04-04 11:27:59,839 INFO spawned: 'stellar-core' with pid 355
supervisor: 2023-04-04 11:27:59,843 INFO spawned: 'horizon' with pid 356
supervisor: 2023-04-04 11:27:59,846 INFO spawned: 'friendbot' with pid 357
supervisor: 2023-04-04 11:27:59,848 INFO spawned: 'nginx' with pid 360
supervisor: 2023-04-04 11:27:59,852 INFO spawned: 'soroban-rpc' with pid 361
supervisor: 2023-04-04 11:28:01,093 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:28:01,093 INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:28:01,093 INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:28:01,093 INFO success: friendbot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:28:01,093 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:28:01,093 INFO success: soroban-rpc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:28:03,315 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:03,666 INFO spawned: 'soroban-rpc' with pid 483
supervisor: 2023-04-04 11:28:04,387 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:05,507 INFO spawned: 'soroban-rpc' with pid 574
supervisor: 2023-04-04 11:28:05,528 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:07,581 INFO spawned: 'soroban-rpc' with pid 591
supervisor: 2023-04-04 11:28:07,638 INFO exited: soroban-rpc (exit status 1; not expected)
stellar-core: Synced!
supervisor: 2023-04-04 11:28:08,684 INFO reaped unknown pid 316
stellar-core: Synced!; Armed with network upgrades: upgradetime=1970-01-01T00:00:00Z, protocolversion=20, basereserve=5000000
supervisor: 2023-04-04 11:28:09,872 INFO exited: friendbot (exit status 1; not expected)
supervisor: 2023-04-04 11:28:10,875 INFO spawned: 'friendbot' with pid 651
supervisor: 2023-04-04 11:28:10,877 INFO spawned: 'soroban-rpc' with pid 652
supervisor: 2023-04-04 11:28:10,948 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:11,966 INFO success: friendbot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stellar-core: Synced!
supervisor: 2023-04-04 11:28:15,683 INFO spawned: 'soroban-rpc' with pid 691
supervisor: 2023-04-04 11:28:15,736 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:20,913 INFO spawned: 'soroban-rpc' with pid 731
supervisor: 2023-04-04 11:28:20,940 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:27,220 INFO spawned: 'soroban-rpc' with pid 776
supervisor: 2023-04-04 11:28:27,277 INFO exited: soroban-rpc (exit status 1; not expected)
horizon: ingestion caught up
supervisor: 2023-04-04 11:28:35,144 INFO spawned: 'soroban-rpc' with pid 840
supervisor: 2023-04-04 11:28:35,213 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:43,227 INFO spawned: 'soroban-rpc' with pid 887
supervisor: 2023-04-04 11:28:43,268 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:28:53,255 INFO spawned: 'soroban-rpc' with pid 952
supervisor: 2023-04-04 11:28:53,307 INFO exited: soroban-rpc (exit status 1; not expected)
soroban rpc: waiting for ready state, 1 minutes...
supervisor: 2023-04-04 11:29:03,781 INFO spawned: 'soroban-rpc' with pid 1017
supervisor: 2023-04-04 11:29:03,836 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:29:15,133 INFO spawned: 'soroban-rpc' with pid 1094
supervisor: 2023-04-04 11:29:15,162 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:29:27,199 INFO spawned: 'soroban-rpc' with pid 1164
supervisor: 2023-04-04 11:29:27,252 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:29:41,102 INFO spawned: 'soroban-rpc' with pid 1254
supervisor: 2023-04-04 11:29:41,152 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:29:55,174 INFO spawned: 'soroban-rpc' with pid 1334
supervisor: 2023-04-04 11:29:55,303 INFO exited: soroban-rpc (exit status 1; not expected)
soroban rpc: waiting for ready state, 2 minutes...
supervisor: 2023-04-04 11:30:11,045 INFO spawned: 'soroban-rpc' with pid 1424
supervisor: 2023-04-04 11:30:11,113 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:30:27,620 INFO spawned: 'soroban-rpc' with pid 1520
supervisor: 2023-04-04 11:30:27,717 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:30:45,241 INFO spawned: 'soroban-rpc' with pid 1622
supervisor: 2023-04-04 11:30:45,332 INFO exited: soroban-rpc (exit status 1; not expected)
soroban rpc: waiting for ready state, 3 minutes...
supervisor: 2023-04-04 11:31:03,670 INFO spawned: 'soroban-rpc' with pid 1721
supervisor: 2023-04-04 11:31:03,699 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:23,291 INFO spawned: 'soroban-rpc' with pid 1829
supervisor: 2023-04-04 11:31:24,393 INFO success: soroban-rpc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:31:24,393 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:25,399 INFO spawned: 'soroban-rpc' with pid 1849
supervisor: 2023-04-04 11:31:25,522 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:26,657 INFO spawned: 'soroban-rpc' with pid 1860
supervisor: 2023-04-04 11:31:26,769 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:28,775 INFO spawned: 'soroban-rpc' with pid 1887
supervisor: 2023-04-04 11:31:28,866 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:32,108 INFO spawned: 'soroban-rpc' with pid 1912
supervisor: 2023-04-04 11:31:32,189 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:36,423 INFO spawned: 'soroban-rpc' with pid 1943
supervisor: 2023-04-04 11:31:36,485 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:41,930 INFO spawned: 'soroban-rpc' with pid 1985
supervisor: 2023-04-04 11:31:42,021 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:48,315 INFO spawned: 'soroban-rpc' with pid 2035
supervisor: 2023-04-04 11:31:48,406 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:31:55,821 INFO spawned: 'soroban-rpc' with pid 2080
supervisor: 2023-04-04 11:31:55,892 INFO exited: soroban-rpc (exit status 1; not expected)
soroban rpc: waiting for ready state, 4 minutes...
supervisor: 2023-04-04 11:32:04,773 INFO spawned: 'soroban-rpc' with pid 2141
supervisor: 2023-04-04 11:32:04,879 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:32:14,716 INFO spawned: 'soroban-rpc' with pid 2191
supervisor: 2023-04-04 11:32:15,827 INFO success: soroban-rpc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-04-04 11:32:15,827 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:32:16,834 INFO spawned: 'soroban-rpc' with pid 2211
supervisor: 2023-04-04 11:32:16,920 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:32:18,228 INFO spawned: 'soroban-rpc' with pid 2225
supervisor: 2023-04-04 11:32:18,322 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-04-04 11:32:20,329 INFO spawned: 'soroban-rpc' with pid 2251
supervisor: 2023-04-04 11:32:20,386 INFO exited: soroban-rpc (exit status 1; not expected)

Notice that the soroban-rcp exit with status 1. It seems that soroban-rcp can't start

When trying to deploy the contract with:

soroban contract deploy \
    --wasm target/wasm32-unknown-unknown/release/soroban_smart_contracts.wasm \
    --secret-key SBOX3EIKSEP7DIMBSL6FQ3T6ZZDH2KDW2WFF5OIQE45VR2QCKND3VXSB \
    --rpc-url http://localhost:8000/soroban/rpc \
    --network-passphrase 'Standalone Network ; February 2017'

I got:

error: jsonrpc error: RPC call failed: ErrorObject { code: MethodNotFound, message: "method not found", data: Some(RawValue("getAccount")) }

What did you expect to see?

After deploying the contract: The output should be the contract ID. Also, the soroban-rcp should start successfully

What did you see instead?

I get this error :

error: jsonrpc error: RPC call failed: ErrorObject { code: MethodNotFound, message: "method not found", data: Some(RawValue("getAccount")) }
@karolrojas07 karolrojas07 added the bug Something isn't working label Apr 4, 2023
@stellarsaur stellarsaur transferred this issue from stellar/stellar-cli Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mollykarcher @karolrojas07