Ask Your Question
1

Unable to start Swift Proxy (liberasurecode missing libshss.so)

asked 2016-06-08 17:28:55 -0500

Alex Usov gravatar image

updated 2016-09-06 02:10:49 -0500

fifieldt gravatar image

Greetings everyone.

Preparing for my Red Hat OpenStack Administrator exam, I've been following RDO install guide, so I finished configuring Swift Object Storage services and tried to start Swift Proxy on controller node, but it failed with errors in journalctl:

Jun 09 01:06:16 openstack-01.svp.test systemd[1]: Started OpenStack Object Storage (swift) - Proxy Server.
Jun 09 01:06:16 openstack-01.svp.test systemd[1]: Starting OpenStack Object Storage (swift) - Proxy Server...
Jun 09 01:06:16 openstack-01.svp.test liberasurecode[13198]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Jun 09 01:06:16 openstack-01.svp.test liberasurecode[13198]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Jun 09 01:06:16 openstack-01.svp.test liberasurecode[13198]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
Jun 09 01:06:16 openstack-01.svp.test liberasurecode[13198]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: Traceback (most recent call last):
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: File "/usr/bin/swift-proxy-server", line 23, in <module>
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: sys.exit(run_wsgi(conf_file, 'proxy-server', **options))
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 893, in run_wsgi
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: loadapp(conf_path, global_conf=global_conf)
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 384, in loadapp
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: ctx = loadcontext(loadwsgi.APP, conf_file, global_conf=global_conf)
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 368, in loadcontext
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: global_conf=global_conf)
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 296, in loadcontext
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: global_conf=global_conf)
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 320, in _loadconfig
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: return loader.get_context(object_type, name, global_conf)
Jun 09 01:06:16 openstack-01.svp.test swift-proxy-server[13198]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 64, in get_context
Jun 09 01:06:16 openstack-01.svp.test systemd[1]: openstack-swift-proxy.service: main process exited, code=exited, status=1/FAILURE
Jun 09 01:06:16 openstack-01.svp.test systemd[1]: Unit openstack-swift-proxy.service entered failed state.
Jun 09 01:06:16 openstack-01.svp.test systemd[1]: openstack-swift-proxy.service failed.

After discovering that no ... (more)

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2016-06-09 13:56:46 -0500

Peter gravatar image

updated 2016-06-09 16:23:07 -0500

Seeing the same thing trying to install keystone+swift (mitaka) in a VM (trusty)

Sure am interested in how to fix this.

Tx!

Peter

PS I got it working by

  1. curl -o libisal2_2.15.0-3~bpo14.04+1_amd64.deb http://mitaka-trusty.pkgs.mirantis.com/debian/pool/trusty-mitaka-backports/main/l/libisal/libisal2_2.15.0-3~bpo14.04+1_amd64.deb (http://mitaka-trusty.pkgs.mirantis.co...)
  2. sudo dpkg -i libisal2_2.15.0-3~bpo14.04+1_amd64.deb

  3. git clone https://bitbucket.org/kmgreen2/pyeclib.git (https://bitbucket.org/kmgreen2/pyecli...)

  4. sudo python setup.py install

  5. sudo apt-get uninstall python-pyeclib

After that the proxy starts

edit flag offensive delete link more
0

answered 2016-06-10 07:58:13 -0500

Alex Usov gravatar image

Thanks for the reply! Unfortunately, I use CentOS Linux 7 and there is no libisal2 rpm. So I downloaded ISAL from here https://01.org/intel%C2%AE-storage-acceleration-library-open-source-version/downloads (https://01.org/intel%C2%AE-storage-ac...) , compiled it, then installed pyeclib from bitbucket, and removed python-pyeclib package. After restarting openstack-swift-proxy I get a new error:

Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: Traceback (most recent call last):
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: File "/usr/bin/swift-proxy-server", line 19, in <module>
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: from swift.common.wsgi import run_wsgi
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 39, in <module>
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: from swift.common.storage_policy import BindPortsCache
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: File "/usr/lib/python2.7/site-packages/swift/common/storage_policy.py", line 25, in <module>
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: from pyeclib.ec_iface import ECDriver, ECDriverError, VALID_EC_TYPES
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: File "/usr/lib64/python2.7/site-packages/pyeclib/ec_iface.py", line 29, in <module>
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: from pyeclib_c import check_backend_available
Jun 10 15:47:42 openstack-01.svp.test swift-proxy-server[4482]: ImportError: /usr/lib64/python2.7/site-packages/pyeclib_c.so: undefined symbol: liberasurecode_backend_available

Googling hasn't yield any results. Am I doing something wrong?

edit flag offensive delete link more

Comments

1

Can't really help here. I did run into https://bugs.launchpad.net/pyeclib/+bug/1586220 (https://bugs.launchpad.net/pyeclib/+b...) which could be relevant for your case.

Grtz

P.

Peter gravatar imagePeter ( 2016-06-11 00:53:06 -0500 )edit

So you edited the source code to make it include changes from the commit, right?

Alex Usov gravatar imageAlex Usov ( 2016-06-11 03:39:29 -0500 )edit

Thanks, Peter. Finally got it working. Had to compile liberasurecode from https://github.com/openstack/liberasurecode.git (https://github.com/openstack/liberasu...), add line /usr/local/lib to /etc/ld.so.conf, run ldconfig, and restart openstack-swift-proxy. What I don't understand is why this problem isn't mentioned anywhere.

Alex Usov gravatar imageAlex Usov ( 2016-06-11 06:12:54 -0500 )edit
0

answered 2016-10-12 22:43:48 -0500

fifieldt gravatar image

Apparently some of these problems are fixed by updating to the latest version of liberasurecode

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

3 followers

Stats

Asked: 2016-06-08 17:28:55 -0500

Seen: 5,004 times

Last updated: Oct 12 '16