Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jan 2024 13:28:15 -0800
From:      Mark Millard <marklmi@yahoo.com>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: USB-serial adapter suggestions needed
Message-ID:  <902798B1-2B66-4ECD-BDAC-195C85066FE6@yahoo.com>
In-Reply-To: <ZaBLnwaHWYedwY9m@www.zefox.net>
References:  <ZZy2FRO7MCOLMQhp@www.zefox.net> <DD96D1B0-92A8-4CBD-9661-FC86AC547405@yahoo.com> <ZZ2E8OZJBfXLkwQ%2B@www.zefox.net> <ZZ3NGeOtadKMHgIj@www.zefox.net> <3012A549-9482-4D69-9DF4-7987E650DFFA@yahoo.com> <ZZ7fBDxYd8Yyw5fm@www.zefox.net> <E769A770-8D23-4EFC-8E75-F0ACF6705C4E@yahoo.com> <55AC6824-587D-4C67-B64B-2045A1112F69@yahoo.com> <ZZ8ugUkEDXbSUjZp@www.zefox.net> <041F74B4-3D44-4364-9EBD-9F21A4F3B313@yahoo.com> <ZaBLnwaHWYedwY9m@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 11, 2024, at 12:12, bob prohaska <fbsd@www.zefox.net> wrote:

> On Wed, Jan 10, 2024 at 09:34:00PM -0800, Mark Millard wrote:
>>=20
>> "&" creates background processes that are still killed when
>> their parent tty or controlling process goes away. nohup
>> avoids that kill.
>=20
> Not sure what's going on, but if I use=20
> make buildworld &
> on one of my RPi* hosts and log out or otherwise drop
> the connection, the job keeps going. Maybe use of tcsh?
>=20
>>=20
>> What was running on nemesis.zefox.com was its side of the
>> ssh that in turn was attached to the shell that in turn
>> was running tip --until those exited/were-killed on
>> nemesis.zefox.com .
>>=20
>> But there is no information here about which of those was the
>> one to start the failure on nemesis.zefox.com :
>>=20
>> A) Was it the tip process?
>> B) Was it the shell process?
>> C) Was it the nemesis.zefox.com side of the ssh?
>>=20
>=20
>=20
> I've put relevant excerpts from /var/log/messages from
> ns2.zefox.net (the console host) and nemesis.zefox.com
> (the terminal server) at
> http://www.zefox.net/~fbsd/tiptrouble/
> They've been trimmed to the tip failure timeframe.

Note the "ucom_close" and "ucom_shutdown" and "ucom_cfg_close"
in:

Jan 10 14:12:54 nemesis syslogd: last message repeated 1 times
Jan 10 14:16:35 nemesis kernel: ucom_outwakeup: sc =3D =
0xffffa00002466088
Jan 10 14:16:35 nemesis kernel: ucom_get_data: cnt=3D1
Jan 10 14:16:35 nemesis kernel: ucom_get_data: cnt=3D0
Jan 10 14:16:35 nemesis kernel: ucom_inwakeup: tp=3D0xffffa00001979800
Jan 10 14:16:35 nemesis syslogd: last message repeated 1 times
Jan 10 14:26:40 nemesis syslogd: last message repeated 1 times
Jan 10 14:29:48 nemesis syslogd: last message repeated 3 times
Jan 10 14:29:48 nemesis kernel: ucom_close: tp=3D0xffffa00001979800
Jan 10 14:29:48 nemesis kernel: ucom_shutdown:=20
Jan 10 14:29:48 nemesis kernel: ucom_dtr: onoff =3D 0
Jan 10 14:29:48 nemesis kernel: ucom_line_state: on=3D0x00, off=3D0x01
Jan 10 14:29:48 nemesis kernel: ucom_rts: onoff =3D 1
Jan 10 14:29:48 nemesis kernel: ucom_line_state: on=3D0x02, off=3D0x00
Jan 10 14:29:48 nemesis kernel: ucom_cfg_close:=20
Jan 10 15:04:07 nemesis su[35181]: bob to root on /dev/pts/4

Note the time frame vs. your reported:

QUOTE
Jan 10 13:14:06 ns2 sshd[48381]: fatal: Timeout before authentication =
for 59.56.110.106 port 50300
Jan 10 13:34:34 ns2 sshd[926]: error: beginning MaxStartups throttling
Jan 10 14:12:41 ns2 sshd[48506]: error: PAM: Authentication error for =
illegal user shutdown from 185.11.61.234


FreeBSD/arm (ns2.zefox.net) (ttyu0)

login: client_loop: send disconnect: Broken pipe
bob@raspberrypi:~ $=20
END QUOTE

Looks to me like something lead to ucom stopping on
nemesis.zefox.com .

The ns2.zefox.net shows:

QUOTE
Jan 10 14:12:41 ns2 sshd[48506]: error: PAM: Authentication error for =
illegal user shutdown from 185.11.61.234
Jan 10 14:26:28 ns2 sshd[48524]: error: =
Fssh_kex_exchange_identification: Connection closed by remote host
Jan 10 14:43:28 ns2 sshd[48546]: error: PAM: Authentication error for =
illegal user test from 85.209.11.226
Jan 10 15:14:29 ns2 sshd[48603]: error: kex protocol error: type 20 seq =
2 [preauth]
Jan 10 15:14:29 ns2 sshd[48603]: error: kex protocol error: type 30 seq =
3 [preauth]
END QUOTE

It does not suggest ns2.zefox.net as starting the sequence.


> There is a link to a copy of nemesis's sshd_debug.log file at
> http://nemesis.zefox.com/~bob/fbsd/sshd_debug.log
> The file seems too big to search interactively via a
> browser, but it might be possible to download it in
> one pass and then grep locally. For some reason it
> isn't timestamped in any way I recognize.=20
>=20
>> We only know that the end result was lack of anything
>> reading the pipe on nemesis.zefox.com : by then
>> the ssh side on nemesis.zefox.com had stopped being
>> set up to read the pipe.
>>=20
>>=20
>> Did you look at /var/logs/messages [or the analogous linux
>> place(s)] on "pi4 RasPiOS workstation"?  What, if anything, did
>> such have from around the failure time frame?
>>=20
>>=20
> I tried, but the naming is very different from FreeBSD and I
> didn't recognize any obvious candidates. I'll look more later.

Looking around I found in:

=
https://askubuntu.com/questions/26237/difference-between-var-log-messages-=
var-log-syslog-and-var-log-kern-log

QUOTE
2020 update

You may still stumble upon syslog; but the defaults have changed.
journald has replaced syslog, in quite a big portion of systems, =
including Ubuntu.

This is relevant because you won't be finding /var/log/messages that =
often anymore. journald doesn't write plaintext logs =E2=80=94 it uses =
its own, compressed and partially authenticated format.

Search online for e.g. journalctl cheatsheet, or just study man 8 =
systemd-journald, man 1 journalctl yourself.

Syslog and journald are, to a degree, cross-compatible; you can =
transport logs between them in either direction. However, you won't get =
plaintext logs a-la /var/log/messages with journald; and you won't get =
structured (journalctl -o json-pretty) and authenticated logging with =
syslog.
END QUOTE

> Meanwhile, the non-ssh-mediated tip session from=20
> nemesis.zefox.com to ns2.zefox.net's console gpio pins
> remains up.
>=20

Looks like the 110 MiByte or so file will take an hour
or so to transfer from when I started it.


=3D=3D=3D
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?902798B1-2B66-4ECD-BDAC-195C85066FE6>