[erlang-questions] running rebar release in background

[Przemysław Wycisk]

thanks a lot !!

I compiled jiffy on the same machine and it works ;)

On Sun, Jan 4, 2015 at 7:01 PM, Alexander Petrovsky <askjuise@REDACTED>
wrote:

> Hi!
>
> Looks like you have a problem with jiffy, take a look at glibc version on
> build server and on worker were you run your app.
>
> воскресенье, 4 января 2015 г. пользователь Przemysław Wycisk написал:
>
> Hi, i have an issue with running erlang application in background on
>> Centos 6.6 (with ./bin/myapp start). The wild fact is that it starts and
>> works fine when i try to run it with "./bin/myapp foreground".
>> I tried also ./bin/myapp console and output was like this:
>>
>>
>> {error_logger,{{2015,1,4},{16,2,59}},crash_report,[[{initial_call,{supervisor,kernel,['Argument__1']}},{pid,<0.1208.0>},{registered_name,[]},{error_info,{exit,{on_load_function_failed,jiffy},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,330}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[kernel_sup,<0.1184.0>]},{messages,[]},{links,[<0.1185.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,27},{reductions,124}],[]]}
>>
>>
>> {error_logger,{{2015,1,4},{16,2,59}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{on_load_function_failed,jiffy}},{offender,[{pid,undefined},{name,kernel_safe_sup},{mfargs,{supervisor,start_link,[{local,kernel_safe_sup},kernel,safe]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
>>
>>
>> {error_logger,{{2015,1,4},{16,3,0}},crash_report,[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.1183.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,jiffy}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,133}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[<0.1182.0>]},{messages,[{'EXIT',<0.1184.0>,normal}]},{links,[<0.1182.0>,<0.1181.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,27},{reductions,117}],[]]}
>>
>>
>> {error_logger,{{2015,1,4},{16,3,0}},std_info,[{application,kernel},{exited,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,jiffy}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
>>
>> {"Kernel pid
>> terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,jiffy}}},{kernel,start,[normal,[]]}}}"}
>>
>>
>> Crash dump was written to: erl_crash.dump
>>
>> Kernel pid terminated (application_controller)
>> ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,jiffy}}},{kernel,start,[normal,[]]}}})
>>
>>
>> On mac the application is working fine with the same configuration i have
>> no clue why is this happening, and i haven't found any question like that
>> or solution in the internet, can anyone help?
>>
>> I'm also curious that is there any way to start an rebar release in
>> foreground and then detach it from user/console, that solution could be a
>> good workaround in this problem.
>>
>
>
> --
> Петровский Александр / Alexander Petrovsky,
>
> Skype: askjuise
> Phone: +7 914 8 820 815
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150105/8039c81f/attachment.htm>