Ask Your Question
0

Swift proxy - problem with liberasurecode - centos/redhat7 [closed]

asked 2016-11-23 05:46:43 -0600

elemca gravatar image

The same problem had Alex Usov.

Durting the startup of proxy service I got following errors:
Nov 23 05:55:17 redhat7 liberasurecode[7111]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Nov 23 05:55:17 redhat7 liberasurecode[7111]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Nov 23 05:55:17 redhat7 liberasurecode[7111]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
Nov 23 05:55:17 redhat7 liberasurecode[7111]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory

He solved the issue by compiling new version of liberasurecode. I did compile too, but still have no those missing libraries in any directory. Also tried to install it from rpm package. The same result - no libraries.

Tried on Centos 7 and RedHat 7.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by elemca
close date 2016-11-28 05:28:59.746878

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-11-28 05:28:25 -0600

elemca gravatar image

updated 2016-11-28 05:52:16 -0600

Regarding these problems - it was completely not related to libraries displayed in logs, just configuration problems. Log files seem useless in many cases in Swift.

So don't take this liberasurecode errors too serious. They may, but probably are not the root cause of problem.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2016-11-23 05:46:43 -0600

Seen: 531 times

Last updated: Nov 28 '16