0.14 crash on OS X

francisco treacy francisco.treacy at gmail.com
Thu Feb 17 12:36:34 EST 2011


I had checked sasl-error.log, nothing interesting in there
(js_vm_count depreaction messages)

I kill -9'd the process and pinged:

 => bin/riaksearch ping

=INFO REPORT==== 17-Feb-2011::14:30:38 ===
Protocol: "inet_tcp": register error: {{badmatch,{error,econnrefused}},
                                       [{inet_tcp_dist,listen,1},
                                        {net_kernel,start_protos,4},
                                        {net_kernel,start_protos,3},
                                        {net_kernel,init_node,2},
                                        {net_kernel,init,1},
                                        {gen_server,init_it,6},
                                        {proc_lib,init_p_do_apply,3}]}
escript: exception error: no match of right hand side value
                 {error,
                     {shutdown,
                         {child,undefined,net_sup_dynamic,
                             {erl_distribution,start_link,
                                 [['riaksearch_maint_96460 at 127.0.0.1',
                                   longnames]]},
                             permanent,1000,supervisor,
                             [erl_distribution]}}}

Then I started up via console, which I assume started up correctly
(Spidermonkey VMs and loading indices).

Now things are fine again (including ping) - but how do we find the
cause of the crash? I'm a bit concerned, I def don't want this
happening in production.

Thanks,

Francisco


2011/2/17 David Smith <dizzyd at basho.com>:
> sasl-error.log is usually the first place of interest, but be warned
> it gets overwritten between restarts. I would suggest trying to start
> up with "console" method (after making sure other process is gone) and
> see what happens.
>
> D.
>
> On Thu, Feb 17, 2011 at 10:09 AM, francisco treacy
> <francisco.treacy at gmail.com> wrote:
>> Riak Search 0.14.0 just inexplicably went down, and pinging takes very
>> long. Trying to `start` it also takes as long.
>>
>>  =>  time bin/riaksearch ping
>> Node 'riaksearch at 127.0.0.1' not responding to pings.
>>
>> real    0m14.205s
>> user    0m0.143s
>> sys     0m0.048s
>>
>>  =>  ps -ef | grep beam
>>  501 95991 95990   0   0:02.69 ttys011    0:10.27
>> /opt/riak/erts-5.7.5/bin/beam.smp -K true -A 64 -- -root /opt/riak
>> -progname riaksearch -- -home /Users/ftreacy -- -boot
>> /opt/riak/releases/0.14.0/riaksearch -embedded -config
>> /opt/riak/etc/app.config -name riaksearch at 127.0.0.1 -setcookie riak --
>> console
>>  501 96207 95639   0   0:00.00 ttys012    0:00.00 grep beam
>>
>> Other than erl_crash.dump (https://gist.github.com/832139), do you
>> need other info to understand what could've happened?
>>
>> Thanks,
>> Francisco
>>
>> _______________________________________________
>> riak-users mailing list
>> riak-users at lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>
>
>
> --
> Dave Smith
> Engineering Manager
> Basho Technologies, Inc.
> dizzyd at basho.com
>




More information about the riak-users mailing list