"swift-init proxy start" starts proxy for Swift object storage but with some weird response, why?

asked 2016-10-12 07:44:36 -0500

RahulS gravatar image

updated 2016-10-12 07:45:25 -0500

I have installed swift on my local machine/s. The installation is smooth without any errors but sometimes the same process leads to weird response while starting the Swift(Object Storage).

The command I use is as follows swift-init proxy start

This command gives the following output. liberasurecode[24027]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory liberasurecode[24027]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory liberasurecode[24027]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory liberasurecode[24027]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory

Even after the above errors(exceptions) , my swift is working, I am able to create Account, Containers and can upload objects. Will this affect my Swift or something is really going wrong somewhere??

Thanx in Advance.

edit retag flag offensive close merge delete

Comments

I am getting the same warning when running the command swift-get-nodes on a master DevStack. Needless to say, I don't have erasure code enabled. While it doesn't look like a problem, it's annoying in a training environment.

Bernd Bausch gravatar imageBernd Bausch ( 2016-12-20 21:07:58 -0500 )edit