I did trace the login ssh process. I haven't tried the top sshd process yet. But that's because we have another problem now. (Apart from being ill the last few weeks.) We can't login to the machine at all anymore. So the problem with the machine gets worse.
A few months ago we have moved to a z13 and zVM 6.3. All machines were moved successfully. But we now have problems with SLES10 SP4 machines. We could logon to them right after the move. At some point ssh failed. And later on the login fails entirely. Even during boot some services can’t be started anymore. It looks like the passwd is corrupted. But when I link the disks in another linux guest I can still read files like passwd, group and shadow. During boot we see some errors, such as: Starting D-BUS daemon Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry Unknown username "haldaemon" in message bus configuration file Starting SSH daemon Privilege separation user sshd does not exist startproc: exit status of parent of /usr/sbin/sshd: 255 When I try to login to the affected machines users are not accepted anymore. Even in a 3270 console I can't login anymore. We have a couple of SLES10 SP2 machines without any problems, all SLES11 machines function correctly. It looks like to be a problem specific to SLES10 SP4. Could there be an issue specifically related to SLES10 SP4 on zVM 6.3/z13? Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post Sent: Friday, May 27, 2016 7:29 PM To: [email protected] Subject: Re: Unable to login with ssh >>> On 5/27/2016 at 08:57 AM, Grzegorz Powiedziuk <[email protected]> wrote: > One other thing you could try (saved me many times) but a bit trouble > some is doing some stracing. This was something I was going to suggest as well. > 1. ssh to the user@server and let it sit on the login 2. on the > server, do ps auxwww |grep sshd and look for a new spawned process Personally I would just pick the "top most" ssh process started at boot time _before_ trying to connect over the network. -snip- > 3. strace -p 36203 &> logfile.x I would probably try strace -f -p 36203 -s500 -o strace.sshd You'll need to break out of it using ^c since the process won't terminate on its own. -snip-> 5. Now examine the the trace by looking at the logile.x (it will be a big > file). If you don't have terminal server access you'll probably need to access it via FTP since scp is not likely to work. Which raises a perhaps interesting question. From the 3270 console are you able to ssh/scp _out_ of the system? That would at least allow you to send things off the system to some place you can use "normal" tools. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
