New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couldn't re-execute SBCL with proper personality flags #511

Closed
Chekote opened this Issue Feb 5, 2017 · 10 comments

Comments

Projects
None yet
5 participants
@Chekote
Copy link

Chekote commented Feb 5, 2017

I'm trying to run pgloader, but I always get the following error as soon as I execute the program. Even if I do something as simple as pgloader --help:

WARNING:
Couldn't re-execute SBCL with proper personality flags (/proc isn't mounted? setuid?)
Trying to continue anyway.

debugger invoked on a SIMPLE-ERROR in thread
#<THREAD "main thread" RUNNING {1008CC43B3}>:
  Error opening shared object "libssl.so.1.0.0":
  libssl.so.1.0.0: cannot open shared object file: No such file or directory.

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE       ] Skip this shared object and continue.
  1: [RETRY          ] Retry loading this shared object.
  2: [CHANGE-PATHNAME] Specify a different pathname to load the shared object from.

(SB-SYS:DLOPEN-OR-LOSE #S(SB-ALIEN::SHARED-OBJECT :PATHNAME #P"libssl.so.1.0.0" :NAMESTRING "libssl.so.1.0.0" :HANDLE NIL :DONT-SAVE NIL))
@dimitri

This comment has been minimized.

Copy link
Owner

dimitri commented Feb 10, 2017

Looks like an SBCL problem, I don't think I can help you with that. Please see http://www.sbcl.org and ask them...

@dimitri dimitri closed this Feb 10, 2017

@yamila-moreno

This comment has been minimized.

Copy link

yamila-moreno commented Jul 27, 2017

Hello! I'm facing the same problem, @Chekote, did you find any solution?

@fabswt

This comment has been minimized.

Copy link

fabswt commented Jul 27, 2017

Same here.

@fabswt

This comment has been minimized.

Copy link

fabswt commented Jul 28, 2017

I posted a bug report over at SBCL, but I now suspect this to be a Docker issue because:

a) I tried to compile a bunch of SBCL Dockerfiles found online and they all end up with the same Couldn't re-execute SBCL with proper personality flags (/proc isn't mounted? setuid?)

b) I managed to install and execute pgloader and sbcl without warning on a non-Docker Ubuntu install (on an Amazon EC2 instance), using the same commands I was using inside the Dockerfile.

I'd be happy to hear which environment @Chekote and @yamila-moreno were using.

@yamila-moreno

This comment has been minimized.

Copy link

yamila-moreno commented Jul 28, 2017

Hi @fabswt thanks for your answer and your research; indeed I was using a Docker environment; my docker-compose has 3 services:

  • postgres
  • mysql
  • pgloader
    and a network to connect them all. I could access both the databases from the pgloader container (so it wasn't a networking issue).

I'll try with a virtualbox machine. Thanks for sharing!!

@yamila-moreno

This comment has been minimized.

Copy link

yamila-moreno commented Jul 31, 2017

Hi again; I've tried to use pgloader inside a virtualbox (with postgres, mysql and pgloader) and after some tuning (with ONLY_FULL_GROUP_BY) it finally worked!!

Thanks to @fabswt cause your hint lead me to the next step 👍

@mmariani

This comment has been minimized.

Copy link

mmariani commented Aug 4, 2017

@yamila-moreno afaik you can do it in docker with docker run --security-opt seccomp=unconfined

or by providing an explicit seccomp profile. See: https://github.com/daewok/slime-docker/blob/master/README.md#sbcl-aslr

@yamila-moreno

This comment has been minimized.

Copy link

yamila-moreno commented Aug 7, 2017

@mmariani thanks for your tip! Very appreciated.

@dimitri

This comment has been minimized.

Copy link
Owner

dimitri commented Aug 7, 2017

Please consider adding those tips to the wiki here!

@mmariani

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment