spurious messages in syslog

[Clay Gerrard]

I'm getting a lot of business like this:

Feb 16 19:33:09 saio liberasurecode[9720]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Feb 16 19:33:09 saio liberasurecode[9720]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Feb 16 19:33:09 saio liberasurecode[9720]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
Feb 16 19:33:09 saio liberasurecode[9720]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
Feb 16 19:33:09 saio liberasurecode[9721]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Feb 16 19:33:09 saio liberasurecode[9721]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
Feb 16 19:33:09 saio liberasurecode[9721]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
Feb 16 19:33:09 saio liberasurecode[9721]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory

in this instance I don't have Jerasure installed, or isa-l, the other stuff I don't even know what it is. But I did notice on another machine where I did have isa-l installed I didn't get that log line - so that's probably good. Can I turn off this debug logging somehow when I build?

[Tushar Gohad]

@clayg is this happening when you run swift EC unit tests?

So far the default has been to log errors to syslog or stderr if that fails .. the next 1.x release should have a way to configure logging at the liberasurecode/pyeclib level. I will get those commits merged sooner.

[Clay Gerrard]

are these "errors" tho if they're not installed? is there any difference in logging debug messages vs error messages? or is that what you're talking about coming in the next release?

... and thanks for the prompt response!

[Tushar Gohad]

@Clayg .. errors if one tries to open the backend and the library is not available .. I think what you are seeing is a result of VALID_EC_TYPES evaluation in pyeclib - it was changed in the last release so it is dynamically populated .. it is iterating through all possible backends and if a backend library isn't found, logs a message to that effect to syslog by default - there isn't yet a way to conditionally silence the "errors" at the liberasurecode level (that's exposed to the python layer), which is coming up shortly.