Node deployment help, values unclear

General
1

Hello,

I’m working through the steps to deploy a node., and the YAML configuration is not clear to me on a few points:

  1. rpc.abc.com appears to be a placeholder value, where do I find the actual values?
  2. Do I need to set up a PostgreSQL or CockroachDB instance?
1 Like
2
  1. endpoint is the interface returning the raw data of the corresponding network. For blockchain networks, you need to source your own RPC endpoints. For the VSL you can use https://rpc.rss3.io. For non-blockchain networks such as farcaster you need your own hubble, IPFS you need your own gateway.
  2. For Alpha stage, no. In fact you do not need endpoint as well.

Note:

  1. for the upcoming Beta stage, you will be able to operate Public Good Nodes which requires endpoint and a database. All Alpha Nodes can continue operating.
  2. for the Production stage after Beta, all Alpha Nodes are required to upgrade to Production.
3

Also we are internally testing a new and simplified config structure as well as a frontend page to generate a config. Stay tuned.

4

I’d like to get a node up in the alpha stage. What would a minimum viable config.yaml look like? This is what I’ve drafted up:

---
environment: production
discovery:
  maintainer:
    # the wallet address used by you during your registration on the RSS3
    # Explorer
    evm_address: TODO
    # the signature obtained on the RSS3 Explorer, it will be used to verify
    # your ownership of this Node
    signature: TODO
  server:
    # This is an endpoint I run on my server?
    endpoint: https://myendpoint.example.com/
    global_indexer_endpoint: https://gi.rss3.io
5

Hey buddy, check out 🟦 Node

6

@jeffca, hey buddy, I read through that document (and many others) before posting here. The options in the YAML document are not well documented, hence coming here.

7

you can generate the configuration from here:

https://explorer.rss3.io/nodes/register/node-coverage

8

Alright, I have a fresh Ubuntu 22.04 machine with Docker installed and I generated a configuration file using the tool @albert linked, but the containers just keep restarting. Here’s my config file

---
environment: production
type: beta
discovery:
  maintainer:
    evm_address: 'redacted'
    signature: 'redacted'
  server:
    global_indexer_endpoint: https://gi.rss3.io
    # Our endpoint
    endpoint: https://my_ip_address
database:
  driver: cockroachdb
  partition: true
  uri: postgres://root@cockroachdb:26257/defaultdb
stream:
  enable: false
observability:
  opentelemetry:
    metrics:
      enable: false
      endpoint: 0.0.0.0:9090
    traces:
      enable: false
      insecure: true
      endpoint: localhost:4318
redis:
  endpoints: [redis:6379]
  disable_cache: true
endpoints:
  crossbell:
    url: https://rpc.crossbell.io
  linea:
    url: https://rpc.linea.build
  vsl:
    url: https://rpc.rss3.io
component:
  decentralized:
    - id: arweave-paragraph
      network: arweave
      worker: paragraph
    - id: linea-core
      network: linea
      worker: core
      endpoint: linea
    - id: linea-stargate
      network: linea
      worker: stargate
      endpoint: linea
    - id: linea-uniswap
      network: linea
      worker: uniswap
      endpoint: linea
    - id: vsl-core
      network: vsl
      worker: core
      endpoint: vsl
    - id: vsl-rss3
      network: vsl
      worker: rss3
      endpoint: vsl
    - id: vsl-vsl
      network: vsl
      worker: vsl
      endpoint: vsl

And docker ps output

CONTAINER ID   IMAGE                           COMMAND                  CREATED         STATUS                          PORTS                 NAMES
1db2d6175125   rss3/node:v0.5.9                "./node --module=wor…"   5 minutes ago   Restarting (1) 46 seconds ago                         node-linea-stargate
0188e986a224   rss3/node:v0.5.9                "./node --module=core"   5 minutes ago   Restarting (1) 45 seconds ago                         rss3_node_core
26132673d93a   rss3/node:v0.5.9                "./node --module=wor…"   5 minutes ago   Restarting (1) 46 seconds ago                         node-arweave-paragraph
18044486b0ec   rss3/node:v0.5.9                "./node --module=wor…"   5 minutes ago   Restarting (1) 44 seconds ago                         node-vsl-rss3
ab53feba6983   rss3/node:v0.5.9                "./node --module=wor…"   5 minutes ago   Restarting (1) 45 seconds ago                         node-vsl-core
3bf2f76d719d   redis:7-alpine                  "docker-entrypoint.s…"   5 minutes ago   Up 5 minutes                    6379/tcp              rss3_node_redis
0ae7f7a084ed   cockroachdb/cockroach:v23.2.5   "/cockroach/cockroac…"   5 minutes ago   Up 5 minutes                    8080/tcp, 26257/tcp   rss3_node_cockroachdb
84eba1ee2194   rss3/node:v0.5.9                "./node --module=wor…"   5 minutes ago   Restarting (1) 44 seconds ago                         node-linea-core
6c754c8a4a9b   rss3/node:v0.5.9                "./node --module=wor…"   5 minutes ago   Restarting (1) 46 seconds ago                         node-vsl-vsl
4037c731c1de   rss3/node:v0.5.9                "./node --module=wor…"   5 minutes ago   Restarting (1) 45 seconds ago                         node-linea-uniswap
9

I suspect the issue is:

uri: postgres://root@cockroachdb:26257/defaultdb

and

redis:
  endpoints: [redis:6379]

The correct values should be

uri: postgres://root@rss3_node_cockroachdb:26257/defaultdb

and

redis:
  endpoint: rss3_node_redis:6379

unless you specifically changed container names for cockroachdb and redis, in this case you should always ensure the values here are correct for docker discovery.

if the above changes did not solve the problem, post docker logs --tail -10 for any restarting container.

free feel to open a ticket on discord, I might be slow to respond here.