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 16:49:31 +0200 Message-ID: <871sd2u8zo.fsf@gnu.org> References: <87y3firpjs.fsf@gmail.com> <877en1xbpq.fsf@gnu.org> <87bmc87rlm.fsf@gmail.com> <87zhzswl4s.fsf@gnu.org> <87bmc75wqv.fsf@gmail.com> <8736xjqg5c.fsf@gnu.org> <871sd354mb.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]:47947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVHxN-0007C1-Ta for bug-guix@gnu.org; Tue, 19 Jun 2018 10:50:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVHxK-0001Em-PB for bug-guix@gnu.org; Tue, 19 Jun 2018 10:50:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:48691) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fVHxK-0001EW-KB for bug-guix@gnu.org; Tue, 19 Jun 2018 10:50:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fVHxK-0002EU-AE for bug-guix@gnu.org; Tue, 19 Jun 2018 10:50:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <871sd354mb.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 19 Jun 2018 08:43:08 -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 Maxim Cournoyer skribis: > Attached is the log for the offloading machine. > > From what I can see, the guix-daemon is trying to find the authorized > key in /etc/guix/acl, but the key is added by Guix to > /usr/local/etc/guix/acl... Hmm you may be using two different =E2=80=98guix=E2=80=99 commands no? > 2. The error message should capture the complete error output to ease > debugging: we can see the useful message "25056 write(2, "guix > authenticate: error: error: unauthorized public key: (public-key \n (ecc > \n (curve Ed25519)\n (q > #EEA139318243D36EB4C728DB96856AB15C47AB64C765FA134CCFB12444B82A7C#)\n > )\n )\n", 176) =3D 176" in strace. Had I seen this from the start, we > would have saved some debugging time :). I agree. > I could work around the issue by copying manually the authorized key > sexp to /etc/guix/acl; I now see: > > guix offload: testing 1 build machines defined in '/etc/guix/machines.scm= '... > 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/stor= e/883yjkl46dxw9mzykykmbs0yzwyxm17z-test") > sending 1 store item to '192.168.1.105'... > exporting path `/gnu/store/np9jwqvxjvasz41nrrh6g3gyn4rpkscw-export-test' > guix offload: '192.168.1.105' successfully imported '/gnu/store/np9jwqvxj= vasz41nrrh6g3gyn4rpkscw-export-test' > retrieving 1 store item from '192.168.1.105'... > guix offload: error: build failed: implementation cannot deal with > 32-b= it integers The log has this: --8<---------------cut here---------------start------------->8--- 10529 write(4, "atad\0\0\0\0\0\200\0\0\0\0\0\0", 16) =3D 16 10529 read(4, "W\1\0\0\0\0\0\0\1\0\0\0\0\0\0\0\r\0\0\0\0\0\0\0nix-archive-1= \0\0\0\1\0\0\0\0\0\0\0(\0\0\0\0\0\0\0\4\0\0\0\0\0\0\0type\0\0\0\0\7\0\0\0\0= \0\0\0regular\0\10\0\0\0\0\0\0\0contents\23\0\0\0\0\0\0\000192.168.1.105-83= 353\0\0\0\0\0\1\0\0\0\0\0\0\0)\0\0\0\0\0\0\0NIXE\0\0\0\0007\0\0\0\0\0\0\0/g= nu/store/wf774mzvfjpw306y5x06wid80d9k90qq-import-test\0\0\0\0\0\0\0\0\0\0\0= \0\0\0\0\0\0\1\0\0\0\0\0\0\0(protocol-error 1 \"getting status of `/etc/gui= x/signing-key.sec': Aucun fichier ou dossier de ce "..., 32768) =3D 352 --8<---------------cut here---------------end--------------->8--- Again the error should be reported=E2=80=A6 HTH, Ludo=E2=80=99.