Done. Here it is: https://github.com/basho/riak_cs/issues/1333
2017-03-08 16:21 GMT+01:00 Jon Brisbin :
> Might be good to make sure this info is encapsulated into a GitHub issue
>> so we don't loose track of it.
>>
>>
>> In the end, the ONE thing to fix is the cumbersome error message. A
>> prop
>
> Might be good to make sure this info is encapsulated into a GitHub issue
> so we don't loose track of it.
>
>
> In the end, the ONE thing to fix is the cumbersome error message. A propre
> error message would have saved me days of "work"...
> Should I create a new issue for that ?
>
Please do.
2017-03-08 15:53 GMT+01:00 Jon Brisbin :
> FWIW- All work done so far on Riak-in-Docker is for purposes of testing
> and ad-hoc cluster creation and NOT for use in "production" environments
> (for any definition of the word "production"). Things like exposing the
> conf files on a volume which are
FWIW- All work done so far on Riak-in-Docker is for purposes of testing and
ad-hoc cluster creation and NOT for use in "production" environments (for
any definition of the word "production"). Things like exposing the conf
files on a volume which are more production-oriented haven't been in scope
of
Hello,
I finally found the problem : the riak and riak-cs config files where
stored in my app container, not in my persistent data container (where the
riak data is).
Whenever I upgraded the app container to a newly generated one, the conf
files and especially the admin user credentials did not ma
On 6 March 2017 at 03:49, Toby Corkindale wrote:
>
> I tried quite hard to get Riak to work reliably in a Docker container, in
a long-term-use kind of way.
> Riak would never shutdown cleanly, though, and so at startup there would
always be lots of lock files left around that had to be deleted fir
I tried quite hard to get Riak to work reliably in a Docker container, in a
long-term-use kind of way.
Riak would never shutdown cleanly, though, and so at startup there would
always be lots of lock files left around that had to be deleted first.
Riak is not well-behaved after a rough shutdown --
I haven't tried CS in a container yet. Could you provide the Dockerfiles
and compose files or the commands you use to start the services?
jb
On Wed, Feb 15, 2017 at 4:49 PM Jean-Marc Le Roux
wrote:
> Hi,
>
> inspecting the logs further, I get this in /etc/riak/console.log even
> before running
Hi,
inspecting the logs further, I get this in /etc/riak/console.log even
before running riak-admin repair-2i :
2017-02-15 23:41:12.441 [warning] <0.714.0> Hintfile
'/var/lib/riak/bitcask/205523667749658222872393179600727299639115513856/2.bitcask.hint'
invalid
2017-02-15 23:41:12.441 [warning] <0
Forgot to mention ACLs are alright AFAIK :
root@b4394bf1de78:/var/lib/riak# ls -la
total 52
drwxr-xr-x. 10 riak riak 179 Feb 9 23:43 .
drwxr-xr-x. 1 root root 95 Feb 15 20:48 ..
-r. 1 riak riak 20 Feb 9 01:00 .erlang.cookie
drwxrwxr-x. 67 riak riak 8192 Feb 15 21:31 anti_entropy
d
Hi,
I'll try to send the log archive ASAP.
Here is what I get in /var/log/riak/error.log after running riak-admin
repair-2i :
2017-02-15 22:09:06.535 [error]
<0.3287.0>@riak_kv_2i_aae:repair_partition:297 Failed to acquire hashtree
lock on partition 1255977969581244695331291653117200168170291
Hi Jean-Marc -
Can you provide a complete archive of the log directory? I wonder if
another file might have more information.
--
Luke Bakken
Engineer
lbak...@basho.com
On Thu, Feb 9, 2017 at 1:58 AM, Jean-Marc Le Roux
wrote:
>
> Hello,
>
> here is the original github issue :
>
> https://github.
Hello,
here is the original github issue :
https://github.com/basho/riak_cs/issues/1329
I'm using riak-cs 2.1.1-1.el6 with stanchion 1.5.0-1.el6 on CentOS 6.8 in a
Docker container.
To make the data persistent, the following directories are mounted from
outside the container :
- /var/log
13 matches
Mail list logo
