Crossbar ends after some period of time

#1

Dear All,

2017-02-16T09:42:55+0000 [Controller 4103] Node configuration loaded from ‘config.json’
2017-02-16T09:42:55+0000 [Controller 4103] __ __ __ __ __ __ __ __
2017-02-16T09:42:55+0000 [Controller 4103] / |)/ //`|) /\ |) |/
2017-02-16T09:42:55+0000 [Controller 4103] ,| /././|)/~| . |__/
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Crossbar.io Version: 16.10.1
2017-02-16T09:42:55+0000 [Controller 4103] Node Public Key: d689234365ec7faf617f4c88446e492b9f628ba53d70c96859193a3f4328a134
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Running from node directory ‘/srv/TestBed/.crossbar’
2017-02-16T09:42:55+0000 [Controller 4103] Controller process starting (CPython-EPollReactor) …
2017-02-16T09:42:55+0000 [Controller 4103] Using default node shutdown triggers [u’shutdown_on_worker_exit’]
2017-02-16T09:42:55+0000 [Controller 4103] Joined realm ‘crossbar’ on node management router
2017-02-16T09:42:55+0000 [Controller 4103] Configuring node from local configuration …
2017-02-16T09:42:55+0000 [Controller 4103] Starting 1 workers …
2017-02-16T09:42:55+0000 [Controller 4103] Starting Router with ID ‘worker-001’…
2017-02-16T09:42:56+0000 [Router 4112] Worker process starting (CPython-EPollReactor) …
2017-02-16T09:42:57+0000 [Controller 4103] Router with ID ‘worker-001’ and PID 4112 started
2017-02-16T09:42:57+0000 [Router 4112] Realm ‘TestBed’ started
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: realm ‘realm-001’ (named ‘TestBed’) started
2017-02-16T09:42:57+0000 [Router 4112] role role-001 on realm realm-001 started
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: role ‘role-001’ (named ‘anonymous’) started on realm ‘realm-001’
2017-02-16T09:42:57+0000 [Router 4112] Site starting on 9000
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: transport ‘transport-001’ started
2017-02-16T09:42:57+0000 [Controller 4103] Local node configuration applied.
2017-02-16T13:15:17+0000 [Controller 4103] Native worker connection closed uncleanly: A process has ended with a probable error condition: process ended by signal 1.
2017-02-16T13:15:17+0000 [Controller 4103] Node worker worker-001 ended with error ([Failure instance: Traceback (failure with no frames): <class ‘twisted.internet.error.ProcessTerminated’>: A process has ended with a probable error condition: process ended by signal 1.
])
2017-02-16T13:15:17+0000 [Controller 4103] Node worker ended, and trigger ‘shutdown_on_worker_exit’ active
2017-02-16T13:15:17+0000 [Controller 4103] Node shutting down …
2017-02-16T13:15:17+0000 [Controller 4103] Shutting down node…
2017-02-16T13:15:17+0000 [Controller 4103] sending TERM to subprocess 4112

python:
Python 2.7.5 (default, Nov 6 2016, 00:28:07)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux2

OS:
Linux vm 4.4.19-1-pve #1 SMP Wed Sep 14 14:33:50 CEST 2016 x86_64 x86_64 x86_64 GNU/Linux

Thanks for any help.

I asked this question on github but were redirected here, by Tobias Oberstein (thanks to him) and he pointed:

Your Node.js worker has exited with error, and due to the default Crossbar.io node policy, the Crossbar.io node shuts down completely.

But I dont use nodejs I dont have it.

0 Likes

#2

Hi,

sorry, I was misreading the log. You are not running NodeJS;)

Could you please start Crossbar.io with debug logging enabled and repost the trace you get?

crossbar start --loglevel=debug

Cheers,
/Tobias

···

Am 16.02.2017 um 18:00 schrieb gms...@gmail.com:

Dear All,

2017-02-16T09:42:55+0000 [Controller 4103] Node configuration loaded from
'config.json'
2017-02-16T09:42:55+0000 [Controller 4103] __ __ __ __ __ __ __ __
2017-02-16T09:42:55+0000 [Controller 4103] / |__)/ \/__/`|) /\ |) |/
2017-02-16T09:42:55+0000 [Controller 4103] __,| \/././|__)/~| . |__/
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Crossbar.io Version: 16.10.1
2017-02-16T09:42:55+0000 [Controller 4103] Node Public Key:
d689234365ec7faf617f4c88446e492b9f628ba53d70c96859193a3f4328a134
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Running from node directory
'/srv/TestBed/.crossbar'
2017-02-16T09:42:55+0000 [Controller 4103] Controller process starting
(CPython-EPollReactor) ..
2017-02-16T09:42:55+0000 [Controller 4103] Using default node shutdown
triggers [u'shutdown_on_worker_exit']
2017-02-16T09:42:55+0000 [Controller 4103] Joined realm 'crossbar' on node
management router
2017-02-16T09:42:55+0000 [Controller 4103] Configuring node from local
configuration ...
2017-02-16T09:42:55+0000 [Controller 4103] Starting 1 workers ...
2017-02-16T09:42:55+0000 [Controller 4103] Starting Router with ID
'worker-001'...
2017-02-16T09:42:56+0000 [Router 4112] Worker process starting
(CPython-EPollReactor) ..
2017-02-16T09:42:57+0000 [Controller 4103] Router with ID 'worker-001' and
PID 4112 started
2017-02-16T09:42:57+0000 [Router 4112] Realm 'TestBed' started
2017-02-16T09:42:57+0000 [Controller 4103] Router 'worker-001': realm
'realm-001' (named 'TestBed') started
2017-02-16T09:42:57+0000 [Router 4112] role role-001 on realm realm-001
started
2017-02-16T09:42:57+0000 [Controller 4103] Router 'worker-001': role
'role-001' (named 'anonymous') started on realm 'realm-001'
2017-02-16T09:42:57+0000 [Router 4112] Site starting on 9000
2017-02-16T09:42:57+0000 [Controller 4103] Router 'worker-001': transport
'transport-001' started
2017-02-16T09:42:57+0000 [Controller 4103] Local node configuration applied.
2017-02-16T13:15:17+0000 [Controller 4103] Native worker connection closed
uncleanly: A process has ended with a probable error condition: process
ended by signal 1.
2017-02-16T13:15:17+0000 [Controller 4103] Node worker worker-001 ended
with error ([Failure instance: Traceback (failure with no frames): <class
'twisted.internet.error.ProcessTerminated'>: A process has ended with a
probable error condition: process ended by signal 1.
])
2017-02-16T13:15:17+0000 [Controller 4103] Node worker ended, and trigger
'shutdown_on_worker_exit' active
2017-02-16T13:15:17+0000 [Controller 4103] Node shutting down ..
2017-02-16T13:15:17+0000 [Controller 4103] Shutting down node...
2017-02-16T13:15:17+0000 [Controller 4103] sending TERM to subprocess 4112

python:
Python 2.7.5 (default, Nov 6 2016, 00:28:07)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux2

OS:
Linux vm 4.4.19-1-pve #1 SMP Wed Sep 14 14:33:50 CEST 2016 x86_64 x86_64
x86_64 GNU/Linux

Thanks for any help.

I asked this question on github but were redirected here, by Tobias
Oberstein (thanks to him) and he pointed:

Your Node.js worker has exited with error, and due to the default

Crossbar.io node policy, the Crossbar.io node shuts down completely.

But I dont use nodejs I dont have it.

0 Likes

#3

Hi Tobias,

I attached debug logs.

Regards,
Roman

crossbar.out (199 KB)

···

четверг, 16 февраля 2017 г., 19:18:49 UTC+2 пользователь Tobias Oberstein написал:

Hi,

sorry, I was misreading the log. You are not running NodeJS;)

Could you please start Crossbar.io with debug logging enabled and repost
the trace you get?

crossbar start --loglevel=debug

Cheers,

/Tobias

Am 16.02.2017 um 18:00 schrieb gms...@gmail.com:

Dear All,

2017-02-16T09:42:55+0000 [Controller 4103] Node configuration loaded from

‘config.json’

2017-02-16T09:42:55+0000 [Controller 4103] __ __ __ __ __ __ __ __

2017-02-16T09:42:55+0000 [Controller 4103] / |)/ //`|) /\ |) |/

2017-02-16T09:42:55+0000 [Controller 4103] ,| /././|)/~| . |__/

2017-02-16T09:42:55+0000 [Controller 4103]

2017-02-16T09:42:55+0000 [Controller 4103] Crossbar.io Version: 16.10.1

2017-02-16T09:42:55+0000 [Controller 4103] Node Public Key:

d689234365ec7faf617f4c88446e492b9f628ba53d70c96859193a3f4328a134

2017-02-16T09:42:55+0000 [Controller 4103]

2017-02-16T09:42:55+0000 [Controller 4103] Running from node directory

‘/srv/TestBed/.crossbar’

2017-02-16T09:42:55+0000 [Controller 4103] Controller process starting

(CPython-EPollReactor) …

2017-02-16T09:42:55+0000 [Controller 4103] Using default node shutdown

triggers [u’shutdown_on_worker_exit’]

2017-02-16T09:42:55+0000 [Controller 4103] Joined realm ‘crossbar’ on node

management router

2017-02-16T09:42:55+0000 [Controller 4103] Configuring node from local

configuration …

2017-02-16T09:42:55+0000 [Controller 4103] Starting 1 workers …

2017-02-16T09:42:55+0000 [Controller 4103] Starting Router with ID

‘worker-001’…

2017-02-16T09:42:56+0000 [Router 4112] Worker process starting

(CPython-EPollReactor) …

2017-02-16T09:42:57+0000 [Controller 4103] Router with ID ‘worker-001’ and

PID 4112 started

2017-02-16T09:42:57+0000 [Router 4112] Realm ‘TestBed’ started

2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: realm

‘realm-001’ (named ‘TestBed’) started

2017-02-16T09:42:57+0000 [Router 4112] role role-001 on realm realm-001

started

2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: role

‘role-001’ (named ‘anonymous’) started on realm ‘realm-001’

2017-02-16T09:42:57+0000 [Router 4112] Site starting on 9000

2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: transport

‘transport-001’ started

2017-02-16T09:42:57+0000 [Controller 4103] Local node configuration applied.

2017-02-16T13:15:17+0000 [Controller 4103] Native worker connection closed

uncleanly: A process has ended with a probable error condition: process

ended by signal 1.

2017-02-16T13:15:17+0000 [Controller 4103] Node worker worker-001 ended

with error ([Failure instance: Traceback (failure with no frames): <class

‘twisted.internet.error.ProcessTerminated’>: A process has ended with a

probable error condition: process ended by signal 1.

])

2017-02-16T13:15:17+0000 [Controller 4103] Node worker ended, and trigger

‘shutdown_on_worker_exit’ active

2017-02-16T13:15:17+0000 [Controller 4103] Node shutting down …

2017-02-16T13:15:17+0000 [Controller 4103] Shutting down node…

2017-02-16T13:15:17+0000 [Controller 4103] sending TERM to subprocess 4112

python:

Python 2.7.5 (default, Nov 6 2016, 00:28:07)

[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux2

OS:

Linux vm 4.4.19-1-pve #1 SMP Wed Sep 14 14:33:50 CEST 2016 x86_64 x86_64

x86_64 GNU/Linux

Thanks for any help.

I asked this question on github but were redirected here, by Tobias

Oberstein (thanks to him) and he pointed:

Your Node.js worker has exited with error, and due to the default

Crossbar.io node policy, the Crossbar.io node shuts down completely.

But I dont use nodejs I dont have it.

0 Likes

#4

Hi Roman,

you can see the (router) worker process "worker-001" successfully starting, and then running for several minutes, happily answering the ping requests sent from the node controller.

Then, suddenly, the router process ends with

"process ended by signal 1"

signal 1 = SIGHUP

Something is sending this signal to the worker process .. are you starting Crossbar.io in an interactive SSH shell, and that SSH connection ends?

Is this a OS container where Crossbar.io runs within?

Try starting Crossbar.io properly daemonized.

Cheers,
/Tobias

2017-02-17T09:08:09+0000 [Router 6389 crossbar.router.protocol.WampWebSocketServerProtocol] WebSocketProtocol.onPing(payload=<4 bytes>)
2017-02-17T09:08:11+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 266, 'bytes': 146701}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:16+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 266, 'bytes': 146701}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:19+0000 [Router 6389 crossbar.router.protocol.WampWebSocketServerProtocol] WebSocketProtocol.onPing(payload=<4 bytes>)
2017-02-17T09:08:21+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 267, 'bytes': 146893}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:26+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 267, 'bytes': 146893}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:29+0000 [Router 6389 crossbar.router.protocol.WampWebSocketServerProtocol] WebSocketProtocol.onPing(payload=<4 bytes>)
2017-02-17T09:08:31+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 268, 'bytes': 147085}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:36+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 268, 'bytes': 147085}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:39+0000 [Router 6389 crossbar.router.protocol.WampWebSocketServerProtocol] WebSocketProtocol.onPing(payload=<4 bytes>)
2017-02-17T09:08:41+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 269, 'bytes': 147277}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:46+0000 [Controller 6380 crossbar.controller.processtypes.RouterWorkerProcess] Worker worker-001 -> Controller traffic: {2: {'count': 269, 'bytes': 147277}, 3: {'count': 8, 'bytes': 3287}}
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.native.NativeWorkerClientProtocol] Native worker connection closed uncleanly: A process has ended with a probable error condition: process ended by signal 1.
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.native.NativeWorkerClientProtocol] Connection to/from process:6389 was lost in a non-clean fashion: process ended by signal 1
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.native.NativeWorkerClientProtocol] _connectionLost: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ProcessTerminated'>: A process has ended with a probable error condition: process ended by signal 1.
]
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.native.NativeWorkerClientProtocol] WAMP-over-WebSocket transport lost: wasClean=False, code=1006, reason="connection was closed uncleanly (peer dropped the TCP connection without previous WebSocket closing handshake)"
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.process.NodeControllerSession] Node worker worker-001 ended with error ([Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ProcessTerminated'>: A process has ended with a probable error condition: process ended by signal 1.
])
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.process.NodeControllerSession] Node worker ended, and trigger 'shutdown_on_worker_exit' active
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.process.NodeControllerSession] Node shutting down ..
2017-02-17T09:08:49+0000 [Controller 6380 crossbar.controller.process.NodeControllerSession] Shutting down node...

···

Am 17.02.2017 um 14:00 schrieb gms...@gmail.com:

Hi Tobias,

I attached debug logs.

Regards,
Roman

четверг, 16 февраля 2017 г., 19:18:49 UTC+2 пользователь Tobias Oberstein > написал:

Hi,

sorry, I was misreading the log. You are not running NodeJS;)

Could you please start Crossbar.io with debug logging enabled and repost
the trace you get?

crossbar start --loglevel=debug

Cheers,
/Tobias

Am 16.02.2017 um 18:00 schrieb gms...@gmail.com <javascript:>:

Dear All,

2017-02-16T09:42:55+0000 [Controller 4103] Node configuration loaded

from

'config.json'
2017-02-16T09:42:55+0000 [Controller 4103] __ __ __ __ __ __ __ __
2017-02-16T09:42:55+0000 [Controller 4103] / |__)/ \/__/`|) /\ |) |/
2017-02-16T09:42:55+0000 [Controller 4103] __,| \/././|__)/~| . |__/
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Crossbar.io Version: 16.10.1
2017-02-16T09:42:55+0000 [Controller 4103] Node Public Key:
d689234365ec7faf617f4c88446e492b9f628ba53d70c96859193a3f4328a134
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Running from node directory
'/srv/TestBed/.crossbar'
2017-02-16T09:42:55+0000 [Controller 4103] Controller process starting
(CPython-EPollReactor) ..
2017-02-16T09:42:55+0000 [Controller 4103] Using default node shutdown
triggers [u'shutdown_on_worker_exit']
2017-02-16T09:42:55+0000 [Controller 4103] Joined realm 'crossbar' on

node

management router
2017-02-16T09:42:55+0000 [Controller 4103] Configuring node from local
configuration ...
2017-02-16T09:42:55+0000 [Controller 4103] Starting 1 workers ...
2017-02-16T09:42:55+0000 [Controller 4103] Starting Router with ID
'worker-001'...
2017-02-16T09:42:56+0000 [Router 4112] Worker process starting
(CPython-EPollReactor) ..
2017-02-16T09:42:57+0000 [Controller 4103] Router with ID 'worker-001'

and

PID 4112 started
2017-02-16T09:42:57+0000 [Router 4112] Realm 'TestBed' started
2017-02-16T09:42:57+0000 [Controller 4103] Router 'worker-001': realm
'realm-001' (named 'TestBed') started
2017-02-16T09:42:57+0000 [Router 4112] role role-001 on realm realm-001
started
2017-02-16T09:42:57+0000 [Controller 4103] Router 'worker-001': role
'role-001' (named 'anonymous') started on realm 'realm-001'
2017-02-16T09:42:57+0000 [Router 4112] Site starting on 9000
2017-02-16T09:42:57+0000 [Controller 4103] Router 'worker-001':

transport

'transport-001' started
2017-02-16T09:42:57+0000 [Controller 4103] Local node configuration

applied.

2017-02-16T13:15:17+0000 [Controller 4103] Native worker connection

closed

uncleanly: A process has ended with a probable error condition: process
ended by signal 1.
2017-02-16T13:15:17+0000 [Controller 4103] Node worker worker-001 ended
with error ([Failure instance: Traceback (failure with no frames):

<class

'twisted.internet.error.ProcessTerminated'>: A process has ended with a
probable error condition: process ended by signal 1.
])
2017-02-16T13:15:17+0000 [Controller 4103] Node worker ended, and

trigger

'shutdown_on_worker_exit' active
2017-02-16T13:15:17+0000 [Controller 4103] Node shutting down ..
2017-02-16T13:15:17+0000 [Controller 4103] Shutting down node...
2017-02-16T13:15:17+0000 [Controller 4103] sending TERM to subprocess

4112

python:
Python 2.7.5 (default, Nov 6 2016, 00:28:07)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux2

OS:
Linux vm 4.4.19-1-pve #1 SMP Wed Sep 14 14:33:50 CEST 2016 x86_64 x86_64
x86_64 GNU/Linux

Thanks for any help.

I asked this question on github but were redirected here, by Tobias
Oberstein (thanks to him) and he pointed:

Your Node.js worker has exited with error, and due to the default

Crossbar.io node policy, the Crossbar.io node shuts down completely.

But I dont use nodejs I dont have it.

0 Likes

#5

Robert thanks for quick reply,

Yes I’m running crossbar via ssh and yes this OS is container. Command is:

nohup python -u /usr/bin/crossbar start &>logs/crossbar.out &

nohup should prevent me from SIGHUP (shouldn’t it?). How should I demonize crossbar properly?

Regards,
Roman.

···

четверг, 16 февраля 2017 г., 19:00:20 UTC+2 пользователь gms...@gmail.com написал:

Your Node.js worker has exited with error, and due to the default Crossbar.io node policy, the Crossbar.io node shuts down completely.
Dear All,

2017-02-16T09:42:55+0000 [Controller 4103] Node configuration loaded from ‘config.json’
2017-02-16T09:42:55+0000 [Controller 4103] __ __ __ __ __ __ __ __
2017-02-16T09:42:55+0000 [Controller 4103] / |)/ //`|) /\ |) |/
2017-02-16T09:42:55+0000 [Controller 4103] ,| /././|)/~| . |__/
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Crossbar.io Version: 16.10.1
2017-02-16T09:42:55+0000 [Controller 4103] Node Public Key: d689234365ec7faf617f4c88446e492b9f628ba53d70c96859193a3f4328a134
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Running from node directory ‘/srv/TestBed/.crossbar’
2017-02-16T09:42:55+0000 [Controller 4103] Controller process starting (CPython-EPollReactor) …
2017-02-16T09:42:55+0000 [Controller 4103] Using default node shutdown triggers [u’shutdown_on_worker_exit’]
2017-02-16T09:42:55+0000 [Controller 4103] Joined realm ‘crossbar’ on node management router
2017-02-16T09:42:55+0000 [Controller 4103] Configuring node from local configuration …
2017-02-16T09:42:55+0000 [Controller 4103] Starting 1 workers …
2017-02-16T09:42:55+0000 [Controller 4103] Starting Router with ID ‘worker-001’…
2017-02-16T09:42:56+0000 [Router 4112] Worker process starting (CPython-EPollReactor) …
2017-02-16T09:42:57+0000 [Controller 4103] Router with ID ‘worker-001’ and PID 4112 started
2017-02-16T09:42:57+0000 [Router 4112] Realm ‘TestBed’ started
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: realm ‘realm-001’ (named ‘TestBed’) started
2017-02-16T09:42:57+0000 [Router 4112] role role-001 on realm realm-001 started
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: role ‘role-001’ (named ‘anonymous’) started on realm ‘realm-001’
2017-02-16T09:42:57+0000 [Router 4112] Site starting on 9000
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: transport ‘transport-001’ started
2017-02-16T09:42:57+0000 [Controller 4103] Local node configuration applied.
2017-02-16T13:15:17+0000 [Controller 4103] Native worker connection closed uncleanly: A process has ended with a probable error condition: process ended by signal 1.
2017-02-16T13:15:17+0000 [Controller 4103] Node worker worker-001 ended with error ([Failure instance: Traceback (failure with no frames): <class ‘twisted.internet.error.ProcessTerminated’>: A process has ended with a probable error condition: process ended by signal 1.
])
2017-02-16T13:15:17+0000 [Controller 4103] Node worker ended, and trigger ‘shutdown_on_worker_exit’ active
2017-02-16T13:15:17+0000 [Controller 4103] Node shutting down …
2017-02-16T13:15:17+0000 [Controller 4103] Shutting down node…
2017-02-16T13:15:17+0000 [Controller 4103] sending TERM to subprocess 4112

python:
Python 2.7.5 (default, Nov 6 2016, 00:28:07)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux2

OS:
Linux vm 4.4.19-1-pve #1 SMP Wed Sep 14 14:33:50 CEST 2016 x86_64 x86_64 x86_64 GNU/Linux

Thanks for any help.

I asked this question on github but were redirected here, by Tobias Oberstein (thanks to him) and he pointed:

But I dont use nodejs I dont have it.

0 Likes

#6

when you ssh into a host that runs docker, and then interactively start/log into a docker container with crossbar running inside, this whole chain must somehow be “kept up” … I guess. whatever that means for your command line options =) Dunno.

Properly daemonize: use systemd on the host to start CB Docker image via rkt.

···

Am Freitag, 17. Februar 2017 19:03:16 UTC+1 schrieb gms...@gmail.com:

Robert thanks for quick reply,

Yes I’m running crossbar via ssh and yes this OS is container. Command is:

nohup python -u /usr/bin/crossbar start &>logs/crossbar.out &

nohup should prevent me from SIGHUP (shouldn’t it?). How should I demonize crossbar properly?

Regards,
Roman.

четверг, 16 февраля 2017 г., 19:00:20 UTC+2 пользователь gms...@gmail.com написал:

Your Node.js worker has exited with error, and due to the default Crossbar.io node policy, the Crossbar.io node shuts down completely.
Dear All,

2017-02-16T09:42:55+0000 [Controller 4103] Node configuration loaded from ‘config.json’
2017-02-16T09:42:55+0000 [Controller 4103] __ __ __ __ __ __ __ __
2017-02-16T09:42:55+0000 [Controller 4103] / |)/ //`|) /\ |) |/
2017-02-16T09:42:55+0000 [Controller 4103] ,| /././|)/~| . |__/
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Crossbar.io Version: 16.10.1
2017-02-16T09:42:55+0000 [Controller 4103] Node Public Key: d689234365ec7faf617f4c88446e492b9f628ba53d70c96859193a3f4328a134
2017-02-16T09:42:55+0000 [Controller 4103]
2017-02-16T09:42:55+0000 [Controller 4103] Running from node directory ‘/srv/TestBed/.crossbar’
2017-02-16T09:42:55+0000 [Controller 4103] Controller process starting (CPython-EPollReactor) …
2017-02-16T09:42:55+0000 [Controller 4103] Using default node shutdown triggers [u’shutdown_on_worker_exit’]
2017-02-16T09:42:55+0000 [Controller 4103] Joined realm ‘crossbar’ on node management router
2017-02-16T09:42:55+0000 [Controller 4103] Configuring node from local configuration …
2017-02-16T09:42:55+0000 [Controller 4103] Starting 1 workers …
2017-02-16T09:42:55+0000 [Controller 4103] Starting Router with ID ‘worker-001’…
2017-02-16T09:42:56+0000 [Router 4112] Worker process starting (CPython-EPollReactor) …
2017-02-16T09:42:57+0000 [Controller 4103] Router with ID ‘worker-001’ and PID 4112 started
2017-02-16T09:42:57+0000 [Router 4112] Realm ‘TestBed’ started
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: realm ‘realm-001’ (named ‘TestBed’) started
2017-02-16T09:42:57+0000 [Router 4112] role role-001 on realm realm-001 started
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: role ‘role-001’ (named ‘anonymous’) started on realm ‘realm-001’
2017-02-16T09:42:57+0000 [Router 4112] Site starting on 9000
2017-02-16T09:42:57+0000 [Controller 4103] Router ‘worker-001’: transport ‘transport-001’ started
2017-02-16T09:42:57+0000 [Controller 4103] Local node configuration applied.
2017-02-16T13:15:17+0000 [Controller 4103] Native worker connection closed uncleanly: A process has ended with a probable error condition: process ended by signal 1.
2017-02-16T13:15:17+0000 [Controller 4103] Node worker worker-001 ended with error ([Failure instance: Traceback (failure with no frames): <class ‘twisted.internet.error.ProcessTerminated’>: A process has ended with a probable error condition: process ended by signal 1.
])
2017-02-16T13:15:17+0000 [Controller 4103] Node worker ended, and trigger ‘shutdown_on_worker_exit’ active
2017-02-16T13:15:17+0000 [Controller 4103] Node shutting down …
2017-02-16T13:15:17+0000 [Controller 4103] Shutting down node…
2017-02-16T13:15:17+0000 [Controller 4103] sending TERM to subprocess 4112

python:
Python 2.7.5 (default, Nov 6 2016, 00:28:07)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux2

OS:
Linux vm 4.4.19-1-pve #1 SMP Wed Sep 14 14:33:50 CEST 2016 x86_64 x86_64 x86_64 GNU/Linux

Thanks for any help.

I asked this question on github but were redirected here, by Tobias Oberstein (thanks to him) and he pointed:

But I dont use nodejs I dont have it.

0 Likes