On 4 May 2017 at 09:56, Arulappan, Jerald (Jerald) <ajer...@avaya.com>
wrote:
> Hi Magnus Kessler,
>
>
>
> The configuration looks good.
>
>
>
> [root@server205 bin]# ./riak config effective | grep "_dir"
>
> anti_entropy.data_dir = $(platform_data_dir)/anti_entropy
>
> bitcask.data_root = $(platform_data_dir)/bitcask
>
> leveldb.data_root = $(platform_data_dir)/leveldb
>
> log.console.file = $(platform_log_dir)/console.log
>
> log.crash.file = $(platform_log_dir)/crash.log
>
> log.error.file = $(platform_log_dir)/error.log
>
> platform_bin_dir = ./bin
>
> platform_data_dir = ./data
>
> platform_etc_dir = ./etc
>
> platform_lib_dir = ./lib
>
> platform_log_dir = ./log
>
> ring.state_dir = $(platform_data_dir)/ring
>
> search.anti_entropy.data_dir = $(platform_data_dir)/yz_anti_entropy
>
> search.root_dir = $(platform_data_dir)/yz
>
> search.temp_dir = $(platform_data_dir)/yz_temp
>
>
>
> Regards,
>
> Jerald
>
>
>
Hi Jerald,
The that fill up the logs at a very high rate are due to the use of
relative file paths for platform_{bin,data,etc,lib,log}_dir. Those entries
should generally contain absolute file paths, such as /var/lib/riak, as
init systems may start the application from an arbitrary working directory.
Please check if the errors go away after adjusting platform_data_dir.
Kind Regards,
Magnus
--
Magnus Kessler
Client Services Engineer
Basho Technologies Limited
Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
