From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] tlssrv: auth_chuid: can't open /lib/namespace: file does not exist: '/lib/namespace' [SOLVED]
Date: Sat, 30 Sep 2023 14:18:29 -0700 [thread overview]
Message-ID: <DDCB4808778CA83D1C987AEF54A10E8C@smtp.pobox.com> (raw)
In-Reply-To: <1E6A72B281D5BDD996600F597B69633D@smtp.pobox.com>
FYI, just as a follow-up, I figured it out. As MJD has yelled before,
"reading the error message!"
Since rcpu(1) uses tcp17019, I considered trying to replicate that
listener with a one-shot listener, but aux/listen had already started
and even if I moved tcp17019 to !tcp17019, it was still listening on
that port. 'kill listen' returned nothing, and I was considering to
attempt a kill on the pid corresponding with the listen process run as
none, but decided first to use auth/none to see if that showed
anything. Indeed it did:
cirno# ls -ld /lib d-rwxrwx--- M 22 sys sys 0 Jun 1 16:49 /lib
So the none user couldn't access anything under /lib. running
'auth/as sys chmod o+rx /lib' resolved this issue.
I have no idea *how* that occurred; I don't think I ever chmod'd that
directory, particularly within the last 48 hours.
Quoth unobe@cpan.org:
> Anyone come across a situation that would make tlssrv throw this error
> on the client side when trying to connect via rcpu? I didn't see anything
> in the e-mail archives.
>
> This just started occurring in the last 24 hours. I can 'touch' the
> file as hostowner. I thought it might have been a stale secstore pw,
> but I've updated that for the hostowner, and still no go.
>
> % ls -l /lib/namespace
> --rw-rw-r-- M 22 sys sys 805 Sep 30 01:40 /lib/namespace
>
> On the client side, tlsclient throws an error:
>
> tlsclient: tlsclient: i/o on hungup channel
>
>
prev parent reply other threads:[~2023-09-30 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 8:55 [9front] tlssrv: auth_chuid: can't open /lib/namespace: file does not exist: '/lib/namespace' unobe
2023-09-30 21:18 ` unobe [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DDCB4808778CA83D1C987AEF54A10E8C@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.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 NNTP newsgroup(s).