On Friday 8. December 2017 14.40.14 Paul Boddie wrote:
> On Friday 8. December 2017 11.28.38 Ludovic Courtès wrote:
> >
> > Could you search in the strace output for the ‘clone’ call that failed
> > with EINVAL? It’s probably the one from nix/libstore/build.cc.
[...]
> I'm tracing the daemon here. Should I also be tracing something else?
Sorry, I found that I should be running strace using the -o, -f and -ff
options:
strace -o /tmp/guix -f -ff /usr/local/bin/guix-daemon \
--build-users-group=guixbuild
This gave me the following in the parent process log (/tmp/guix.793):
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x404c5f28) = 797
close(4) = 0
accept(3, 0xbfff7224, [110]) = ? ERESTARTSYS (To be restarted if
SA_RESTART is set)
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=797, si_uid=0,
si_status=0, si_utime=51, si_stime=524} ---
waitpid(-1, NULL, WNOHANG) = 797
This resembling what I showed before. Meanwhile in the child process log
(/tmp/guix.797) the clone call with EINVAL is this one:
clone(child_stack=0xbffedfa4, flags=CLONE_NEWNS|CLONE_NEWUTS|CLONE_NEWIPC|
CLONE_NEWPID|CLONE_NEWNET|SIGCHLD) = -1 EINVAL (Invalid argument)
Again, this is using the 4.9.67 kernel.
Paul
