unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: swedebugia@riseup.net
To: Mark H Weaver <mhw@netris.org>
Cc: 34006-done@debbugs.gnu.org
Subject: bug#34006: Guix gc killed live roots - broke git
Date: Sat, 12 Jan 2019 11:02:16 -0800	[thread overview]
Message-ID: <65080922ebfc8a46006fd7fab1ac951c@riseup.net> (raw)
In-Reply-To: <87k1jfk2o7.fsf@netris.org>

On 2019-01-08 07:50, Mark H Weaver wrote:
> Hi,
> 
> swedebugia <swedebugia@riseup.net> writes:
> 
>> On 2019-01-07 12:31, Ricardo Wurmus wrote:
>>>
>>>> $ git pull swedebugia
>>>> fatal: unable to fork
>>>>
>>>> Stracing it reveals that it is missing something (see full attached):
>>>
>>> Where do you see that?
>>
>> Ah, sorry the full command was:
>> strace git pull swedebugia
> 
> I looked at the strace output you provided, and didn't find any evidence
> of a missing file, which I doubt would lead to the error message "unable
> to fork" anyway.  The short excerpt that you quoted in your earlier mail
> showed the failure to find "/etc/ld.so.preload", but that's expected,
> and does not indicate a problem.  The problem might be happening in the
> child process (/home/sdb/.guix-profile/libexec/git-core/git), so adding
> the -f option to strace, i.e. "strace -f git pull swedebugia", might
> yield more useful information.
> 
> If I'm not mistaken, "unable to fork" more likely indicates a lack of
> available resources, possibly due to configured resource limits (see
> ulimit(3) and the 'ulimit' bash builtin, e.g. try "ulimit -a").
> Otherwise, I guess it could be due to restrictions imposed by the use of
> a security framework.

Tried again with "strace -f" and got this:

stat("/home/sdb/.guix-profile/libexec/git-core/ssh", 0x7ffe26617620) =
-1 ENOENT (No such file or directory)
stat("/gnu/store/6ff29rxibnfzabp17qj3mzpc8jggrmsn-profile/bin/ssh",
0x7ffe26617620) = -1 ENOENT (No such file or directory)
stat("/gnu/store/6ff29rxibnfzabp17qj3mzpc8jggrmsn-profile/sbin/ssh",
0x7ffe26617620) = -1 ENOENT (No such file or directory)
stat("/home/sdb/.local/bin;/home/sdb/.guix-profile/bin/ssh",
0x7ffe26617620) = -1 ENOENT (No such file or directory)
stat("/home/sdb/.guix-profile/sbin/ssh", 0x7ffe26617620) = -1 ENOENT (No
such file or directory)
stat("/run/setuid-programs/ssh", 0x7ffe26617620) = -1 ENOENT (No such
file or directory)
stat("/home/sdb/.config/guix/current/bin/ssh", 0x7ffe26617620) = -1
ENOENT (No such file or directory)
stat("/home/sdb/.guix-profile/bin/ssh", 0x7ffe26617620) = -1 ENOENT (No
such file or directory)
stat("/home/sdb/.guix-profile/sbin/ssh", 0x7ffe26617620) = -1 ENOENT (No
such file or directory)
stat("/run/current-system/profile/bin/ssh", 0x7ffe26617620) = -1 ENOENT
(No such file or directory)
stat("/run/current-system/profile/sbin/ssh", 0x7ffe26617620) = -1 ENOENT
(No such file or directory)
close(14)                               = 0

So installing ssh might be a good idea >D

Solved! :D

-- 
Cheers 
Swedebugia

      parent reply	other threads:[~2019-01-12 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 10:07 bug#34006: Guix gc killed live roots - broke git swedebugia
2019-01-07 11:31 ` Ricardo Wurmus
2019-01-07 16:58   ` swedebugia
2019-01-07 17:52     ` Ricardo Wurmus
2019-01-08  7:50     ` Mark H Weaver
2019-01-08  8:50       ` swedebugia
2019-01-12 19:02       ` swedebugia [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=65080922ebfc8a46006fd7fab1ac951c@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=34006-done@debbugs.gnu.org \
    --cc=mhw@netris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).