Maintenance

if found a same problem error in check log

journalctl -fu slinky --no-hostname

Check your gRPC port and setting Oracle in app.toml

  • gRPC

Address defines the gRPC server address to bind to.

address = "localhost:9090"

  • Oracle

###############################################################################
###                                  Oracle                                 ###
###############################################################################
[oracle]
# Enabled indicates whether the oracle is enabled.
enabled = "true"

# Oracle Address is the URL of the out of process oracle sidecar. This is used to
# connect to the oracle sidecar when the application boots up. Note that the address
# can be modified at any point, but will only take effect after the application is
# restarted. This can be the address of an oracle container running on the same
# machine or a remote machine.
oracle_address = "127.0.0.1:8080"

# Client Timeout is the time that the client is willing to wait for responses from 
# the oracle before timing out.
client_timeout = "500ms"

# MetricsEnabled determines whether oracle metrics are enabled. Specifically
# this enables instrumentation of the oracle client and the interaction between
# the oracle and the app.
metrics_enabled = "false"

Change systemd

sudo nano /etc/systemd/system/slinky.service

ExecStart=$(which slinky) --oracle-config-path $HOME/slinky/config/core/oracle.json --market-map-endpoint 0.0.0.0:<port grpc>

Reload systemd

sudo systemctl daemon-reload 
sudo systemctl restart slinky.service

Check the systemd log

journalctl -fu slinky --no-hostname

Last updated