Ask Your Question
0

Problems starting Openstack Swift Mitaka on RHEL7 and CENTOS7 [closed]

asked 2016-11-24 02:49:30 -0500

elemca gravatar image

Hi, during the startup i get:

systemctl status -l openstack-swift-proxy.service

 openstack-swift-proxy.service - OpenStack Object Storage (swift) - Proxy Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-swift-proxy.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2016-11-24 09:40:38 CET; 2s ago
  Process: 18394 ExecStart=/usr/bin/swift-proxy-server /etc/swift/proxy-server.conf (code=exited, status=1/FAILURE)
 Main PID: 18394 (code=exited, status=1/FAILURE)

Nov 24 09:40:38 server swift-proxy-server[18394]: File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 328, in _loadegg
Nov 24 09:40:38 server swift-proxy-server[18394]: return loader.get_context(object_type, name, global_conf)
Nov 24 09:40:38 server swift-proxy-server[18394]: File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 620, in get_context
Nov 24 09:40:38 server swift-proxy-server[18394]: object_type, name=name)
Nov 24 09:40:38 server swift-proxy-server[18394]: File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 659, in find_egg_entry_point
Nov 24 09:40:38 server swift-proxy-server[18394]: for prot in protocol_options] or '(no entry points)'))))
Nov 24 09:40:38 server swift-proxy-server[18394]: LookupError: Entry point 'main' not found in egg 'swift' (dir: /usr/lib/python2.7/site-packages; protocols: paste.filter_factory, paste.filter_app_factory; entry_points: )
Nov 24 09:40:38 server systemd[1]: openstack-swift-proxy.service: main process exited, code=exited, status=1/FAILURE
Nov 24 09:40:38 server systemd[1]: Unit openstack-swift-proxy.service entered failed state.
Nov 24 09:40:38 server systemd[1]: openstack-swift-proxy.service failed.

Before it, I've had many errors in /etc/swift/proxy-server.conf file got by: curl -o /etc/swift/swift.conf https://git.openstack.org/cgit/openstack/swift/plain/etc/swift.conf-sample?h=stable/mitaka (https://git.openstack.org/cgit/openst...)

Every line edited with vi on the sam machine had "\n" sign at the end.

In /var/log/messages I also have:

Nov 24 09:40:37 server liberasurecode[18394]: liberasurecode_instance_create: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Nov 24 09:40:37 server liberasurecode[18394]: liberasurecode_instance_create: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Nov 24 09:40:37 server liberasurecode[18394]: liberasurecode_instance_create: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
Nov 24 09:40:37 server liberasurecode[18394]: liberasurecode_instance_create: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory

I compiled liberasurecode 1.2 from source as well as installed it from rpm - with the same result - not getting these missing libraries.

At this moment I'm completely puzzled which is the root problem and how to solve it. Can anyone help?

Thanks in advance

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:27:43.742188

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-11-28 05:27:22 -0500

elemca gravatar image

updated 2016-11-28 05:51:07 -0500

Problem solved.

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

1 follower

Stats

Asked: 2016-11-24 02:49:30 -0500

Seen: 384 times

Last updated: Nov 28 '16