Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #219484 > unrolled thread
| Started by | "James H. H. Lampert" <jamesl@touchtonecorp.com> |
|---|---|
| First post | 2020-02-26 17:50 +0100 |
| Last post | 2020-02-27 20:30 +0100 |
| Articles | 6 — 3 participants |
Back to article view | Back to linux.debian.user
This is weird: I can ssh into a box, but I can't access it directly "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2020-02-26 17:50 +0100
Re: This is weird: I can ssh into a box, but I can't access it directly Dan Purgert <dan@djph.net> - 2020-02-26 18:00 +0100
Re: This is weird: I can ssh into a box, but I can't access it directly "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2020-02-27 19:40 +0100
Re: This is weird: I can ssh into a box, but I can't access it directly Dan Purgert <dan@djph.net> - 2020-02-27 19:50 +0100
Re: This is weird: I can ssh into a box, but I can't access it directly Greg Wooledge <wooledg@eeg.ccf.org> - 2020-02-27 20:00 +0100
Re: This is weird: I can ssh into a box, but I can't access it directly Dan Purgert <dan@djph.net> - 2020-02-27 20:30 +0100
| From | "James H. H. Lampert" <jamesl@touchtonecorp.com> |
|---|---|
| Date | 2020-02-26 17:50 +0100 |
| Subject | This is weird: I can ssh into a box, but I can't access it directly |
| Message-ID | <zE82J-X2-3@gated-at.bofh.it> |
One of our Linux boxes is behaving oddly. If I ssh into it, I can connect easily, and I get: > 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. > Last login: Wed Jan 29 08:32:12 2020 from 192.168.1.15 But if I go into the server cage, and punch it up on the KVM switch, and try to sign on as root, I get: > Debian GNU/Linux 8 Titan tty1 > > Titan login: root > [10371235.533392] end_request: I/O error, dev sda, sector 105228592 and after a few seconds, the screen clears, and goes back to > Debian GNU/Linux 8 Titan tty1 > > Titan login: Or, at other times, when I punch it up on the KVM switch, I get a whole screen full of hard disk error messages. It's pretty clear to me that the box is more-or-less shot anyway (even from the ssh session, if I try to "cd home," I get an error message), but can somebody tell me why I'm getting one behavior through ssh, and completely different behavior through a direct connection? -- JHHL
[toc] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2020-02-26 18:00 +0100 |
| Subject | Re: This is weird: I can ssh into a box, but I can't access it directly |
| Message-ID | <zE8cp-10f-9@gated-at.bofh.it> |
| In reply to | #219484 |
[Multipart message — attachments visible in raw view] — view raw
On Feb 26, 2020, James H. H. Lampert wrote: > One of our Linux boxes is behaving oddly. If I ssh into it, I can connect > easily, and I get: > [...] > > But if I go into the server cage, and punch it up on the KVM switch, > and try to sign on as root, I get: Are you ssh'ing in as root? If not, is your user's $HOME on the machine's failing disk, or another (remote?) drive? -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
[toc] | [prev] | [next] | [standalone]
| From | "James H. H. Lampert" <jamesl@touchtonecorp.com> |
|---|---|
| Date | 2020-02-27 19:40 +0100 |
| Subject | Re: This is weird: I can ssh into a box, but I can't access it directly |
| Message-ID | <zEweJ-7wO-5@gated-at.bofh.it> |
| In reply to | #219486 |
On 2/26/20 8:52 AM, Dan Purgert wrote: > Are you ssh'ing in as root? If not, is your user's $HOME on the > machine's failing disk, or another (remote?) drive? and I replied (off-List, and *not* intentionally so): > Yes. As root. > > Oh, and one other thing, the thing that brought this to my attention in the first place: something in the server cage is emitting a faint beep (or perhaps a faint squeak of a dying hard drive), every second or so. I think it's coming from that selfsame box. I signed on again via ssh, intending to just shut the thing down for good, and noticed two things: 1. "shutdown" didn't work 2. It was telling me I'd last signed on sometime in January, when in fact, I'd signed on yesterday. Further investigation of #1 led me to find out that it was getting a disk error just trying to shut itself down. It's clearly toast. So I did a hard shutdown (and disconnected the power, for good measure. And it *was* the source of the faint beeping. -- JHHL
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2020-02-27 19:50 +0100 |
| Subject | Re: This is weird: I can ssh into a box, but I can't access it directly |
| Message-ID | <zEwop-7Ac-3@gated-at.bofh.it> |
| In reply to | #219589 |
[Multipart message — attachments visible in raw view] — view raw
On Feb 27, 2020, James H. H. Lampert wrote: > On 2/26/20 8:52 AM, Dan Purgert wrote: > > Are you ssh'ing in as root? If not, is your user's $HOME on the > > machine's failing disk, or another (remote?) drive? > > and I replied (off-List, and *not* intentionally so): > > Yes. As root. Interesting that "root from SSH" would behave differently than "local root". That's news to me. > [...] > It's clearly toast. So I did a hard shutdown (and disconnected the power, > for good measure. Sounds like it won't be giving you any trouble for a few days (until if you're like me, you see it unplugged and wonder why that is and ...) -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-02-27 20:00 +0100 |
| Subject | Re: This is weird: I can ssh into a box, but I can't access it directly |
| Message-ID | <zEwy6-7DA-11@gated-at.bofh.it> |
| In reply to | #219590 |
On Thu, Feb 27, 2020 at 01:47:10PM -0500, Dan Purgert wrote: > Interesting that "root from SSH" would behave differently than "local > root". That's news to me. Well, they run different programs, and read different config files. A console login uses getty + login, and reads /etc/pam.d/login. An ssh login uses sshd, and reads /etc/pam.d/sshd. If one of those files is damaged beyond recovery, it could affect one type of login, but not the other.
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2020-02-27 20:30 +0100 |
| Subject | Re: This is weird: I can ssh into a box, but I can't access it directly |
| Message-ID | <zEx18-82R-11@gated-at.bofh.it> |
| In reply to | #219591 |
[Multipart message — attachments visible in raw view] — view raw
On Feb 27, 2020, Greg Wooledge wrote: > On Thu, Feb 27, 2020 at 01:47:10PM -0500, Dan Purgert wrote: > > Interesting that "root from SSH" would behave differently than "local > > root". That's news to me. > > Well, they run different programs, and read different config files. > A console login uses getty + login, and reads /etc/pam.d/login. An > ssh login uses sshd, and reads /etc/pam.d/sshd. Thanks for the clarity. I suppose I have to bump up console vs. ssh logins higher on the list of "everything I need to learn about Linux" -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web