tolstoyevsky / cusdeb-single-node

Set of scripts intended for simplifying deployment of CusDeb for developing purposes
Apache License 2.0
1 stars 2 forks source link

Add Orion to single-node #23

Closed mdanil007 closed 5 years ago

denismosolov commented 5 years ago

I've build project from scratch and got the following:

2019-01-05 17:54:29,596 CRIT Supervisor running as root (no user in config file)
2019-01-05 17:54:29,603 INFO RPC interface 'supervisor' initialized
2019-01-05 17:54:29,604 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-01-05 17:54:29,604 INFO supervisord started with pid 8446
2019-01-05 17:54:30,606 INFO spawned: 'dashboard_server' with pid 8514
2019-01-05 17:54:30,607 INFO spawned: 'bm' with pid 8515
2019-01-05 17:54:30,608 INFO spawned: 'dashboard_client' with pid 8516
2019-01-05 17:54:30,609 INFO spawned: 'orion' with pid 8517
2019-01-05 17:54:30,610 INFO spawned: 'dominion' with pid 8520
2019-01-05 17:54:30,611 INFO spawned: 'worker_00' with pid 8522
2019-01-05 17:54:31,011 INFO exited: orion (exit status 0; not expected)
2019-01-05 17:54:31,855 INFO success: dashboard_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-05 17:54:31,855 INFO success: bm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-05 17:54:31,855 INFO success: dashboard_client entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-05 17:54:31,855 INFO success: dominion entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-05 17:54:32,039 INFO spawned: 'orion' with pid 8559
2019-01-05 17:54:32,291 INFO exited: orion (exit status 0; not expected)
2019-01-05 17:54:35,076 INFO spawned: 'orion' with pid 8599
2019-01-05 17:54:35,377 INFO exited: orion (exit status 0; not expected)
2019-01-05 17:54:38,381 INFO spawned: 'orion' with pid 8692
2019-01-05 17:54:38,618 INFO exited: orion (exit status 0; not expected)
2019-01-05 17:54:39,619 INFO gave up: orion entered FATAL state, too many start retries too quickly
2019-01-05 17:54:40,620 INFO success: worker_00 entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)