RGB-WG / rgb-node

RGB node - the official server-side implementation

Home Page:https://rgb.tech

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error spawning bucketd service on contract register

louneskmt opened this issue · comments

I tried to register an RGB20 contract using rgb-cli:

$ docker compose exec -t rgb-node rgb-cli -n testnet contract register rgbc1q...tg7f

It seemed at first to be working has the following logs appeared:

Registering contract rgb1ecdfc5tds8dz9ehn7aj40m7eka5hwm0g5nd9skw7hvxx0q7natgq770n3x...
A new bucket daemon instance is started

But it than kept running without showing anything and an error appeared in the container logs:

instance1-rgb-node-1      | rgbd: RGB stash microservice
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG rgbd] CTL socket /var/lib/rgbd/ctl
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG rgbd] RPC socket 0.0.0.0:63963
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG rgbd] STORE socket /var/lib/sockets/store
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG rgbd] STORM socket /var/lib/sockets/storm
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG rgbd] Starting runtime ...
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG rgb_node::rgbd::service] Connecting to store service at /var/lib/sockets/store
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG store_rpc::client] Initializing runtime
instance1-rgb-node-1      | [2022-07-17T11:09:54Z INFO  rgb_node::rgbd::service] RGBd runtime started successfully
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG rgb_node::rgbd::service] Connecting to service buses /var/lib/sockets/storm, 0.0.0.0:63963, /var/lib/rgbd/ctl
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG microservices::esb::controller] Creating ESB session for service RPC located at 0.0.0.0:63963 with identity 'rgbd'
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG microservices::esb::controller] Creating ESB session for service STORM located at /var/lib/sockets/storm with identity 'rgbd'
instance1-rgb-node-1      | [2022-07-17T11:09:54Z DEBUG microservices::esb::controller] Creating ESB session for service CTL located at /var/lib/rgbd/ctl with identity 'rgbd'
instance1-rgb-node-1      | [2022-07-17T11:13:23Z DEBUG microservices::esb::controller] client<5263152711582617448> -> rgbd: hello(testnet, rgb-cli)
instance1-rgb-node-1      | [2022-07-17T11:13:23Z INFO  rgb_node::rgbd::service] Accepting new client with id 5263152711582617448 (rgb-cli)
instance1-rgb-node-1      | [2022-07-17T11:13:23Z DEBUG microservices::esb::controller] client<5263152711582617448> -> rgbd: accept(force: false, ...)
instance1-rgb-node-1      | [2022-07-17T11:13:23Z DEBUG microservices::launcher] Launching bucketd as a separate process using `/usr/local/bin/bucketd` as binary
instance1-rgb-node-1      | bucketd: RGB bucket microservice
instance1-rgb-node-1      | error: Found argument '--storm' which wasn't expected, or isn't valid in this context
instance1-rgb-node-1      | 
instance1-rgb-node-1      | 	Did you mean '--store'?
instance1-rgb-node-1      | 
instance1-rgb-node-1      | 	If you tried to supply `--storm` as a value rather than a flag, use `-- --storm`
instance1-rgb-node-1      | 
instance1-rgb-node-1      | USAGE:
instance1-rgb-node-1      |     bucketd --verbose --chain <CHAIN> --store <STORE_ENDPOINT>
instance1-rgb-node-1      | 
instance1-rgb-node-1      | For more information try --help

rgbd has been started with the following options (see full Docker stack):

-vvv --chain=testnet --storm=/var/lib/sockets/storm --store=/var/lib/sockets/store --data-dir=/var/lib/rgbd

Versions:

$ docker compose exec -t rgb-node bucketd --version
bucketd: RGB bucket microservice
bucketd 0.8.0-rc.1
$ docker compose exec -t rgb-node rgbd --version
rgbd: RGB stash microservice
rgbd 0.8.0-rc.1

@dr-orlovsky From what I'm understanding, the error comes from the config passed to the bucketd daemon.

let _handle = self.launch_daemon(Daemon::Bucketd, self.config.clone())?;
It looks like it doesn't take only the shared opts but also the storm_endpoint as well, not sure why.

Just skip the --storm-endpoint argument for now when starting rgbd - or run with --threaded. I'll fix in the next version.

bucketd does not have that parameter, but rgbd passes all parameters to the child daemons.