crossbar start-worker

#1

hi

do you know how crossbar start-worker works ? what is the difference between node id and worker id option ? do you have an example ?

$ ./bin/crossbar start-worker --title hello -k app.hello.Component -r realm1 -w hello001

CROSSBAR_RICH_LOGGING_ENABLE=True
Started hello worker "hello001" on node "None" [app.hello.Component / PyPy-EPollReactor]
{"worker_title": "hello", "klass": "app.hello.Component", "node_id": null, "worker_id": "hello001", "pid": 4730, "python": "PyPy", "reactor": "EPollReactor", "log_time": 1522854805.797308, "level": "info", "namespace": "crossbar.worker.process.run", "text": "Started hello worker \"hello001\" on node \"None\" [app.hello.Component / PyPy-EPollReactor]"}Unhandled exception: [Errno 9] Bad file descriptor
{"e": "IOError(9, 'Bad file descriptor')", "log_time": 1522854805.799102, "level": "info", "namespace": "crossbar.worker.process.run", "text": "Unhandled exception: [Errno 9] Bad file descriptor"}

thanks

ninou

0 Likes

#2

hi

do you know how crossbar start-worker works ? what is the difference

This is not a public API or user feature. Workers can only be started
from the node controller process itself.

···

Am 05.04.2018 um 09:12 schrieb ninou:

between node id and worker id option ? do you have an example ?

$ ./bin/crossbar start-worker --title hello -k app.hello.Component -r
realm1 -w hello001

CROSSBAR_RICH_LOGGING_ENABLE=True
Started hello worker "hello001" on node "None" [app.hello.Component /
PyPy-EPollReactor]
{"worker_title": "hello", "klass": "app.hello.Component", "node_id":
null, "worker_id": "hello001", "pid": 4730, "python": "PyPy", "reactor":
"EPollReactor", "log_time": 1522854805.797308, "level": "info",
"namespace": "crossbar.worker.process.run", "text": "Started hello
worker \"hello001\" on node \"None\" [app.hello.Component /
PyPy-EPollReactor]"}Unhandled exception: [Errno 9] Bad file descriptor
{"e": "IOError(9, 'Bad file descriptor')", "log_time":
1522854805.799102, "level": "info", "namespace":
"crossbar.worker.process.run", "text": "Unhandled exception: [Errno 9]
Bad file descriptor"}

thanks

ninou

0 Likes

#3

We can probably add some explicit text to the help of start-worker command line option that its a private API and is not supposed to work.

I’ll prepare a PR.

···

On Thursday, April 5, 2018 at 5:10:03 PM UTC+5, Tobias Oberstein wrote:

Am 05.04.2018 um 09:12 schrieb ninou:

hi

do you know how crossbar start-worker works ? what is the difference

This is not a public API or user feature. Workers can only be started

from the node controller process itself.

between node id and worker id option ? do you have an example ?

$ ./bin/crossbar start-worker --title hello -k app.hello.Component -r

realm1 -w hello001

CROSSBAR_RICH_LOGGING_ENABLE=True

Started hello worker “hello001” on node “None” [app.hello.Component /

PyPy-EPollReactor]

{“worker_title”: “hello”, “klass”: “app.hello.Component”, “node_id”:

null, “worker_id”: “hello001”, “pid”: 4730, “python”: “PyPy”, “reactor”:

“EPollReactor”, “log_time”: 1522854805.797308, “level”: “info”,

“namespace”: “crossbar.worker.process.run”, “text”: "Started hello

worker “hello001” on node “None” [app.hello.Component /

PyPy-EPollReactor]"}Unhandled exception: [Errno 9] Bad file descriptor

{“e”: “IOError(9, ‘Bad file descriptor’)”, “log_time”:

1522854805.799102, “level”: “info”, “namespace”:

“crossbar.worker.process.run”, “text”: "Unhandled exception: [Errno 9]

Bad file descriptor"}

thanks

ninou

0 Likes