Skip to content

Conversation

@martinsumner
Copy link
Contributor

No description provided.

@martinsumner
Copy link
Contributor Author

Starting riak previously:

(riak@127.0.0.1)1> setup:find_env_vars(exometer_defaults).
[{riak_core,[{['_'],
              histogram,
              [{options,[{histogram_module,exometer_slot_slide},
                         {keep_high,500}]}]}]}]
(riak@127.0.0.1)2> setup:find_env_vars(exometer_predefined).
[]

Starting riak with this branch:

(riak@127.0.0.1)1> exometer_util:find_env_vars(exometer_defaults).
[{riak_core,[{['_'],
              histogram,
              [{options,[{histogram_module,exometer_slot_slide},
                         {keep_high,500}]}]}]}]
(riak@127.0.0.1)2> exometer_util:find_env_vars(exometer_predefined).
[]

@tburghart
Copy link
Member

+1 👍

@Bob-The-Marauder
Copy link

Sorry if this is irrelevant but is this related to a brand new node being started for the first time with a distributed_cookie other than "riak"?
If so, a work around we've been using is to run sudo riak chkconfig first to make a set of pre-generated app.config and vm.args which appear to be read by the application with the issue when you actually start Riak and thus prevent the error from happening.

@martinsumner martinsumner changed the base branch from openriak-3.2 to openriak-3.4 February 19, 2025 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants