Not much luck with Riak 0.7.1 on CentOS 5.4

Andy Gross andy at
Wed Feb 3 09:59:27 EST 2010

Hi Mårten,

The "Bad Path" messages are actually ignorable - .ez files are a relatively
new feature to Erlang - we're submitting a patch to the Erlang team to
remove them, but for now, pay them no mind.

As for the crash - it appears that Erlang can't write to whatever directory
you have set for "riak_dets_backend_root" in your etc/app.config file.

Try the steps below - these should get you up and running.

% rm -Rf rel/riak
% make clean all
% cd rel/riak
% bin/riak console (or bin/riak start to launch in the background - you can
run bin/riak attach later to get an Erlang console)

Let us know if that works for you.



On Wed, Feb 3, 2010 at 9:41 AM, Mårten Gustafson <marten.gustafson at
> wrote:

> Hello!
> I just downloaded Riak 0.7.1 in order to try out a three-node cluster.
> Everything built successfully. But running proved to be all other than
> successful.
> 1) Problem with .ez archives
> When I ran "riak start" I got a whole slew of:
> ** Bad path can't read
> /home/riak/riak-0.7.1/lib/kernel-2.13.4.ez/kernel-2.13.4/ebin
> After som googling, first finding out what .ez is etc. I took a chance
> and manually unzipped all .ez archives, keeping any unzipped
> directories already in place - thus merging their content with the
> contents from the .ez-archive. This got rid of the "Bad path" problem.
> 2)
> After the above, the current state is that riak crashes directly upon
> start, see attached log file.
> Environment is CentOS 5.4 on x86_64.
> I've killed all left-behind processes and cleaned the dets and ring
> directories between each run.
> /Mårten.
> _______________________________________________
> riak-users mailing list
> riak-users at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the riak-users mailing list