Open erikdubbelboer opened 9 years ago
I confirm the same behaviour on my CentOS 6.6 with the following software packages:
$ rpm -q erlang
erlang-17.5.3-1.el6.x86_64
$ erl
Erlang/OTP 17 [erts-6.4.1] [source-381fb6c] [64-bit] [smp:24:24] [async-threads:10] [hipe] [kernel-poll:false]
$ cd disco && git describe
0.5-478-g451e96f
I would only like to add that after issuing disco start
for the first time, no error log is created and, a described above, only one line of error description is printed to stdout:
$ disco start
zero length field name in format
At this point, a zero-length file /usr/var/disco/disco_8989.config
is created.
Further steps and results are the same as described above by @ErikDubbelboer.
Is there any chance to get a fix for this bug?
Same issue in Centos 6.7 I cannot get Disco to start and there doesn't seem to much support or documentation for this project in Centos unfortunately.
Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:12:12] [rq:12] [async-threads:0] [kernel-poll:true]
Eshell V5.8.5 (abort with ^G) (disco_8989_master@testing)1> 17:19:26.566 [info] Application lager started on node disco_8989_master@testing 17:19:26.603 [info] Application inets started on node disco_8989_master@testing 17:19:26.626 [info] DISCO BOOTS 17:19:26.628 [info] Disco proxy disabled 17:19:26.631 [info] DDFS master starts 17:19:26.634 [info] Event server starts 17:19:26.636 [info] Disco config starts 17:19:26.638 [info] DISCO SERVER STARTS 17:19:26.640 [info] Fair scheduler starts 17:19:26.640 [info] Scheduler uses fair policy 17:19:26.641 [info] Fair scheduler: Fair policy 17:19:26.644 [warning] Disco config dies: {{badmatch,any},[{mochijson2,tokenize,2},{mochijson2,decode1,2},{mochijson2,json_decode,2},{disco_config,get_full_config,0},{disco_config,do_get_config_table,0},{disco_config,handle_call,3},{gen_server,handle_msg,5},{proc_lib,init_p_do_apply,3}]} 17:19:26.644 [error] gen_server disco_config terminated with reason: no match of right hand value any in mochijson2:tokenize/2 17:19:26.644 [warning] Parsing config failed: exit:{{{badmatch,any},[{mochijson2,tokenize,2},{mochijson2,decode1,2},{mochijson2,json_decode,2},{disco_config,get_full_config,0},{disco_config,do_get_config_table,0},{disco_config,handle_call,3},{gen_server,handle_msg,5},{proc_lib,init_p_do_apply,3}]},{gen_server,call,[disco_config,get_config_table]}} 17:19:26.644 [warning] Disco server dies: shutdown 17:19:26.644 [error] CRASH REPORT Process disco_config with 0 neighbours exited with reason: no match of right hand value any in mochijson2:tokenize/2 in gen_server:terminate/6 17:19:26.649 [error] Supervisor {<0.85.0>,disco_main} had child disco_server started with disco_server:start_link() at undefined exit with reason ok in context start_error 17:19:26.650 [error] Supervisor {<0.85.0>,disco_main} had child disco_config started with disco_config:start_link() at <0.93.0> exit with reason no match of right hand value any in mochijson2:tokenize/2 in context shutdown_error 17:19:26.650 [info] Application disco exited with reason: {shutdown,{disco_main,start,[normal,[]]}}
After doing the normal install process disco fails to start on CentOS.
The problem is fixed by manually filling
/usr/var/disco/disco_8989.config
which seems to be empty after the first start.Versions:
Disco is installed using
sudo make install
. The python libs are also installed system wide./usr/var/disco/
and/usr/lib/disco
are both chowned to the user which starts disco.What happened:
/etc/disco/settings.py
:/usr/var/disco/log/console.log
:/usr/var/disco/log/error.log
:/usr/var/disco/log/crash.log
: