Thanks guys! I was able to start the last build (riak-2.0.0pre15)
On Mon, Mar 17, 2014 at 4:56 PM, Seth Thomas wrote:
> I'd try using an updated build and let us know if it's still an issue. My
> hunch is that it'll still be the same issue if in fact there is some Erlang
> VM local or remote ho
I’d try using an updated build and let us know if it’s still an issue. My hunch
is that it’ll still be the same issue if in fact there is some Erlang VM local
or remote holding onto that name/IP. If you want to ping me directly with the
configuration directory (etc) contents, logs, and OS versio
Thanks, Seth.
No, I don't think there is something in my system that is using the same
port. I rebooted and checked ips and all riak default ports were free. I
started the old riak just to test. I stopped id and cleaned beam.smp, epmd,
etc.
I didn't change anything in the configs. After installin
Is there something else on the network trying to operate with the same name/IP?
If you’d like I'm happy to look at the vm.args and app.config but I’m of the
mind that there is something else in the environment that causing this error.
That is to say I don’t agree with the assertion this is 2.0 s
Thanks, Michael.
I checked ports and made sure they were free. I even rebooted my server to
start from clean. Didn't help.
On Mon, Mar 17, 2014 at 3:07 PM, Michael Dillon
wrote:
> Best way to do a quick check to see if Riak started OK is to run
>
> netstat -lnp
>
> and see if something is liste
