How to resolve "No workers configured, nothing to do" condition?

Hello team crossbar,

I was using the crossbar 2/3 months ego. But later due to someother work I just stopped using it. Now I am trying to use the crossbar for my work. But whenever I run (by using "/snap/bin/crossbar start " command in the terminal.) the crossbar I am getting

“2020-05-28T09:00:06+0530 [Controller 3244] Booting node from local configuration [parallel_worker_start=False] … <crossbar.node.node.Node.boot_from_config>
2020-05-28T09:00:06+0530 [Controller 3244] No workers configured, nothing to do” message.

But at the end it is also showing " 2020-05-28T09:00:06+0530 [Controller 3244] Ok, local node configuration booted successfully! " message.

May I know why it happening here. Because of ehich I am not able to connect my WAMP C++ application.

What went wrong here? Why the crossbar is not working properly here?

Below is the whole log on running the crossbar.

020-05-28T09:00:06+0530 [Controller 3244]
2020-05-28T09:00:06+0530 [Controller 3244] :::::::::::::::::
2020-05-28T09:00:06+0530 [Controller 3244] ::::: _____ __
2020-05-28T09:00:06+0530 [Controller 3244] ::::: : ::::: / /_ ___ ___ ___ / / ___ _ ____
2020-05-28T09:00:06+0530 [Controller 3244] ::::::: ::::::: / /__ / // _ \ (-< (-< / _ / _ `// /
2020-05-28T09:00:06+0530 [Controller 3244] ::::: : ::::: _
//_/ _
//////.__/_,//_/
2020-05-28T09:00:06+0530 [Controller 3244] :::::
2020-05-28T09:00:06+0530 [Controller 3244] ::::::::::::::::: Crossbar v20.1.1
2020-05-28T09:00:06+0530 [Controller 3244]
2020-05-28T09:00:06+0530 [Controller 3244] Copyright © 2013-2020 Crossbar.io Technologies GmbH, licensed under AGPL 3.0.
2020-05-28T09:00:06+0530 [Controller 3244]
2020-05-28T09:00:06+0530 [Controller 3244] Initializing <crossbar.node.node.Node> as node [realm=crossbar, cbdir=/home/siddhu]
2020-05-28T09:00:06+0530 [Controller 3244] New node key pair generated! Public key is 0xa7a5b84fd99652cf5bab01b015d4c95d3085473076c0ebfbde451ce41fe53608
2020-05-28T09:00:06+0530 [Controller 3244] File permissions on node private key fixed
2020-05-28T09:00:06+0530 [Controller 3244] Node key loaded from /home/siddhu/key.priv
2020-05-28T09:00:06+0530 [Controller 3244] Node configuration loaded [config_source=empty, config_path=None]
2020-05-28T09:00:06+0530 [Controller 3244] Entering event reactor …
2020-05-28T09:00:06+0530 [Controller 3244] Starting standalone node <crossbar.node.node.Node.start>
2020-05-28T09:00:06+0530 [Controller 3244] Node ID siddhu-3244 set from hostname/pid
2020-05-28T09:00:06+0530 [Controller 3244] RouterFactory.start_realm: router created for realm “crossbar”
2020-05-28T09:00:06+0530 [Controller 3244] No extra node router roles
2020-05-28T09:00:06+0530 [Controller 3244] Router.attach(session=6651248655131751)
2020-05-28T09:00:06+0530 [Controller 3244] Router.attach(session=6651248655131751): attached session 6651248655131751 to router realm “crossbar”
2020-05-28T09:00:06+0530 [Controller 3244] RouterServiceAgent: realm service session attached (details=
SessionDetails(realm=,
session=6651248655131751,
authid=,
authrole=,
authmethod=None,
authprovider=None,
authextra=None,
serializer=,
resumed=None,
resumable=None,
resume_token=None))
2020-05-28T09:00:06+0530 [Controller 3244] RouterServiceAgent: realm service session ready (realm_name=“crossbar”, on_ready=None)
2020-05-28T09:00:06+0530 [Controller 3244] Router.attach(session=3571466862836513)
2020-05-28T09:00:06+0530 [Controller 3244] Router.attach(session=3571466862836513): attached session 3571466862836513 to router realm “crossbar”
2020-05-28T09:00:06+0530 [Controller 3244] Joined realm ‘crossbar’ on node management router
2020-05-28T09:00:06+0530 [Controller 3244] Registered 23 management procedures on realm “crossbar”
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_cpu_affinity
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_cpu_count
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_cpus
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_manhole
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_process_info
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_process_monitor
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_process_stats
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_status
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_system_stats
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_worker
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_worker_log
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.get_workers
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.set_cpu_affinity
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.set_process_stats_monitoring
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.shutdown
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.start_manhole
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.start_worker
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.started
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.stop_manhole
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.stop_worker
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.trigger_gc
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.uptime
2020-05-28T09:00:06+0530 [Controller 3244] crossbar.utcnow
2020-05-28T09:00:06+0530 [Controller 3244] Signal handler installed on process 3244 thread 140346538276672
2020-05-28T09:00:06+0530 [Controller 3244] Using default node shutdown triggers [‘shutdown_on_worker_exit’]
2020-05-28T09:00:06+0530 [Controller 3244] Booting node <crossbar.node.node.Node.boot>
2020-05-28T09:00:06+0530 [Controller 3244] Booting node from local configuration [parallel_worker_start=False] … <crossbar.node.node.Node.boot_from_config>
2020-05-28T09:00:06+0530 [Controller 3244] No workers configured, nothing to do
2020-05-28T09:00:06+0530 [Controller 3244] Ok, local node configuration booted successfully!
^C2020-05-28T09:00:37+0530 [Controller 3244] Controller received SIGINT [signal=2]: shutting down node [shutdown_was_clean=True] …
2020-05-28T09:00:37+0530 [Controller 3244] Node shutdown requested (restart=False, mode=None, reactor.running=True) …
siddhu@siddhu:~$ /snap/bin/crossbar start

Eagerly waitng for the response.

Thanks,
Siddhartha V

Crossbar.io is a multi-process server. The “Controller” process is always started, and controls the local node. “Worker” processes come in different flavors (Router, Proxy, Container, Guest), and workers are only started when they are defined in the node configuration. So in your case, the node configuration being used doesn’t have any workers configured. “Ok, local node configuration booted successfully!” is the final log message after the node controller has started everything (which is 0 workers in your case).

try sth like:

/snap/bin/crossbar start --cbdir=/home/whatever/mynode/.crossbar --config=config.json

see:

(cpy382_1) oberstet@intel-nuci7:~$ crossbar start --help

usage: crossbar start [-h] [--color {true,false,auto}] [--loglevel {none,error,warn,info,debug,trace}]
                      [--logformat {syslogd,standard,none}] [--logdir LOGDIR] [--logtofile] [--cbdir CBDIR] [--config CONFIG]
                      [--shutdownafter SHUTDOWNAFTER]

optional arguments:
  -h, --help            show this help message and exit
  --color {true,false,auto}
                        If logging should be colored.
  --loglevel {none,error,warn,info,debug,trace}
                        How much Crossbar.io should log to the terminal, in order of verbosity.
  --logformat {syslogd,standard,none}
                        The format of the logs -- suitable for syslogd, not colored, or colored.
  --logdir LOGDIR       Crossbar.io log directory (default: <Crossbar Node Directory>/)
  --logtofile           Whether or not to log to file
  --cbdir CBDIR         Crossbar.io node directory (overrides ${CROSSBAR_DIR} and the default ./.crossbar)
  --config CONFIG       Crossbar.io configuration file (overrides default CBDIR/config.json)
  --shutdownafter SHUTDOWNAFTER
                        Automatically shutdown node after this many seconds.
(cpy382_1) oberstet@intel-nuci7:~$