Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263631 > unrolled thread
| Started by | Adam Weremczuk <adamw@matrixscience.com> |
|---|---|
| First post | 2023-11-17 20:30 +0100 |
| Last post | 2023-11-18 13:10 +0100 |
| Articles | 5 — 5 participants |
Back to article view | Back to linux.debian.user
unexplained crash Adam Weremczuk <adamw@matrixscience.com> - 2023-11-17 20:30 +0100
Re: unexplained crash <tomas@tuxteam.de> - 2023-11-18 07:10 +0100
Re: unexplained crash David Wright <deblis@lionunicorn.co.uk> - 2023-11-18 07:30 +0100
Re: unexplained crash Jeffrey Walton <noloader@gmail.com> - 2023-11-18 07:40 +0100
Re: unexplained crash on Ubuntu 20.04 system Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-11-18 13:10 +0100
| From | Adam Weremczuk <adamw@matrixscience.com> |
|---|---|
| Date | 2023-11-17 20:30 +0100 |
| Subject | unexplained crash |
| Message-ID | <HBcHn-67YP-5@gated-at.bofh.it> |
Hello, Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. The machine was responding to ping and "telnet 22" was briefly connecting before connection closed. The graphical login prompt was visible, but when I tried to log in, it threw me to the text console. No login prompt on any virtual consoles and Ctrl-Alt-Del did nothing. There is no information logged in wtmp, kern.log and dmesg. Nothing interesting in auth.log The last 40 lines from syslog look as below: Nov 16 17:04:23 ubu20 systemd[1]: session-5089.scope: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Manager for UID 0... Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Main User Target. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Basic System. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Paths. Nov 16 17:04:33 ubu20 systemd[1259208]: ubuntu-report.path: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped Pending report trigger for Ubuntu Report. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Sockets. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Timers. Nov 16 17:04:33 ubu20 systemd[1259208]: dbus.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed D-Bus User Message Bus Socket. Nov 16 17:04:33 ubu20 systemd[1259208]: dirmngr.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG network certificate management daemon. Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-browser.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-extra.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-ssh.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent (ssh-agent emulation). Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent and passphrase cache. Nov 16 17:04:33 ubu20 systemd[1259208]: pk-debconf-helper.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed debconf communication socket. Nov 16 17:04:33 ubu20 systemd[1259208]: snapd.session-agent.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed REST API socket for snapd user session agent. Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Shutdown. Nov 16 17:04:33 ubu20 systemd[1259208]: systemd-exit.service: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Finished Exit the Session. Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Exit the Session. Nov 16 17:04:33 ubu20 systemd[1]: user@0.service: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Manager for UID 0. Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Runtime Directory /run/user/0... Nov 16 17:04:33 ubu20 systemd[2567]: run-user-0.mount: Succeeded. Nov 16 17:04:33 ubu20 systemd[1294]: run-user-0.mount: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: run-user-0.mount: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: user-runtime-dir@0.service: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Runtime Directory /run/user/0. Nov 16 17:04:33 ubu20 systemd[1]: Removed slice User Slice of UID 0. Does anybody have an idea what could have happened? Regards, Adam
[toc] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-11-18 07:10 +0100 |
| Message-ID | <HBmGJ-6e1k-3@gated-at.bofh.it> |
| In reply to | #263631 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Nov 17, 2023 at 07:17:08PM +0000, Adam Weremczuk wrote:
> Hello,
>
> Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.
>
> The machine was responding to ping and "telnet 22" was briefly connecting
> before connection closed.
Guessing from the context, you tried to ssh into your desktop and
something went wrong ("became unresponsive"). What /exactly/ did
your ssh client say?
I'd guess along the lines of "connection closed by foreign host",
which would mean the ssh daemon is listening on the other side
but closes the connection shortly after establishing it.
You can gather a bit more of info by adding one (or more) -v options
to your ssh client invocation.
> The graphical login prompt was visible, but when I tried to log in, it threw
> me to the text console. No login prompt on any virtual consoles and
> Ctrl-Alt-Del did nothing.
>
> There is no information logged in wtmp, kern.log and dmesg. Nothing
> interesting in auth.log
>
> The last 40 lines from syslog look as below:
[...]
I'm not a systemd expert by a long shot, so I'll have to leave
this to others, but my first impression of the log is that of
a system shutting down (which is kind of strange).
Perhaps you've had a file system (or underlying drive media)
error and your root FS is mounted read only?
I understand that you managed to log into a console: what does
"mount" say?
Cheers
--
t
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-11-18 07:30 +0100 |
| Message-ID | <HBn06-6e7r-1@gated-at.bofh.it> |
| In reply to | #263635 |
On Sat 18 Nov 2023 at 07:06:49 (+0100), tomas@tuxteam.de wrote:
> On Fri, Nov 17, 2023 at 07:17:08PM +0000, Adam Weremczuk wrote:
> > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.
> >
> > The machine was responding to ping and "telnet 22" was briefly connecting
> > before connection closed.
>
> Guessing from the context, you tried to ssh into your desktop and
> something went wrong ("became unresponsive"). What /exactly/ did
> your ssh client say?
>
> I'd guess along the lines of "connection closed by foreign host",
> which would mean the ssh daemon is listening on the other side
> but closes the connection shortly after establishing it.
>
> You can gather a bit more of info by adding one (or more) -v options
> to your ssh client invocation.
>
> > The graphical login prompt was visible, but when I tried to log in, it threw
> > me to the text console. No login prompt on any virtual consoles and
> > Ctrl-Alt-Del did nothing.
↑↑↑↑↑↑↑↑↑↑↑↑
> >
> > There is no information logged in wtmp, kern.log and dmesg. Nothing
> > interesting in auth.log
> >
> > The last 40 lines from syslog look as below:
>
> [...]
>
> I'm not a systemd expert by a long shot, so I'll have to leave
> this to others, but my first impression of the log is that of
> a system shutting down (which is kind of strange).
They did say they tried Ctrl-Alt-Del. That shuts down (and reboots)
on my systems.
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-11-18 07:40 +0100 |
| Message-ID | <HBn9L-6ean-1@gated-at.bofh.it> |
| In reply to | #263631 |
On Fri, Nov 17, 2023 at 7:11 PM Adam Weremczuk <adamw@matrixscience.com> wrote: > > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. > > The machine was responding to ping and "telnet 22" was briefly > connecting before connection closed. > > The graphical login prompt was visible, but when I tried to log in, it > threw me to the text console. No login prompt on any virtual consoles > and Ctrl-Alt-Del did nothing. > > There is no information logged in wtmp, kern.log and dmesg. Nothing > interesting in auth.log > > The last 40 lines from syslog look as below: > > Nov 16 17:04:23 ubu20 systemd[1]: session-5089.scope: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Manager for UID 0... > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Main User Target. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Basic System. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Paths. > Nov 16 17:04:33 ubu20 systemd[1259208]: ubuntu-report.path: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped Pending report trigger > for Ubuntu Report. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Sockets. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Timers. > Nov 16 17:04:33 ubu20 systemd[1259208]: dbus.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed D-Bus User Message Bus > Socket. > Nov 16 17:04:33 ubu20 systemd[1259208]: dirmngr.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG network certificate > management daemon. > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-browser.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > and passphrase cache (access for web browsers). > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-extra.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > and passphrase cache (restricted). > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-ssh.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > (ssh-agent emulation). > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > and passphrase cache. > Nov 16 17:04:33 ubu20 systemd[1259208]: pk-debconf-helper.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed debconf communication socket. > Nov 16 17:04:33 ubu20 systemd[1259208]: snapd.session-agent.socket: > Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed REST API socket for snapd > user session agent. > Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Shutdown. > Nov 16 17:04:33 ubu20 systemd[1259208]: systemd-exit.service: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Finished Exit the Session. > Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Exit the Session. > Nov 16 17:04:33 ubu20 systemd[1]: user@0.service: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Manager for UID 0. > Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Runtime Directory > /run/user/0... > Nov 16 17:04:33 ubu20 systemd[2567]: run-user-0.mount: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1294]: run-user-0.mount: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: run-user-0.mount: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: user-runtime-dir@0.service: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Runtime Directory > /run/user/0. > Nov 16 17:04:33 ubu20 systemd[1]: Removed slice User Slice of UID 0. > > Does anybody have an idea what could have happened? Whenever I see Snap, I get suspicious. You should probably ask on the ubuntu-users list. The list has a person that answers Snap questions. <ubuntu-users@lists.ubuntu.com>. You should also show the SSH connection log for the client and server. I think that's 'ssh -vvv' for the client, and 'journalctl -u ssh' for the server. Jeff
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-11-18 13:10 +0100 |
| Subject | Re: unexplained crash on Ubuntu 20.04 system |
| Message-ID | <HBsj7-6hHA-1@gated-at.bofh.it> |
| In reply to | #263639 |
On 18 Nov 2023 01:36 -0500, from noloader@gmail.com (Jeffrey Walton): > On Fri, Nov 17, 2023 at 7:11 PM Adam Weremczuk <adamw@matrixscience.com> wrote: >> Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. > > [...] You should probably ask on the ubuntu-users list. [...] I agree. While Ubuntu is based on Debian, it's far enough removed these days that the differences can have a rather large impact, especially for someone who doesn't have hands-on access to the system and who is trying to determine the cause of a problem; so it makes sense to start out somewhere with people most familiar with the distribution you're having issues with. In this case that's Ubuntu; the argument would be the same were it, say, Mint, Slackware, SuSE or RHEL. Which is not to say that whatever the problem is couldn't _also_ have happened on a Debian system. Just that it didn't in this particular instance. If/when you do find out what happened, do however consider posting a summary here. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web