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.tre...@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@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@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@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > -- Dave Smith Engineering Manager Basho Technologies, Inc. diz...@basho.com _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
