Ask Your Question
1

OpenStack swift mitaka: undefined liberasurecode_backend_available

asked 2016-06-28 15:41:11 -0500

henry gravatar image

updated 2016-11-10 00:51:48 -0500

notmyname gravatar image

I have a mitaka OpenStack Swift cluster consisting of a keystone VM, a Swift Proxy VM, and three storage nodes in three separate VMs. ( I refer them as keystone, sproxy, snode01, snode02, snode03). All VMs are running CentOS 7 (x86_64).

I followed the official installation guide for mitaka on CentOS 7.

However, whenever I do "systemctl openstack-swift-account start" ,and then check "systemctl status openstack-swift-account", I got

● openstack-swift-account.service - OpenStack Object Storage (swift) - Account Server Loaded: loaded (/usr/lib/systemd/system/openstack-swift-account.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2016-06-28 14:24:42 MDT; 6s ago Process: 27492 ExecStart=/usr/bin/swift-account-server /etc/swift/account-server.conf (code=exited, status=1/FAILURE) Main PID: 27492 (code=exited, status=1/FAILURE)

Jun 28 14:24:42 snode01c.library.ualberta.ca swift-account-server[27492]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 39, in <module>
Jun 28 14:24:42 snode01c.swift-account-server[27492]: from swift.common.storage_policy import BindPortsCache
Jun 28 14:24:42 snode01c
swift-account-server[27492]: File "/usr/lib/python2.7/site-packages/swift/common/storage_policy.py", line 25, in <module>
Jun 28 14:24:42 snode01c* swift-account-server[27492]: from pyeclib.ec_iface import ECDriver, ECDriverError, VALID_EC_TYPES Jun 28 14:24:42 snode01c* swift-account-server[27492]: File "/usr/lib64/python2.7/site-packages/pyeclib/ec_iface.py", line 29, in <module>
Jun 28 14:24:42 snode01c* swift-account-server[27492]: from pyeclib_c import check_backend_available
Jun 28 14:24:42 snode01c.* swift-account-server[27492]: ImportError: /usr/lib64/python2.7/site-packages/pyeclib_c.so: undefined symbol: liberasurecode_backend_available
Jun 28 14:24:42 * systemd[1]: openstack-swift-account.service: main process exited, code=exited, status=1/FAILURE
Jun 28 14:24:42 snode01c systemd[1]: Unit openstack-swift-account.service entered failed state.
Jun 28 14:24:42 snode01c.* systemd[1]: openstack-swift-account.service failed.

I followed someone's comment to compile liberasurecode from github and then install PyeClib from github as well, but still couldn't get it work

I know people are having the same problem since Kilo, up to Liberty and now Mitaka. Just wondering what is the fix for this, and why it carries from older version to now but still have not been resolved.

Thanks for you attention.

Hello !

I'm trying to install SAIO on a Ubuntu 16.04.1 LTS.

I followed the procedure here : http://docs.openstack.org/developer/s...

When I'm launching the command : $ $HOME/swift/.unittests

I'm getting the following errors :

liberasurecode[12210]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory liberasurecode[12210]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory liberasurecode[12210]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory liberasurecode[12210]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory

Should I worry about those errors ? Any idea how to solve this ?

Thanks for your help.

The full result of the command unittests is ... (more)

edit retag flag offensive close merge delete

Comments

I too installed Mitaka on CentOS 7 and can confirm a working swift installation without additional software. I have errors in my /var/log/messages regarding liberasurecode (libJerasure.so2, libisal.so.2, libshss.so.1...No such file or directory) however swift functions correctly. All services start.

barry.davis gravatar imagebarry.davis ( 2016-07-14 13:55:49 -0500 )edit

Are you able to run the swift services fine?

Beny gravatar imageBeny ( 2016-11-08 00:49:31 -0500 )edit

2 answers

Sort by » oldest newest most voted
1

answered 2016-11-10 00:34:46 -0500

notmyname gravatar image

The liberasurecode_backend_open error is not something to worry about. All it's saying is that there are some other available EC backends that weren't found. More recent versions of liberasurecode suppress the error.

edit flag offensive delete link more
0

answered 2016-11-08 01:45:07 -0500

No, I have the error :

$ startmain WARNING: Unable to modify max process limit. Running as non-root? Starting proxy-server...(/etc/swift/proxy-server.conf) Starting container-server...(/etc/swift/container-server/1.conf) Starting container-server...(/etc/swift/container-server/2.conf) Starting container-server...(/etc/swift/container-server/3.conf) Starting container-server...(/etc/swift/container-server/4.conf) Starting account-server...(/etc/swift/account-server/1.conf) Starting account-server...(/etc/swift/account-server/2.conf) Starting account-server...(/etc/swift/account-server/3.conf) Starting account-server...(/etc/swift/account-server/4.conf) Starting object-server...(/etc/swift/object-server/1.conf) Starting object-server...(/etc/swift/object-server/2.conf) Starting object-server...(/etc/swift/object-server/3.conf) Starting object-server...(/etc/swift/object-server/4.conf) Traceback (most recent call last): File "/usr/local/bin/swift-proxy-server", line 6, in <module> exec(compile(open(__file__).read(), __file__, 'exec')) File "/home/swift/swift/bin/swift-proxy-server", line 19, in <module> from swift.common.wsgi import run_wsgi File "/home/swift/swift/swift/common/wsgi.py", line 41, in <module> from swift.common.storage_policy import BindPortsCache File "/home/swift/swift/swift/common/storage_policy.py", line 25, in <module> from pyeclib.ec_iface import ECDriver, ECDriverError, VALID_EC_TYPES File "build/bdist.linux-x86_64/egg/pyeclib/ec_iface.py", line 29, in <module> File "build/bdist.linux-x86_64/egg/pyeclib_c.py", line 7, in <module> File "build/bdist.linux-x86_64/egg/pyeclib_c.py", line 4, in __bootstrap__ File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1172, in resource_filename self, resource_name File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1716, in get_resource_filename self._extract_resource(manager, self._eager_to_zip(name)) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1746, in _extract_resource self.egg_name, self._parts(zip_path) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1239, in get_cache_path self.extraction_error() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1219, in extraction_error raise err pkg_resources.ExtractionError: Can't extract file(s) to egg cache

The following error occurred while trying to extract file(s) to the Python egg cache:

[Errno 17] File exists: '/tmp/pyeclib-1.3.1-py2.7-linux-x86_64.egg-tmp'

The Python egg cache directory is currently set to:

/tmp

Perhaps your account does not have write access to this directory? You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-06-28 15:41:11 -0500

Seen: 1,101 times

Last updated: Nov 10 '16