This question has been flagged
4764 Views

Hello

Today i decided to manage openerp with supervisord . Everything works alright if i run openerp as standalone mode . But if i use openerp in multiprocess mode , i've found that supervisord cannot start openerp .

below is my openerp-multiproccess in supervisord.conf

[program:openerp_multiprocess] command = "/root/7.0-buildout/bin/start_openerp" --logfile "/root/7.0-buildout/var/log/openerp-stdout.log" --workers=4 process_name = openerp_multiprocess directory = /root/7.0-buildout priority = 10 redirect_stderr = true

And this is the error log

2013-12-26 13:21:31,356 INFO spawned: 'openerp_multiprocess' with pid 5462 2013-12-26 13:21:31,357 INFO spawned: 'openerp_connector_worker' with pid 5463 2013-12-26 13:21:31,924 INFO exited: openerp_connector_worker (exit status 1; not expected) 2013-12-26 13:21:31,925 INFO exited: openerp_multiprocess (exit status 0; not expected) 2013-12-26 13:21:34,931 INFO spawned: 'openerp_multiprocess' with pid 5465 2013-12-26 13:21:34,933 INFO spawned: 'openerp_connector_worker' with pid 5466 2013-12-26 13:21:35,451 INFO exited: openerp_multiprocess (exit status 0; not expected) 2013-12-26 13:21:35,451 INFO exited: openerp_connector_worker (exit status 1; not expected) 2013-12-26 13:21:36,453 INFO gave up: openerp_multiprocess entered FATAL state, too many start retries too quickly 2013-12-26 13:21:36,453 INFO gave up: openerp_connector_worker entered FATAL state, too many start retries too quickly

Seems that instead of start Openerp proccess , then let it fork workers, supervisord try to spawn multiple openerp proccess, which is not the correct behaviour .

Is there anyone have experience with this problem ? Thanks for any advance

Alex

Avatar
Discard