From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#31825: guix offload fails with guix-authenticate error Date: Tue, 19 Jun 2018 11:28:31 +0200 Message-ID: <8736xjqg5c.fsf@gnu.org> References: <87y3firpjs.fsf@gmail.com> <877en1xbpq.fsf@gnu.org> <87bmc87rlm.fsf@gmail.com> <87zhzswl4s.fsf@gnu.org> <87bmc75wqv.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVCwl-0004KA-Om for bug-guix@gnu.org; Tue, 19 Jun 2018 05:29:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVCwg-0005XN-PQ for bug-guix@gnu.org; Tue, 19 Jun 2018 05:29:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:47819) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fVCwg-0005XE-Lw for bug-guix@gnu.org; Tue, 19 Jun 2018 05:29:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fVCwg-0000yT-Ft for bug-guix@gnu.org; Tue, 19 Jun 2018 05:29:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87bmc75wqv.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 18 Jun 2018 22:35:36 -0400") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Maxim Cournoyer Cc: 31825@debbugs.gnu.org Hi Maxim, Maxim Cournoyer skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> Hello, >> >> Maxim Cournoyer skribis: >> >>> maxim@apteryx ~$ guix offload test >>> guix offload: testing 1 build machines defined in '/etc/guix/machines.s= cm'... >>> guix offload: '192.168.1.105' is running guile (GNU Guile) 2.2.3 >>> guix offload: Guix is usable on '192.168.1.105' (test returned "/gnu/st= ore/883yjkl46dxw9mzykykmbs0yzwyxm17z-test") >>> sending 1 store item to '192.168.1.105'... >>> exporting path `/gnu/store/smgzvgc9krglk0mjpcscg5450l05w4dg-export-test' >>> guix offload: error: build failed: program `guix-authenticate' failed >>> with exit code 1 >> >> On closer inspection, it looks like it may be =E2=80=98guix-authenticate= =E2=80=99 on >> =E2=80=9Capteryx=E2=80=9D that fails. This could happen if there=E2=80= =99s no signing key, for >> instance, but you said there=E2=80=99s one, so I don=E2=80=99t know. >> >> Could you attach strace to guix-daemon on =E2=80=9Capteryx=E2=80=9D and = run =E2=80=9Cguix >> offload test=E2=80=9D again? >> >> Use something like: >> >> # strace -p $(pidof guix-daemon) -f -s 345 -o /tmp/log >> >> and then: >> >> # guix offload test > > I've ran exactly those commands, and this produced the log attached > (half a megabyte of text!). I looked at it but I can't seem to see > what's wrong in there. I hope your trained eyes can see differently! I don=E2=80=99t see =E2=80=9Cprogram `guix-authenticate' failed=E2=80=9D, a= nd indeed =E2=80=98guix authenticate=E2=80=99 exits with code 0 (indicating success.) Are you still getting the error above? If so it may be that my diagnostic was wrong and that the authentication failure happens on the other machine. Could you strace guix-daemon on that other machine similarly? However, note that the log ended up containing a copy of your secret key, /etc/guix/signing-key.sec; sorry for not thinking about this before. So once we=E2=80=99re done debugging, you should consider throwing= away that key and re-running =E2=80=9Cguix archive --generate-key=E2=80=9D. In = the next strace log you send, you might want to remove the private key (look for an sexp starting with =E2=80=9C(private-key =E2=80=A6=E2=80=9D). Thanks, Ludo=E2=80=99.