unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "dabbede@gmail.com" <dabbede@gmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: Felix Lechner <felix.lechner@lease-up.com>, help-guix@gnu.org
Subject: Re: Connection refused to Guix-hosted SSH
Date: Sun, 16 Oct 2022 09:53:15 +0200	[thread overview]
Message-ID: <CAEwYQ4QsFpFnLKOhJncbiFOvFCmWuhwKBhHv2AbURWW=e-X6Rw@mail.gmail.com> (raw)
In-Reply-To: <87a65xbp6z.fsf@gmail.com>

Hi all,

in the end I gave up... since my guix was not pulling anymore, I
suspected something more "serious" was happening than just a broken
ssh.
Then I've re-installed the whole system (it was a test system anyway,
not a big deal) and this time ssh works out of the box.
During installation, I've spotted one possible cause that could have
broken sshd in my first sistem: I did not select "Mozilla NSS
certificates" (which translates to package (specification->package
"nss-certs")) ).
I don't know if it is related, but the description says "To connect
through https"... probably not...
The other difference is that my first system was based on i686
(32bit), while the latter is x86_64 (64bit).

Whatever the reason, thank you all for the help.
I hope one day I'll be skilled enough to help others as well.

Regards

On Sat, Oct 15, 2022 at 8:01 AM Oleg Pykhalov <go.wigust@gmail.com> wrote:
>
> "dabbede@gmail.com" <dabbede@gmail.com> writes:
>
> […]
>
> > Sure. I receive a bunch of messages of this form:
> >
> > Oct 14 10:04:23 localhost vmunix: [ 5869.880044] audit: type=1326
> > audit(1665734663.369:6): auid=4294967295 uid=989 gid=983
> > ses=4294967295 subj=unconfined pid=599 comm="sshd"
> > exe="/gnu/store/jgw64z5w2q6b4nph7a74jc97ihfxkfsf-openssh-8.9p1/sbin/sshd"
> > sig=31 arch=40000003 syscall=414 compat=0 ip=0xb7f94549 code=0x0
> > Oct 14 10:04:23 localhost shepherd[1]: 0 connections still in use
> > after sshd-5 termination.
> > Oct 14 10:04:23 localhost shepherd[1]: Service sshd-5 (PID 598) exited with 255.
> > Oct 14 10:04:23 localhost shepherd[1]: Service sshd-5 has been disabled.
> > Oct 14 10:04:23 localhost shepherd[1]: Transient service sshd-5
> > terminated, now unregistered.
> > Oct 14 10:05:43 localhost shepherd[1]: Service sshd-6 has been started.
> > Oct 14 10:05:43 localhost vmunix: [ 5950.061859] audit: type=1326
> > audit(1665734743.553:7): auid=4294967295 uid=989 gid=983
> > ses=4294967295 subj=unconfined pid=601 comm="sshd"
> > exe="/gnu/store/jgw64z5w2q6b4nph7a74jc97ihfxkfsf-openssh-8.9p1/sbin/sshd"
> > sig=31 arch=40000003 syscall=414 compat=0 ip=0xb7fba549 code=0x0
> > Oct 14 10:05:43 localhost shepherd[1]: 0 connections still in use
> > after sshd-6 termination.
> > Oct 14 10:05:43 localhost shepherd[1]: Service sshd-6 (PID 600) exited with 255.
> > Oct 14 10:05:43 localhost shepherd[1]: Service sshd-6 has been disabled.
> > Oct 14 10:05:43 localhost shepherd[1]: Transient service sshd-6
> > terminated, now unregistered.
> >
> > I see "Service sshd-6 (PID 600) exited with 255." but I don't know
> > what it means nor why.
> > In order to gain more insight I've tried to connect with verbose
> > output "ssh -v test@localhost" and this is the output
>
> 255 usually means something wrong with a program execution (e.g. missing
> binary).  In the current case it should a Shell program by SSH default.
>
> Could you try to specify a non-interactive program manually? E.g.:
>
>     ssh -vvv 127.0.0.1 -- /run/current-system/profile/bin/id
>
> It should output SSH client log and ‘id’ program output.
>
>
> Oleg.
>


      reply	other threads:[~2022-10-16  7:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 20:22 Connection refused to Guix-hosted SSH dabbede
2022-10-13  5:30 ` Oleg Pykhalov
2022-10-14  8:27   ` dabbede
2022-10-13 21:04 ` Felix Lechner via
2022-10-14  8:54   ` dabbede
2022-10-14 17:06     ` Felix Lechner via
2022-10-14 20:01       ` dabbede
2022-10-14 20:18         ` Felix Lechner via
2022-10-19 18:54         ` Efraim Flashner
2022-10-19 19:39           ` dabbede
2022-10-15  6:01     ` Oleg Pykhalov
2022-10-16  7:53       ` dabbede [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='CAEwYQ4QsFpFnLKOhJncbiFOvFCmWuhwKBhHv2AbURWW=e-X6Rw@mail.gmail.com' \
    --to=dabbede@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --cc=go.wigust@gmail.com \
    --cc=help-guix@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.
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).