Thanks Pete.
I got my openstack-swift-account.service up now.
SELINUX was the root cause for preventing the service to go up.
[root@opstack-objstorage1 srv 2016.10.14 10:46:00]# ls -lZ
/etc/swift/swift.conf
-rw-r--r--. root swift system_u:object_r:etc_t:s0
/etc/swift/swift.conf
On Fri, Oct
On Thu, 13 Oct 2016 11:58:58 +0900
Yu Watanabe wrote:
> Oct 12 19:44:45 opstack-objstorage1 swift-account-server[27793]: Error:
> [swift-hash]: both swift_hash_path_suffix and swift_hash_path_prefix are
> m...ft.conf
Leaving libshss aside, Swift being unable to read
Thank you for the response.
I will check the latest liberasurecode (ver1.2.0).
https://github.com/openstack/liberasurecode
Best Regards,
Yu Watanabe
On Thu, Oct 13, 2016 at 1:47 PM, Kota TSUYUZAKI <
tsuyuzaki.k...@lab.ntt.co.jp> wrote:
> Correct. Thanks John for your quick response.
>
> Kota
Correct. Thanks John for your quick response.
Kota
(2016/10/13 12:14), John Dickinson wrote:
> Unfortunately, no (as far as i know). It's a proprietary library used by NTT.
>
> However, if you update to the latest version of liberasurecode, that warning
> message is suppressed.
>
> --John
>
Unfortunately, no (as far as i know). It's a proprietary library used by NTT.
However, if you update to the latest version of liberasurecode, that warning
message is suppressed.
--John
On 12 Oct 2016, at 19:58, Yu Watanabe wrote:
> Hello.
>
> I would like to ask question related to swift