Hi Paul, I just wanted to let you know that I'm currently investigating this and will get back to you shortly.
I've opened the following issue for tracking it: https://github.com/basho/riak_control/issues/128 In addition, in retrospect I've realized that using the "incompatible" language is a bit misleading -- only a subset of functionality becomes unavailable when Control detects a possible incompatibility, and this is usually limited to display a node's memory utilization (leaving management commands unaffected.) I've opened the following issue for tracking updating the language to provide a less ambiguous, more concrete, display of what is actually happening within the cluster: https://github.com/basho/riak_control/issues/127 Thanks for being so patient and diligent with testing our latest releases! - Chris On Mon, Aug 5, 2013 at 2:51 PM, Paul Ingalls <p...@fanzo.me> wrote: > Hope you all don't get pissed for me spamming the list….;) > > I upgraded my cluster to 1.4.1 in hopes the levelDB changes may help. The > cluster is now up and running, however Riak Control is complaining: > > The following nodes are currently incompatible with Riak Control: > <all my nodes> > > I googled around and saw this had something to do with the RPC calls > failing, but I can't find any logs on the server that give me a hint where > to go next. > > When I rebuilt from source, my rel directory was nuked, so I needed to > regenerate my certs. Would this screw things up? > > Thanks, > > Paul > > > Paul Ingalls > Founder & CEO Fanzo > p...@fanzo.me > @paulingalls > http://www.linkedin.com/in/paulingalls > > > > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
