unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 44999@debbugs.gnu.org
Subject: bug#44999: guix deploy Error reading from the channel
Date: Thu, 17 Dec 2020 14:20:49 +0100	[thread overview]
Message-ID: <02995ae7c6c68a77e1f3b15351b64115d90ada47.camel@korwin-zmijowski.fr> (raw)
In-Reply-To: <87eejok6ix.fsf@gnu.org>

Hey Ludo' !

Thank you for asking !

I apologize to have not taken the time to investigate on this
(understand: put 'pk' commands everywhere haha. I don't know what else
to do).

Just did a retry. The command line still hangs with :

   $ guix deploy ynm-droplet-declaration.scm 
   La (1) machine suivante sera déployée :
     kitchen

   guix deploy: déploiement vers kitchen...

The droplet is created with the right hostname (kitchen in ynm / 1 GB
Memory  / 25 GB Disk  / FRA1 - Debian 9 x64)

So I SSH to the machine and ran some commands :

$ ssh root@165.22.28.15 -p 22 -i /home/jeko/.ssh/id_rsa.pub
The authenticity of host '165.22.28.15 (165.22.28.15)' can't be
established.
ECDSA key fingerprint is
SHA256:7dACwKdFtebnZB/vs/pMcChgsp3yoITOvATZFtXki+c.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
yes
Warning: Permanently added '165.22.28.15' (ECDSA) to the list of known
hosts.
Linux kitchen 4.9.0-13-amd64 #1 SMP Debian 4.9.228-1 (2020-07-05)
x86_64

The programs included with the Debian GNU/Linux system are free
software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
# ls /root/
guix-binary-1.0.1.x86_64-linux.tar.xz
# ls /tmp/
guix-infect.sh	var
# guix --version
guix (GNU Guix) 1.0.1
Copyright (C) 2019 the Guix authors
License GPLv3+: GNU GPL version 3 or later <
http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

While I was writing this message, I've been disconnected from SSH

   root@kitchen:~# Connection to 165.22.28.15 closed by remote host.
   Connection to 165.22.28.15 closed.

And the following trace appeared on the hanging deploy command

   ;;; [2020/12/17 14:10:55.445770, 0] read_from_channel_port: [GSSH
   ERROR] Error reading from the channel: #<unknown channel (freed)
   7f2cf28b86c0>

If I want to SSH again to the machine, I get this message :

   $ ssh root@165.22.28.15 -p 22 -i /home/jeko/.ssh/id_rsa.pub
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
   Someone could be eavesdropping on you right now (man-in-the-middle
   attack)!
   It is also possible that a host key has just been changed.
   The fingerprint for the ECDSA key sent by the remote host is
   SHA256:52FacP3UGfdq4zggEVW5cbCzlbqSepkZhki5qMo0bnQ.
   Please contact your system administrator.
   Add correct host key in /home/jeko/.ssh/known_hosts to get rid of
   this message.
   Offending ECDSA key in /home/jeko/.ssh/known_hosts:36
     remove with:
     ssh-keygen -f "/home/jeko/.ssh/known_hosts" -R "165.22.28.15"
   ECDSA host key for 165.22.28.15 has changed and you have requested
   strict checking.
   Host key verification failed.

That's all I can bring on the table right know ! 

To be continued…

Jérémy





  reply	other threads:[~2020-12-17 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02  0:14 bug#44999: guix deploy Error reading from the channel Jérémy Korwin-Zmijowski
2020-12-03 16:45 ` Ludovic Courtès
2020-12-04 14:53   ` Jérémy Korwin-Zmijowski
2020-12-17 11:37     ` Ludovic Courtès
2020-12-17 13:20       ` Jérémy Korwin-Zmijowski [this message]
2021-07-23 21:33         ` Jérémy Korwin-Zmijowski
2021-07-25 17:01           ` Ludovic Courtès

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=02995ae7c6c68a77e1f3b15351b64115d90ada47.camel@korwin-zmijowski.fr \
    --to=jeremy@korwin-zmijowski.fr \
    --cc=44999@debbugs.gnu.org \
    --cc=ludo@gnu.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).